chore(deps): update dependency @changesets/cli to v2.29.8

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@changesets/cli (source)	2.29.4 -> 2.29.8

---

Release Notes

changesets/changesets (@​changesets/cli)

v2.29.8

Compare Source

v2.29.7

Compare Source

Patch Changes

• Updated dependencies [957f24e]:
  • @​changesets/apply-release-plan@​7.0.13

v2.29.6

Compare Source

Patch Changes

• #​1712 a3563b0 Thanks @​benmccann! - Switch to maintained fork of external-editor

v2.29.5

Compare Source

Patch Changes

• #​1693 6352819 Thanks @​Andarist! - Fixed an issue with workspace:^ and workspace:~ dependency ranges not being semantically treated as, respectively, ^CURRENT_VERSION and ~CURRENT_VERSION. This led to dependent packages being, at times, bumped too often when their dependencies with those ranges were bumped.

• Updated dependencies [6352819]:

  • @​changesets/assemble-release-plan@​6.0.9
  • @​changesets/get-release-plan@​4.0.13

---

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

[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 13 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 32, reused 0, downloaded 0, added 0
Progress: resolved 99, reused 0, downloaded 0, added 0
Progress: resolved 102, reused 0, downloaded 0, added 0
Progress: resolved 155, reused 0, downloaded 0, added 0
Progress: resolved 280, reused 0, downloaded 0, added 0
Progress: resolved 410, reused 0, downloaded 0, added 0
Progress: resolved 502, reused 0, downloaded 0, added 0
Progress: resolved 737, reused 0, downloaded 0, added 0
Progress: resolved 953, reused 0, downloaded 0, added 0
Progress: resolved 1039, reused 0, downloaded 0, added 0
Progress: resolved 1268, reused 0, downloaded 0, added 0
Progress: resolved 1513, reused 0, downloaded 0, added 0
 ERR_PNPM_PATCH_NOT_APPLIED  The following patches were not applied: @changesets/[email protected]

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: 459a366

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

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
nextra-theme-docs-dev	Error			Dec 6, 2025 7:22am
nextra-v2	Error			Dec 6, 2025 7:22am

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
nextra	Ignored	Preview		Dec 6, 2025 7:22am