Repository navigation
ci: setup-node check-latest so builds use the newest Node 22 patch - #18
Merged
Merged
Conversation
The 10/21 deploy built with the runner's cached 22.23.3; today's Node security release (22.23.4: Brotli OOB write CVE-2026-111497, TLS hostname, DNS truncation) only lands if setup-node checks for the latest 22.x. The site is static on GitHub Pages, so this is build-time exposure only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Collaborator
Author
|
Merge record (vale, 2026-10-21 23:2x): CI green on the head sha. Positive control: before this PR the deploy built with cached v22.23.3 (run 39687079451); with it, CI logs "Resolved as '22.23.4'" → node v22.23.4. Cross-model review (xreview, gpt-6.1-sol-2026-09-29): AGREE; its comment-wording nit is applied. gitleaks found no leaks. Merged under JP's standing yes (CI-workflow change, independent review done). |
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.
realmwatch-e5 (JP #136, via jp-58) flagged Node 20 EOL and today's Node security release (10 CVEs; worst CVE-2026-111497, a Brotli decoder OOB write).
State before this PR
22, all workflowsnode-version: 22).server: GitHub.com); it's a static export, so no Node runs in production.check-latest: false.This PR
check-latest: trueto all six setup-node steps (ci, deploy-web, release ×3, sync-data), so builds take the newest 22.x patch.Dependency items from the 10-21 audit
@expo/cli(^6.0.5) andcacache(^6.1.11), both build tools. A tar 7 override brokeexpo prebuildon 10/21 ("Cannot read properties of undefined (reading 'extract')"), and tar never reaches the static web bundle. Revisit when Expo moves to tar 7.🤖 Generated with Claude Code