Repository navigation
chore: forward-merge main into next - #306
Merged
Merged
Conversation
docs: standardize EdgeStore branding
fix: repair Sponsor and YouTube links
Upload button usage and block, and file field, imported FileList/FileListItem from multi-file without the matching registry dependency. Extract FileBadge, FileListItem and FileList into file-list.tsx with a file-list registry item. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
fix: move file list into its own registry item
…y-imports # Conflicts: # docs/public/r/upload-button-block.json
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
fix: open registry blocks in v0 as the app page
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Patches GHSA-673q-mjm6-r5xr (use cache RCE), CVE-2026-96889 / GHSA-2464-fhr4-w9xw (Image Optimization SVG RCE via sharp) and GHSA-p3m5-59mp-jv5r (Server Actions DoS) in the docs site and the Next.js examples. Next now resolves the fixed sharp 0.35.5. 16.4.1 is younger than the one-day minimumReleaseAge, so its exact versions are excluded until then. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
fix(deps): upgrade Next.js to 16.4.1 (October 14 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>
|
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
Forward-merges
mainintonext, asRELEASING.mddescribes for stable fixes.nextwas 21 commits behindmain. The important one is the Next.js 16.4.1 security upgrade (#304, the October 14 advisories). Until this merges, Vercel preview deployments built fromnextkeep running Next 16.2.10: today'sedgestore-docs,example-access-controlandexample-componentspreviews do. Production (main) is already on 16.4.1.The merge applied cleanly with no conflicts.
nextkeeps its own Node 24.22.1 pin from #305.Evidence
On the merge commit, using pnpm 11.15.1 and Node 24.22.1:
pnpm install --frozen-lockfile: passes (lockfile consistent; catalognext: 16.4.1)pnpm build: passespnpm typecheck: passespnpm test: 9/9 tasks passRisk and rollback
Door: Two-way. Revert the merge commit to undo. Merge this with a merge commit, not a squash, so later forward merges stay clean.
Blast radius: Only the
nextbranch and its Vercel previews. Nothing is published:nextis dormant (no.changeset/pre.json), so the release workflow skips on push.🤖 Generated with Claude Code