Align local Node version with Docker - #735
Merged
naveed-ahmad merged 1 commit intoAug 25, 2026
Merged
Conversation
Member
|
We should upgrade node to 24 |
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.
Description
The Dockerfile uses Node 20, but
.node-versionstill points to Node 18.0.0. This updates it to 20.20.2 so local development and Docker use the same Node release.Related Issue
Addresses the Node version mismatch reported in #707.
Motivation and Context
Keeping the Node versions aligned helps avoid differences between local and Docker builds.
How Has This Been Tested?
Tested with
yarn install --frozen-lockfileandyarn run buildusing Node 20.20.2 and Yarn 1.22.22.Screenshots
Not applicable.