{{ message }}
Repository navigation
fix: no-ticket: use relative node-version-file path for setup-node v7.1.0 - #8948
Merged
Merged
Conversation
….1.0 The "Update web version" workflow started failing with: Error: The specified node version file at: /web/client-api/types/.nvmrc does not exist The failure began after Dependabot bumped actions/setup-node from v7.0.0 to v7.1.0 (7212db0). v7.1.0 added "Support absolute paths in node-version-file" (actions/setup-node#1633). Previously the input was always joined onto $GITHUB_WORKSPACE, so the leading "/" was harmless. Now a path starting with "/" is treated as absolute on the runner filesystem, so the action looked outside the checkout. Drop the leading slash so the path resolves relative to the workspace. The leading slashes under sparse-checkout are git patterns anchored at the repo root and are unaffected. Release notes: https://github.com/actions/setup-node/releases/tag/v7.1.0
mofojed
requested review from
JamesXNelson,
cpwright,
devinrsmith,
jcferretti and
rcaudy
as code owners
October 19, 2026 14:53
Contributor
No docs changes detected for ed6f6c4 |
mofojed
added
NoDocumentationNeeded
NoReleaseNotesNeeded
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The relative path matches the checked-out file and setup-node’s path resolution behavior.
No open issues 🎉
What changed in this PR
Fixes Node setup in the “Update web version” workflow after the setup-node v7.1.0 upgrade.
Changes:
- Makes
node-version-filerelative to the workspace. - Leaves sparse-checkout patterns unchanged.
Review effort: Balanced
mofojed
enabled auto-merge (squash)
October 19, 2026 14:57
cpwright
approved these changes
Oct 19, 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The "Update web version" workflow started failing with:
Error: The specified node version file at: /web/client-api/types/.nvmrc does not exist
The failure began after Dependabot bumped actions/setup-node from v7.0.0
to v7.1.0 (7212db0). v7.1.0 added "Support absolute paths in
node-version-file" (actions/setup-node#1633). Previously the input was
always joined onto $GITHUB_WORKSPACE, so the leading "/" was harmless.
Now a path starting with "/" is treated as absolute on the runner
filesystem, so the action looked outside the checkout.
Drop the leading slash so the path resolves relative to the workspace.
The leading slashes under sparse-checkout are git patterns anchored at
the repo root and are unaffected.
Release notes: https://github.com/actions/setup-node/releases/tag/v7.1.0