Repository navigation
chore(deps): bump next from 16.3.0 to 16.3.1 - #2460
Conversation
Castiron custom code✅ No new custom-code files detected. 32 mixed files remain; 0 existing customizations changed. Compared 32 existing customizations unchanged
A changed generated baseline means this report cannot reliably identify which handwritten lines changed. Inspect the custom-code diffDownload the exact patch produced by this run (requires repository access): gh run download 32877600748 --repo openai/openai-node \
--name castiron-custom-code-32877600748-1 --dir /tmp/castiron-custom-code-32877600748-1
git apply --stat /tmp/castiron-custom-code-32877600748-1/custom-code.patch
cat /tmp/castiron-custom-code-32877600748-1/custom-code.patchOr reproduce it from an SDK checkout containing the vendored reporter: git fetch --no-tags origin cc532b3f173e64c0dbc9975516bbf4f6195c9b21 91294c4f4f575b3e7864e1651d5dea24dad19743
python3 scripts/castiron/custom_code_report.py report \
--base cc532b3f173e64c0dbc9975516bbf4f6195c9b21 \
--head 91294c4f4f575b3e7864e1651d5dea24dad19743 --fetch --require-head-hash --public \
--out /tmp/castiron-custom-code-91294c4f4f57
cat /tmp/castiron-custom-code-91294c4f4f57/custom-code.patchThis is the current full custom patch for mixed files, not an attribution of only the handwritten lines changed by this PR. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8e6c5b1124
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| '@napi-rs/wasm-runtime@1.2.3': | ||
| resolution: {integrity: sha512-UMduMbqO5s5zF2NkNacMT/yK5Y5QiKvWr2+50bzIIxFDwVJ2h49b+oyjaCGPhJxd2/gC2x39EHv/gHVuu36x2Q==} |
There was a problem hiding this comment.
Remove the unrelated WASM runtime upgrade
This upgrades @napi-rs/wasm-runtime from 1.2.2 to 1.2.3 even though its sole changed consumer is @rolldown/binding-wasm32-wasi, not the updated Next.js dependency graph. That expands this dependency-only change to an unrequested tooling transitive and bypasses the focused provenance/compatibility review expected for that package; retain 1.2.2 and limit the lockfile update to Next and its actual closure.
AGENTS.md reference: AGENTS.md:L150-L153
Useful? React with 👍 / 👎.
| next: | ||
| specifier: ^16.3.0 | ||
| version: 16.3.0(@babel/core@7.29.7)(@types/node@26.2.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) | ||
| version: 16.3.1(@babel/core@7.29.7)(@types/node@26.2.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) |
There was a problem hiding this comment.
Defer Next until the release cooldown expires
On this commit's 2026-08-24 timestamp, Next 16.3.1 is less than eight days old—the included release history contains changes from 2026-08-19—so this resolution violates minimumReleaseAge: 11520 with minimumReleaseAgeStrict: true. In the current review window, the frozen install executed by .github/workflows/ci.yml:251 therefore cannot accept this version under the repository's dependency policy; regenerate the update after the configured cooldown or obtain the required policy exception.
AGENTS.md reference: AGENTS.md:L150-L153
Useful? React with 👍 / 👎.
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. |
Bumps [next](https://github.com/vercel/next.js) from 16.3.0 to 16.3.1. - [Release notes](https://github.com/vercel/next.js/releases) - [Commits](vercel/next.js@v16.3.0...v16.3.1) --- updated-dependencies: - dependency-name: next dependency-version: 16.3.1 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
0e9a59d to
91294c4
Compare
Bumps next from 16.3.0 to 16.3.1.
Release notes
Sourced from next's releases.
... (truncated)
Commits
3d32eb8v16.3.12b4b1ec[backport] Revert i18n localization change for dynamic Pages API routes (#949...228df5f[backport] Retain fewer stale cache versions and use a TTL, plus the mtime fa...16eab3a[backport] Fix: Optimistic routing bugs leading to repeated prefetch loops (#...75548c9[backport] Fix Nav Inspector request loop on repeat captures (#97326)f6bd714[backport] [test] Compile the middleware redirect routes up front in dev (#97...43c1c60[16.3] [ci] Use OIDC tokens to read private preview builds (#97258)9dbb357[backport] Encode the cache item name built byunstable_cache(#97313)323a17c[backport] Discard only cache entries that predate a tag revalidation, and re...6d67f46[backport] Keep the dev validation worker alive across HMR updates (#97315)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)