You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The reason will be displayed to describe this comment to others. Learn more.
By removing node-version: 'latest' here, this actions/setup-node@v6 step no longer supplies a node-version or node-version-file, so the action will fail with a missing required input. To keep builds deterministic and functional, specify a pinned Node version (for example an LTS range like 22.x) or use node-version-file referencing your repo's Node version file instead of omitting the version entirely.
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
The reason will be displayed to describe this comment to others. Learn more.
Removing the node-version: 'latest' line here leaves actions/setup-node@v6 without any node-version or node-version-file input, which will cause the action to fail with "Input required and not supplied: node-version" at runtime. To keep the workflow working while avoiding latest, configure a specific Node version (e.g., an LTS range like 22.x) or point node-version-file at your .nvmrc/.node-version file instead of removing the version entirely.
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By removing
node-version: 'latest'here, thisactions/setup-node@v6step no longer supplies anode-versionornode-version-file, so the action will fail with a missing required input. To keep builds deterministic and functional, specify a pinned Node version (for example an LTS range like22.x) or usenode-version-filereferencing your repo's Node version file instead of omitting the version entirely.