build: update node toolchain to 24.17.0 - #79
Merged
Conversation
✅ Deploy Preview for limitless-angular-sanity-example canceled.
|
commit: |
osnoser1
force-pushed
the
osnoser1/replicate-cianz-pr-32-node-24
branch
from
June 21, 2026 04:54
867c8ec to
31b2b5e
Compare
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.
PR Checklist
No linked issue.
What is the new behavior?
volta.extendsto nested workspace package manifests so commands inherit the root toolchain.24.17.0across.nvmrc, root Volta config, root engines,pnpm-workspace.yaml, Netlify config, and contributor docs.devEngines.runtimepinned to Node24.17.0, plusnode@runtime:24.17.0lockfile metadata sopnpm nodeandpnpm exec nodeuse the pinned runtime.@types/nodespecs to~24.13.2and refreshespnpm-lock.yaml.mcr.microsoft.com/playwright:v1.44.1-jammyimage, removingplaywright install --with-depsfrom GitHub-hosted runners, trusting the checked-out workspace inside containers, and passingPLAYWRIGHT_BROWSERS_PATH=/ms-playwrightthrough Turbo.webServerhangs inside the generated consumer.timeout-minutesworkarounds.Does this PR introduce a breaking change?
Other information
CI diagnosis:
devEngines.runtimecommit, so the runtime metadata was not the root cause.24.17.0; this was not an Angular/Node version incompatibility.Validation:
git diff --checkpnpm --filter @limitless-angular/angular-compat testpnpm --filter @limitless-angular/release-tools test[Optional] What gif best describes this PR or how it makes you feel?
N/A