fix(deps): update nextjs monorepo to v16.2.9#144
Merged
Conversation
✅ Deploy Preview for semantic-template ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
happy-haki
approved these changes
Jun 17, 2026
happy-haki
left a comment
happy-haki
left a comment
Contributor
There was a problem hiding this comment.
Maintainer check: patch-level Next.js monorepo update. npm publish times for next/eslint-config-next/@next/env 16.2.9 are 2026-06-09T23:01-23:02Z, which is older than the 2026-06-10T00:30Z 7-day cutoff. Local gates passed: pnpm install --frozen-lockfile, pnpm lint, pnpm build.
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
1 participant
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.
This PR contains the following updates:
16.2.7→16.2.916.2.7→16.2.9Release Notes
vercel/next.js (@next/mdx)
v16.2.9Compare Source
Empty release to ensure
next@latestpoints at a stable release. Next.js only allows publishing with Trusted Publishing enabled. In order to fix NPM dist-tags, we have to release a new version. Updating dist-tags is not possible with Trusted Publishing.v16.2.8Compare Source
Release with no changes in an attempt to fix
next@latestpointing at a prerelease version.vercel/next.js (next)
v16.2.9Compare Source
v16.2.8Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.