chore(deps): update Next.js to 15.5.21 - #206
Merged
Merged
Conversation
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
^15.5.0to^15.5.21.@next/envand platform@next/swc-*packages.mainand contains one dependency-only commit.Why
The live Dependabot baseline has eight open Next.js alerts (#8-#15) whose first patched version is 15.5.21. PR #202 updated Next.js but its refreshed lockfile also moved unrelated
@emnapi/runtime,caniuse-lite,nanoid, andsemverentries. This replacement preserves the approved two-file boundary and leaves those unrelated packages unchanged.Alert closure is expected only after merge and a separate live Dependabot readback; this PR does not claim that alerts are already closed.
Review Of What Was Built
/and/u/octocat, with expected route content.Cleanup Review
No cleanup or refactor was performed. The patch intentionally excludes the unrelated lockfile upgrades present in PR #202.
Verification Summary
All package-manager, cache, HOME, XDG, temporary, Corepack, pnpm, and uv state was redirected to disposable isolated directories.
pnpm install --frozen-lockfile --store-dir <isolated-store>— passed.pnpm typecheck— passed.pnpm build— passed with Next.js 15.5.21./and/u/octocat— HTTP 200 with expected markers.python -m pytest -q -p no:cacheprovider tests/test_api_only.py— 14 passed.ruff check src/ tests/on Python 3.11 and 3.12 — passed.git diff --checkand full lockfile audit — passed; exactlyweb/package.jsonandweb/pnpm-lock.yamlchanged.Shipped Summary
The branch resolves Next.js 15.5.21 with only the required Next.js package-family lockfile changes. It is not merged and has not altered branch protection, reviews, or alerts.
Next Phase
Run fresh required checks and obtain one eligible independent approval on this exact head. Reviewer focus: confirm the two-file boundary, the absence of unrelated lockfile churn from PR #202, and the Next.js 15.5.21 resolution.
Remaining Roadmap
After separately authorized protected merge, re-read Dependabot state to confirm exact alert closure. Current expectation: alerts #8-#15 close, leaving sharp #7 and postcss #16-#17 open.