Update dependency next to v16.4.6 #21
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/next-16.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
16.4.1→16.4.6Release Notes
vercel/next.js (next)
v16.4.6Compare Source
Core Changes
Credits
Huge thanks to @lukesandberg and @eps1lon for helping!
v16.4.5Compare Source
This release contains security fixes for the following advisories:
Moderate
v16.4.4Compare Source
Core Changes
reads fallback params after a client navigationdeployment test (#100668)Credits
Huge thanks to @icyJoseph, @mischnic, @wbinnssmith, @lukesandberg, and @eps1lon for helping!
v16.4.3Compare Source
Core Changes
Credits
Huge thanks to @mischnic, @lukesandberg, @acdlite, @eps1lon, and @sokra for helping!
v16.4.2Compare Source
What's Changed
Full Changelog: https://github.com/vercel/next.js/compare/v16.4.1...v16.4.2
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 this update again.
This PR has been generated by Mend Renovate CLI.
⚠️ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below:
File name: web/package-lock.json
212ea82ddc2667920706Update dependency next to v16.4.2to Update dependency next to v16.4.32667920706362acdc993Update dependency next to v16.4.3to Update dependency next to v16.4.4362acdc9939b9f9d322bUpdate dependency next to v16.4.4to Update dependency next to v16.4.59b9f9d322bfe0f9dd1b4Update dependency next to v16.4.5to Update dependency next to v16.4.6View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.