chore: update dependencies and verify supported Node runtimes in CI - #209
Merged
Conversation
Contributor
|
🦞👀 Pull request received. I will update this pull request when review starts. ClawSweeper review completeClawSweeper finished reviewing this revision. The review result is being finalized. |
Contributor
|
ClawSweeper status: review started. I am starting a fresh review of this pull request: chore: update dependencies and verify supported Node runtimes in CI This is item 1/1 in the current shard. Shard 0/1. This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking. Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted. |
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 Problem This Solves
The CLI declares Node 22 support, but CI tested only Node 26 and used Node 26 typings. Several dependencies and security/deployment actions had newer eligible releases, and some workflows still referenced mutable action tags.
User Impact
Runtime support remains Node 22 or newer. CI now tests and runs the installed package on Node 22, 24, and 26, while preserving the Windows process-execution checks.
Why This Change Was Made
Update Zod to 4.6.2, pnpm to 11.26.0, Oxfmt to 0.67.0, Oxlint to 1.82.0, and the Vite override to 8.3.0. Align Node typings to 22.20.2. Pin all remaining action references to verified commit SHAs, update CodeQL to 4.38.0 and Pages deployment to 5.0.1, and bound CI jobs with PR cancellation for superseded runs. Existing permissions and security checks remain in place.
All chosen releases are older than 48 hours. Zod 4.6.3 was intentionally deferred because it was published on September 12 at 22:23 UTC; 4.6.2 was published September 10 at 21:44 UTC. The pnpm minimum release age remains 2880 minutes. No package version bump or runtime-floor change.
Evidence
pnpm install --frozen-lockfilesucceeds with pnpm 11.26.0 and its supply-chain policy verification.actionlintpasses. GitHub tag/ref queries resolve every new action pin, including the annotated CodeQL release tag.pnpm audit --json: zero vulnerabilities at every severity.pnpm typecheck,pnpm lint,pnpm format:check,pnpm test,pnpm build, andpnpm website:smokepassed: 941 passed / 2 existing platform skips.pnpm pack:smokemaps 13 mixed-language features, including 3 CUDA.