Use Node major version rather than full version#15673
Open
DanielCliftonGuardian wants to merge 4 commits intomainfrom
Open
Use Node major version rather than full version#15673DanielCliftonGuardian wants to merge 4 commits intomainfrom
DanielCliftonGuardian wants to merge 4 commits intomainfrom
Conversation
DanielCliftonGuardian
changed the title
DanielCliftonGuardian
added
the
maintenance
|
Hello 👋! When you're ready to run Chromatic, please apply the You will need to reapply the label each time you want to run Chromatic. |
SiAdcock
reviewed
Apr 10, 2026
SiAdcock
reviewed
Apr 10, 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.
What does this change?
Following a DevX recommendation, this PR updates our tooling to specify a node_major_version (22) instead of a strict node_full_version (22.18.0) across the repository.
Previously, bumping patch/minor Node versions required creating new AMIgo recipes and updating several synced files. By moving to a major version constraint, we simplify our upgrade path and align with DevX best practices.
Deployed to code
Why?
Resolves: #15081
Keeping .nvmrc, CI configs, and AMIgo recipes synced to a highly specific patch version creates unnecessary maintenance overhead. Relying on the major version ensures consistency across environments while allowing safe, automatic consumption of non-breaking security and bug fixes.