fix: pin Volta runtime for setup - #30
Merged
Merged
Conversation
✅ Deploy Preview for limitless-angular-sanity-example canceled.
|
osnoser1
marked this pull request as ready for review
June 7, 2026 18:23
commit: |
Angular canary compatibility warningThe advisory Angular canary compatibility check failed. This does not block the PR because canary targets are outside the currently required support matrix. Supported peer range:
Stable Angular compatibility rows remain required and will still fail CI if the declared peer range is broken. |
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
1 participant
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.
PR Checklist
Fixes a local Codex worktree setup failure where the generated setup script ran
pnpm install --frozen-lockfileunder Volta's default Node24.11.0, which fails@netlify/angular-runtime@4.0.0engine checks.Closes #
What is the new behavior?
Adds a
voltapin in the rootpackage.jsonfor Node22.22.3and pnpm11.5.2, matching the existing.nvmrc,packageManager, and engine requirements. This lets plainpnpm install --frozen-lockfileuse the compatible Node version during local environment setup.Validation:
24.11.0.nvm use && pnpm install --frozen-lockfilesucceeds.node -vresolves tov22.22.3after the Volta pin.Does this PR introduce a breaking change?
Other information
Ignored setup artifacts such as
node_modules, copied.env.localfiles, and.authwere created locally while verifying the setup, but are not included in this PR.[Optional] What gif best describes this PR or how it makes you feel?