fix(deps): update next to v15.1.7

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@next/eslint-plugin-next (source)	15.1.6 -> 15.1.7
next (source)	15.1.6 -> 15.1.7

---

Release Notes

vercel/next.js (@​next/eslint-plugin-next)

v15.1.7

Compare Source

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

Core Changes

• fix: work around setTimeout memory leak, improve wrappers (#​75727)
• add additional x-middleware-set-cookie filtering (#​75869)
• fix: ensure lint worker errors aren't silenced (#​75766)

Credits

Huge thanks to @​lubieowoce and @​ztanner for helping!

vercel/next.js (next)

v15.1.7

Compare Source

---

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), 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 these updates again.

---

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

---

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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nextra-theme-docs-dev	❌ Failed (Inspect)			Feb 15, 2025 0:43am
nextra-v2	❌ Failed (Inspect)			Feb 15, 2025 0:43am

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
nextra	⬜️ Ignored (Inspect)	Visit Preview		Feb 15, 2025 0:43am

[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 12 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 37, reused 0, downloaded 0, added 0
Progress: resolved 102, reused 0, downloaded 0, added 0
Progress: resolved 103, reused 0, downloaded 0, added 0
Progress: resolved 104, reused 0, downloaded 0, added 0
Progress: resolved 212, reused 0, downloaded 0, added 0
Progress: resolved 337, reused 0, downloaded 0, added 0
Progress: resolved 594, reused 0, downloaded 0, added 0
Progress: resolved 688, reused 0, downloaded 0, added 0
Progress: resolved 737, reused 0, downloaded 0, added 0
Progress: resolved 1003, reused 0, downloaded 0, added 0
Progress: resolved 1074, reused 0, downloaded 0, added 0
Progress: resolved 1232, reused 0, downloaded 0, added 0
Progress: resolved 1335, reused 0, downloaded 0, added 0
 ERR_PNPM_PATCH_NOT_APPLIED  The following patches were not applied: next@15.1.6

Either remove them from "patchedDependencies" or update them to match packages in your dependencies.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 63f28ef

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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