fix(frontend): restore Node 20 toolchain - #142
Merged
Merged
Conversation
|
Someone is attempting to deploy a commit to the gexs Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
gac0812
marked this pull request as ready for review
August 3, 2026 01:55
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
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 changed
>=20.20.2 <21.20.20.2in the main CI workflow.20.20.2in the PR preview workflow.Why
The repository already declares Node
20.20.2infrontend/.nvmrcand the root package metadata infrontend/package-lock.json. Commitf8852c0changed only the package engine and workflow runners to Node 22, leaving the version sources inconsistent. This PR restores one toolchain version across the project.Validation
npm run check(lint, format check, TypeScript, and 209 tests)frontend/package.json,frontend/package-lock.json, andfrontend/.nvmrcall resolve to Node20.20.2.