Skip to content

Update Action to use Node.js v20#411

Merged
MoChilia merged 3 commits intoAzure:masterfrom
j-chao:master
Feb 20, 2024
Merged

Update Action to use Node.js v20#411
MoChilia merged 3 commits intoAzure:masterfrom
j-chao:master

Conversation

@j-chao
Copy link
Copy Markdown
Contributor

@j-chao j-chao commented Jan 23, 2024

Node.js 16 actions are deprecated.
Updating action to use Node.js 20.

Link: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/

Fixes #357

@j-chao
Copy link
Copy Markdown
Contributor Author

j-chao commented Jan 23, 2024

@YanaXu @MoChilia
Any objections to getting this Action updated to using Node.js 20?

@YanaXu
Copy link
Copy Markdown
Collaborator

YanaXu commented Jan 24, 2024

Hi @j-chao , we do want to upgrade the node version, together with other old node module versions. But it's not a easy update. It asks for full tests and all necessary checks. We'll keep this PR open for a reminder. Thanks for your work.

Copy link
Copy Markdown

@bharatatDisys bharatatDisys left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes are not significant . Can be merged without breaking.

@kohtala
Copy link
Copy Markdown

kohtala commented Jan 29, 2024

Usually packages just open a new major when a node version support is removed. That way users know it can break something and can avoid unintentional upgrades.

@eikooc
Copy link
Copy Markdown

eikooc commented Jan 30, 2024

There is already an open PR with this change here #392

@FlorentATo
Copy link
Copy Markdown

This PR seems incomplete @j-chao: https://github.com/search?q=repo%3AAzure%2Flogin%2016.x&type=code

@eikooc
Copy link
Copy Markdown

eikooc commented Feb 14, 2024

@FlorentATo I've explained the same comment in another PR in a comment. Those node versions don't have anything to do with this action's node version. It is their own workflows and they can be updated independently as they are not used by the action when you run the action in your repo.

@kohtala
Copy link
Copy Markdown

kohtala commented Feb 15, 2024

Those node versions don't have anything to do with this action's node version. It is their own workflows and they can be updated independently as they are not used by the action when you run the action in your repo.

@eikooc There are some npm run test that should run with the same version that is going to be used to run the action when released. I see some integration tests are run by executing the action, so those parts do use the node20 to test it, but I expect the unittests would cover some additional cases.

Updating all Github workflows used in CI checks to use Node 20.x
@j-chao
Copy link
Copy Markdown
Contributor Author

j-chao commented Feb 17, 2024

@microsoft-github-policy-service agree

@MoChilia MoChilia self-requested a review February 20, 2024 05:44
@AndrewEhlo
Copy link
Copy Markdown

AndrewEhlo commented Feb 29, 2024

When using an updated to node20 version got the error
image
Did anyone face it too?
@MoChilia @justinmchase
Seems like lib folder has been excluded from the action in recent versions:
image

@MoChilia
Copy link
Copy Markdown
Member

Hi @AndrewEhlo, please avoid running azure/login from the master branch. The built files will be only included in the release branch. Kindly wait for the new release. Thank you.

@JochemE
Copy link
Copy Markdown

JochemE commented Feb 29, 2024

Hi @MoChilia, do you have an idea on when this will be released?
Expected release is March 👍
#420 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Deprecation warning due to Node 16

10 participants