CI: Add explicit node version to jobs#63262
Open
champ24-36 wants to merge 1 commit intomicrosoft:mainfrom
Open
CI: Add explicit node version to jobs#63262champ24-36 wants to merge 1 commit intomicrosoft:mainfrom
champ24-36 wants to merge 1 commit intomicrosoft:mainfrom
Conversation
|
@champ24-36 please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds an explicit
node-versionkey to each job in the CI workflow. This ensures consistent behavior across different runners and avoids potential issues caused by relying on the default node version. It also improves reproducibility.Specifically, I've added
node-version: 18to all relevant jobs. This version is currently used by the project and is a good balance of stability and features.Contributed via automated PR bot