chore(deps)(deps-dev): Bump @changesets/cli from 2.31.1 to 3.0.0

[dependabot]

Bumps @changesets/cli from 2.31.1 to 3.0.0.

Changelog

Sourced from @​changesets/cli's changelog.

3.0.0

Major Changes

• #21287113c01 Thanks @​Andarist! - Renamed the changeset tag command to changeset git-tag.

• #20743599e47 Thanks @​bluwy! - Set supported package manager versions in "engines" field, including npm >=10.9.0, pnpm >=10.0.0, and yarn >=4.5.2.

• #186092b1c1b Thanks @​mixelburg! - changeset version now exits with code 1 when there are no unreleased changesets, instead of silently exiting with code 0.

  This makes it easier to detect when a version step is a no-op — for example, to prevent accidentally publishing packages with incorrect version tags when using --snapshot mode.

• #1482df424a4 Thanks @​Andarist! - Bumped supported Node versions to ^22.11 || ^24 || >=26

• #1994062530b Thanks @​bluwy! - The prettier option in .changeset/config.json has been removed in favor of format. format supports "auto", "prettier", "oxfmt", "deno", and "dprint", and false disables formatting. If you previously used prettier: false, migrate to format: false or remove the option to use automatic formatter detection.

• #219096b65ee Thanks @​bluwy! - Move versioned prerelease changesets to .changeset/pre/ folder instead of accumulating in the root and tracking the versioned changeset ids in the .changeset/pre.json file. Existing pre.json will auto-migrate to this new structure on the next run of changeset version or when calling changeset status.

  This change allows easier management of versioned prerelease changesets (for the final stable release) and current queued changesets (for the next prerelease). Changesets in .changeset/pre/ can be edited or deleted depending if it's still relevant for the final stable release of a package. There's no need to synchronize the changeset ids in pre.json if certain changesets are deleted.

• #2145f5887ff Thanks @​Andarist! - Removed Yarn Classic support

• #20978c88f6a Thanks @​Andarist! - Packages with only prerelease versions published will now be published with the prerelease tag in the prerelease mode if the target registry doesn't auto-assign latest tag. npm registry itself does that and such packages will continue to be released with latest tag (and not with the configured prerelease tag).

• #1879c76b232 Thanks @​beeequeue! - Removed warning messages about using v1 configs. They will now be silently ignored.

• #1655db46911 Thanks @​bluwy! - Update @manypkg/get-packages which drops support for detecting packages in Bolt monorepos and adds support for npm monorepos

• #1651e1df862 Thanks @​bluwy! - Remove support for the --sinceMaster flag for changeset status. Use --since=master or --since=main instead.

• #2117813bbf3 Thanks @​bluwy! - Remove the pre.jsoninitialVersions property and handling as it's unused internally

• #196107278a7 Thanks @​beeequeue! - CommitFunctions can now be both sync and async, and the defaultCommitFunctions are now sync.

• #1482df424a4 Thanks @​Andarist! - From now on this package is going to be published as ES module.

• #1652a0b5326 Thanks @​bluwy! - Remove support for the deprecated ___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH.useCalculatedVersionForSnapshots config. The snapshot.useCalculatedVersion config should be used instead.

• #21863910adf Thanks @​Andarist! - Private packages are no longer versioned by default. Set privatePackages to true to opt into versioning and tagging them, or set privatePackages.version to true to version them without tagging.

• #1879c76b232 Thanks @​beeequeue! - Migrated from enquirer + @inquirer/launch-editor to @clack/prompts + launch-editor.

  This means the CLI flows will have minor changes, but they are largely the same.

  This change also fixes various issues related to enquirer like cancelling prompts crashing the CLI.

• #20903aae903 Thanks @​beeequeue! - Peer dependencies now bump packages that depend on them by patch instead of major.

  This means a peer dependency update is no longer assumed (forced) to be a breaking change.

... (truncated)

Commits

• f442221 Version Packages (#2235)
• e3facad Version Packages (next) (#2228)
• c98af4c Do not bump ignored independent packages when exiting pre mode (#2092)
• 496ca21 Build(deps-dev): Bump the development-dependencies group with 6 updates (#2225)
• d1053ac Build(deps): Bump the production-dependencies group across 1 directory with 2...
• 68ea6ec Fix linked and fixed glob patterns expansion (#2222)
• c1b6f8c fix missing coloring of name (#2218)
• a53d1f8 Remove old atlaskit changelogs (#2217)
• 7bcb2d2 Build(deps-dev): Bump the development-dependencies group across 1 directory w...
• baa658d Version Packages (next) (#2192)
• Additional commits viewable in compare view

[os-project-manager]

Do not merge this PR as it stands — and the green CI is not the reason to think otherwise.

PR CI never runs changeset version, changeset publish, or the RC cut. It proves the workspace still installs; it says nothing about whether releases still work. The v3 breaking changes land squarely on machinery this repo has built on v2's semantics:

• changeset version now exits 1 on a no-op, and pnpm run version is a && chain (changeset version && sync-protocol-version.mjs && …).
• Consumed prerelease changesets move to .changeset/pre/ instead of accumulating in the root — which is what cut-rc.yml's enforced file allowlist ("76 package.json, 76 CHANGELOG.md, .changeset/pre.json, zero deletions") and check-changeset-no-major.mjs's RC exemption are both built on.
• privatePackages no longer defaults to versioning; the sibling of our ___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH key was removed.

The upgrade is worth doing — v3 removes the root cause of the RC-window pollution behind ~88 lines of exemption logic, and its exit-1 targets the silent-green release stall of #4898. So it is scheduled as a migration rather than dropped: #9465, which carries the bump and every consequential change in one PR, because both half-states (bump without migration, migration without bump) are broken silently until the next release.

This PR is superseded by that card and will close itself once main carries ^3.0.0. Sibling #9208 (changesets/action v1 → v2) is resolved inside the same card rather than separately — two open PRs mutating one machine is the shape to avoid.

---

Generated by Claude Code

[dependabot]

Looks like @changesets/cli is up-to-date now, so this is no longer needed.