Repository navigation
Conversation
Pin .nvmrc to 24.22.1, point CI and release workflows at it instead of the runner's cached 24.x, and raise the root engines floor. Published package engines are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
node:20-alpine is end of life and won't receive the October 21 Node.js security fixes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
chore: pin Node.js 24.22.1 for the October 21 security release
Brings next up to date with main, including the Next.js 16.4.1 security upgrade (#304), so Vercel previews built from next stop running Next 16.2.10. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings the security fixes (#308, #309), release pipeline hardening (#307, #316), action updates and the 1.0.1 version bump into next. In release.yml, keeps next's node-version-file pin from #305 and main's removal of the pnpm cache from publishing jobs (#307). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…o-next-1.0.1 chore: forward-merge main into next after 1.0.1
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This branch was successfully deployed
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.
Summary
Merges
nextintomain. Since #317,nextcontains everything onmain. The only change this brings over is #305, the Node.js 24.22.1 pin from the October 21 security release, which so far landed only onnext:.nvmrc→24.22.1(new onmain), andengines.node→>=24.22.1node-version-file: .nvmrc.mainasked for plainnode-version: 24, which resolves to 24.22.1 today, but the pin keeps it explicit.AGENTS.mdmentions the pin, andexamples/remix-basic/Dockerfilebuilds on Node 24.In
release.ymlthe publishing jobs keepmain's removal of the pnpm cache (#307). Only the Node source changes.Evidence
git diff main nextis 8 files, +15/−14 lines, listed above.nexthas no.changeset/*.mdfiles and no.changeset/pre.json, so the release workflow onmainfinds nothing to version or publish after the merge.Risk and rollback
Door: Two-way. Revert the merge commit to undo. Merge with a merge commit so
mainandnextstay in sync.Blast radius: CI and release workflows install Node from
.nvmrc(24.22.1) instead of the latest 24.x. Contributors on Node older than 24.22.1 get an engines warning.🤖 Generated with Claude Code