Skip to content

chore(deps): bump @next/third-parties from 16.2.0 to 16.2.1#213

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/next/third-parties-16.2.1
Open

chore(deps): bump @next/third-parties from 16.2.0 to 16.2.1#213
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/next/third-parties-16.2.1

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot bot commented on behalf of github Mar 20, 2026

Bumps @next/third-parties from 16.2.0 to 16.2.1.

Release notes

Sourced from @​next/third-parties's releases.

v16.2.1

[!NOTE] This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • docs: post release amends (#91715)
  • docs: fix broken Activity Patterns demo link in preserving UI state guide (#91698)
  • Fix adapter outputs for dynamic metadata routes (#91680)
  • Turbopack: fix webpack loader runner layer (#91727)
  • Fix server actions in standalone mode with cacheComponents (#91711)
  • turbo-persistence: remove Unmergeable mmap advice (#91713)
  • Fix layout segment optimization: move app-page imports to server-utility transition (#91701)
  • Turbopack: lazy require metadata and handle TLA (#91705)
  • [turbopack] Respect {eval:true} in worker_threads constructors (#91666)

Credits

Huge thanks to @​icyJoseph, @​abhishekmardiya, @​ijjk, @​mischnic, @​unstubbable, @​sokra, and @​lukesandberg for helping!

v16.2.1-canary.4

Core Changes

  • Fix adapter outputs for dynamic metadata routes: #91680

Misc Changes

  • Turbopack: fix webpack loader runner layer: #91727
  • [turbopack] Remove incorrect debug_assert in try_read_task_cell: #91699
  • Add module count field to module graph tracing spans: #91697
  • turbopack-cli: add --persistent-caching flag for filesystem-backed cache: #91657
  • Turbopack: pull in updated vercel/nft tests: #91651
  • Update Rspack development test manifest: #91695
  • [test] Unflake use-node-streams-env-precedence test: #91733
  • Update Rspack production test manifest: #91694
  • [turbopack] Improve regressed build speed on cross-compiled MUSL: #91477

Credits

Huge thanks to @​ijjk, @​mischnic, @​sokra, @​vercel-release-bot, @​unstubbable, and @​mmastrac for helping!

v16.2.1-canary.3

Core Changes

  • Fix layout segment optimization: move app-page imports to server-utility transition: #91701
  • Fix server actions in standalone mode with cacheComponents: #91711
  • Turbopack: lazy require metadata and handle TLA: #91705

Misc Changes

  • [turbopack] Optimize compaction cpu usage: #91468

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [@next/third-parties](https://github.com/vercel/next.js/tree/HEAD/packages/third-parties) from 16.2.0 to 16.2.1.
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](https://github.com/vercel/next.js/commits/v16.2.1/packages/third-parties)

---
updated-dependencies:
- dependency-name: "@next/third-parties"
  dependency-version: 16.2.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file frontend Frontend/UI changes labels Mar 20, 2026
@vercel
Copy link
Copy Markdown

vercel bot commented Mar 20, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
volvox-website Ready Ready Preview, Comment Mar 20, 2026 11:36pm

Request Review

@claude
Copy link
Copy Markdown
Contributor

claude bot commented Mar 20, 2026

Claude encountered an error —— View job


I'll analyze this and get back to you.

@greptile-apps
Copy link
Copy Markdown

greptile-apps bot commented Mar 20, 2026

Greptile Summary

This PR is a routine patch bump of @next/third-parties from 16.2.0 to 16.2.1, generated by Dependabot. The change is limited to updating the version specifier in package.json and the resolved entry + integrity hash in pnpm-lock.yaml.

  • The 16.2.1 release is a backport-only patch that fixes adapter outputs for dynamic metadata routes, server actions in standalone mode with cacheComponents, and a layout segment optimization issue — no breaking changes.
  • Peer dependency requirements (next: ^13–16, react: ^18/19) remain unchanged.
  • The integrity hash in pnpm-lock.yaml has been correctly updated to match the new package version.
  • No application source code is affected.

Confidence Score: 5/5

  • This PR is safe to merge — it is a non-breaking patch dependency update with no source code changes.
  • The change is a pure patch-level dependency bump touching only package.json and pnpm-lock.yaml. The upstream release is explicitly described as a backport of bug fixes with no new features or breaking changes. Peer dependency constraints are unaltered and the lock file integrity hash is consistent.
  • No files require special attention.

Important Files Changed

Filename Overview
package.json Version specifier for @next/third-parties bumped from ^16.2.0 to ^16.2.1. No other changes.
pnpm-lock.yaml Lock file updated to reflect the new @next/third-parties@16.2.1 resolution with an updated integrity hash. All peer dependencies remain the same.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Dependabot detects\n@next/third-parties 16.2.1] --> B[Update package.json\nspecifier: ^16.2.0 → ^16.2.1]
    B --> C[Regenerate pnpm-lock.yaml\nresolution + integrity hash updated]
    C --> D{Peer dependencies\ncompatible?}
    D -- Yes\nnext ^13-16, react ^18/19 --> E[Safe to merge ✅]
    D -- No --> F[Conflict — not applicable here]
Loading

Last reviewed commit: "chore(deps): bump @n..."

@morph-subagents
Copy link
Copy Markdown

🤖 Morph Preview Test

Preview URL: https://volvox-website-m74iz0tj9-volvox-llc.vercel.app

AI Summary

Issues:

  • None found

Verified:

  • Google Tag Manager script loads correctly without console errors, confirming the @next/third-parties update is functional.
  • Navigation and visual integrity across Home, About, Blog, Community, and Products pages.
  • Mobile menu functionality and responsive layout in mobile viewport.

Recording

Preview Recording

View full session →


Automated testing by Morph

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file frontend Frontend/UI changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant