fix(deps): update nextjs monorepo to v16.3.0 - #39
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/nextjs-monorepo
branch
3 times, most recently
from
July 4, 2026 03:08
9e84653 to
a301c9b
Compare
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/nextjs-monorepo
branch
from
July 12, 2026 18:43
a301c9b to
e8397d9
Compare
renovate
Bot
force-pushed
the
renovate/nextjs-monorepo
branch
from
July 21, 2026 17:55
e8397d9 to
c51f202
Compare
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/nextjs-monorepo
branch
from
July 25, 2026 23:34
c51f202 to
64ea332
Compare
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/nextjs-monorepo
branch
from
August 7, 2026 04:08
64ea332 to
cc0da8c
Compare
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/nextjs-monorepo
branch
from
August 13, 2026 03:30
cc0da8c to
bad6426
Compare
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.
This PR contains the following updates:
16.2.7→16.3.016.2.7→16.3.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
vercel/next.js (eslint-config-next)
v16.3.0Compare Source
v16.2.12Compare Source
v16.2.11Compare Source
v16.2.10Compare Source
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.3.0Compare Source
v16.2.12Compare Source
v16.2.11Compare Source
v16.2.10Compare Source
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.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.