Update dependency @edge-runtime/primitives to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@edge-runtime/primitives (source)	5.1.1 -> 6.0.0

---

Release Notes

vercel/edge-runtime (@​edge-runtime/primitives)

v6.0.0

Compare Source

Major Changes

• drop node16 (#​1045)

v5.1.1

Compare Source

Patch Changes

• force bumping primitives as format changed and it didn't trigger a rebuild (#​1027)

v5.1.0

Compare Source

Minor Changes

• remove custom entries() iterator in favor of Undici's default implementation (#​942)

  The difference will be that set-cookie headers will be emitted independently.

  const headers = new Headers()
  headers.append('set-cookie', 'a=1')
  headers.append('set-cookie', 'b=2')
  
  const entries = [...headers.entries()]
  
  // previous implementation
  console.log(entries) // [["set-cookie", "a=1, b=2"]]
  
  // new implementation (undici's native implementation)
  console.log(entries) // [["set-cookie", "a=1"], ["set-cookie", "b=2"]]

v5.0.1

Compare Source

Patch Changes

• minify source texts (#​925)

v5.0.0

Compare Source

Major Changes

• use MIT license (#​909)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

Summary by Sourcery

Build:

• Update @edge-runtime/primitives dependency to version 6.0.0 in package.json.

[renovate]

⚠️ 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:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

Scope: all 21 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
bench/vercel                             |  WARN  deprecated [email protected]
/tmp/renovate/repos/github/X-oss-byte/Nextjs/packages/next-swc/crates/next-dev-tests/tests:
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/@turbo%2Fpack-test-harness: Not Found - 404

This error happened while installing a direct dependency of /tmp/renovate/repos/github/X-oss-byte/Nextjs/packages/next-swc/crates/next-dev-tests/tests

@turbo/pack-test-harness is not in the npm registry, or you have no permission to fetch it.

No authorization header was set for the request.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c68d820

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR updates the @edge-runtime/primitives dependency from version 5.1.1 to 6.0.0 in the Next.js package. The major version bump is primarily due to dropping Node.js 16 support and includes several changes from previous versions including modifications to set-cookie header handling and licensing updates.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Dependency version update with breaking changes	Updates @edge-runtime/primitives from 5.1.1 to 6.0.0 Drops support for Node.js 16 Changes set-cookie headers behavior to emit independently instead of combining them Updates to MIT license	packages/next/package.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. Here's why:

• It seems to have been created by a bot (hey, renovate[bot]!). We assume it knows what it's doing!
• We don't review packaging changes - Let us know if you'd like us to change this.