chore(deps): bump next from 16.0.7 to 16.2.7#318
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
commit: |
Contributor
Author
|
Dependabot can't resolve your JavaScript dependency files. Because of this, Dependabot cannot update this pull request. |
2 similar comments
Contributor
Author
|
Dependabot can't resolve your JavaScript dependency files. Because of this, Dependabot cannot update this pull request. |
Contributor
Author
|
Dependabot can't resolve your JavaScript dependency files. Because of this, Dependabot cannot update this pull request. |
Bumps [next](https://github.com/vercel/next.js) from 16.0.7 to 16.2.7. - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v16.0.7...v16.2.7) --- updated-dependencies: - dependency-name: next dependency-version: 16.2.6 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
80bee1d to
aeb751b
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.
Bumps next from 16.0.7 to 16.2.7.
Release notes
Sourced from next's releases.
... (truncated)
Commits
9bd3c26v16.2.7c63224f[backport] feat(turbopack): add LocalPathOrProjectPath PostCSS config resolut...63115c7[16.2.x] Don't dropFormDataentries (#94240)aef22fd[backport] Propagate adapter preferred regions (#94200)f126e72[backport] Fix "type: module" in project dir when using standalone or adapter...bda3e2a[ci] Disable hanging node 24 typescript tests on 16.2 backport branch (#94164)7e16e07[backport] Turbopack: switch from base40 to base38 hash encoding (#93932)6139f4b[backport] Fix server action forwarding loop with middleware rewrites (#93919)c021d10[backport] Encode non-ASCII characters in cache tags at construction (#93918)9184ddb[backport] Fix catch-allrouter.querycorruption withbasePath+ `rewrite...Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for next since your current version.
Note
Medium Risk
Framework upgrade spanning multiple examples with security fixes in Next 16.2.x; behavior may shift around middleware, caching, and server actions even though application source is unchanged.
Overview
Bumps Next.js from 16.0.7 to 16.2.7 in
examples/kitchen-sinkand refreshespnpm-lock.yamlso every workspace that resolvesnext(includinglatesttelemetry examples) lands on 16.2.7 instead of 16.2.6 or the removed 16.0.7 entry.The lockfile change also drops the deprecated vulnerable
next@16.0.7package record and pulls in Next’s updated optional stack (e.g.@next/env/ platform@next/swc-*at 16.2.7, sharp 0.34.5, refreshed caniuse-lite / baseline-browser-mapping), plus minor transitive bumps such as turbo 2.9.16 where referenced by tooling.Reviewed by Cursor Bugbot for commit aeb751b. Bugbot is set up for automated code reviews on this repo. Configure here.