You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Empty release to ensure next@latest points 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.
Maintainer check 2026-06-11: holding this PR for now. Local gates on main pass with Next 16.2.7, but this PR targets next/@next/mdx 16.2.9, published 2026-06-09T23:02Z, so it does not satisfy our 7-day npm age rule yet (cutoff: 2026-06-04T00:30Z). Netlify deploy-preview checks are also failing. Will revisit after the package age window and green checks.
Maintainer cleanup: closing this Renovate dependency PR instead of merging now. The target package version is still younger than the repo's 7-day dependency-age policy and/or its preview checks are not clean. Main currently passes local install/check/build, so keeping the repo green and PR queue empty. Renovate can propose a fresh update after the version has aged or a newer qualifying version exists.
Closing during maintainer cleanup to keep PR queue at 0 while preserving build stability. Target update is not eligible for merge under the 7-day dependency-age policy and/or has failing preview checks.
Because you closed this PR without merging, Renovate will ignore this update (^16.2.7). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.
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
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.
renovate
Bot
force-pushed
the
renovate/nextjs-monorepo
branch
from
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.