fix(ci): install latest 22.x Node to satisfy @microsoft/fast-build engines#36246
Merged
Merged
Conversation
…gines The 1ES container ships Node 22.14.0, but @microsoft/fast-build (and @microsoft/fast-test-harness) require node >=22.18.0, causing yarn install to fail. Set checkLatest: true on UseNode@1 so the task upgrades to the latest 22.x when the bundled container Node is older.
📊 Bundle size report✅ No changes found |
|
Pull request demo site: URL |
dmytrokirpa
approved these changes
May 26, 2026
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
2 participants
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.
Problem
yarn installfails on Azure CI with:Cause
@microsoft/fast-build@0.6.0and@microsoft/fast-test-harness@0.1.0to root devDependencies.engines.node: ">=22.18.0"(verified across all published versions, 0.1.1 → 0.7.0 — so downgrading is not an option).22.14.0. The Azure pipeline'sUseNode@1task was pinned withversion: '22.x'+checkLatest: false, so it just reused the container's older 22.x instead of installing a newer one.actions/setup-nodewithnode-version: '22'already resolves to the latest 22.x.Fix
Set
checkLatest: trueon theUseNode@1task in.devops/templates/tools.yml. This forces the task to fetch the latest 22.x when the container's bundled Node is older, while still respecting the22.xmajor-version pin.Verification
.devops/templates/tools.yml, so the fix applies broadly with a single change.engines: ^22.0.0 || ^24.0.0from rootpackage.json; this only changes the ADO Node install task).