Repository navigation
chore(deps): upgrade Next.js to 16.3.8 - #144
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Mogplex PR ReviewStatus: No material issues found Approve-ready: this is a correct and complete security bump of Affected files
Suggestions
|
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.
Upgrade Next.js from 16.3.6 to 16.3.8 and match eslint-config-next to 16.3.8. Regenerate the pnpm lockfile so the runtime, env helper, SWC packages, and Next ESLint plugin resolve the requested patch version.
Next.js 16.3.8 release notes
Validation: pnpm lint, pnpm types:check, all 18 existing tests, and pnpm build passed on Node 22.23.3. Verified installed Next.js and eslint-config-next are both 16.3.8.
No-tests: Dependency-only patch upgrade; existing tests/*.test.mjs, typecheck, lint, and production build cover the docs content and build contract.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.