Skip to content

chore(deps-dev): bump @changesets/cli from 2.31.1 to 3.0.1 - #1264

Closed
dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/npm_and_yarn/changesets/cli-3.0.1
Closed

chore(deps-dev): bump @changesets/cli from 2.31.1 to 3.0.1#1264
dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/npm_and_yarn/changesets/cli-3.0.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 24, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps @changesets/cli from 2.31.1 to 3.0.1.

Release notes

Sourced from @​changesets/cli's releases.

@​changesets/cli@​3.0.1

Patch Changes

@​changesets/cli@​3.0.0

Major Changes

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

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

  • #1860 92b1c1b 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.

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

  • #1994 062530b 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.

  • #2190 96b65ee 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.

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

  • #2097 8c88f6a 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).

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

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

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

  • #2117 813bbf3 Thanks @​bluwy! - Remove the pre.json initialVersions property and handling as it's unused internally

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

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

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

  • #2186 3910adf 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.

  • #1879 c76b232 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.

... (truncated)

Changelog

Sourced from @​changesets/cli's changelog.

3.0.1

Patch Changes

3.0.0

Major Changes

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

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

  • #1860 92b1c1b 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.

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

  • #1994 062530b 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.

  • #2190 96b65ee 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.

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

  • #2097 8c88f6a 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).

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

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

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

  • #2117 813bbf3 Thanks @​bluwy! - Remove the pre.json initialVersions property and handling as it's unused internally

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

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

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

  • #2186 3910adf 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.

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

... (truncated)

Commits

@dependabot dependabot Bot added the dependencies Dependency bumps and lockfile changes label Aug 24, 2026
@dependabot @github

dependabot Bot commented on behalf of github Aug 24, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: automated. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot dependabot Bot added skip-changeset PR ships nothing to users (pure CI/docs chore) — changeset gate waived dependencies Dependency bumps and lockfile changes labels Aug 24, 2026
@dependabot dependabot Bot mentioned this pull request Aug 24, 2026
Closed
@vercel

vercel Bot commented Aug 24, 2026 •
edited
Loading

Copy link
Copy Markdown

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

1 Skipped Deployment
Project Deployment Actions Updated
hotcrm Ignored Ignored Sep 3, 2026 1:32am UTC

Request Review

This was referenced Aug 25, 2026
Closed
Closed
Closed
Closed
This was referenced Aug 25, 2026
Closed
Closed
Closed
Closed
Closed
@os-steve os-steve mentioned this pull request Aug 27, 2026
Open
@dependabot @github

dependabot Bot commented on behalf of github Aug 27, 2026

Copy link
Copy Markdown
Contributor Author

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot recreate.

@dependabot
chore(deps-dev): bump @changesets/cli from 2.31.1 to 3.0.1
0a14d45 
Bumps [@changesets/cli](https://github.com/changesets/changesets/tree/HEAD/packages/cli) from 2.31.1 to 3.0.1.
- [Release notes](https://github.com/changesets/changesets/releases)
- [Changelog](https://github.com/changesets/changesets/blob/main/packages/cli/CHANGELOG.md)
- [Commits](https://github.com/changesets/changesets/commits/@changesets/cli@3.0.1/packages/cli)

---
updated-dependencies:
- dependency-name: "@changesets/cli"
  dependency-version: 3.0.1
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/changesets/cli-3.0.1 branch from 49ea8b2 to 0a14d45 Compare September 1, 2026 03:05
@hotlong hotlong mentioned this pull request Sep 3, 2026
Closed
@hotlong Claude

hotlong commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

⛔ Reviewed by the repo:hotcrm seat (R26) — do not merge this as a bare bump. Holding it open; the work it needs is tracked in #1503.

@changesets/cli 3.0.0 carries 18 breaking changes. One of them is decisive here:

Private packages are no longer versioned by default.

This repo's package.json declares "private": true alongside "version": "3.0.0" — hotcrm is a single private package that versions itself through changesets, and .changeset/config.json sets no privatePackages option, so on 3.x it would take the new default.

⭐ The failure mode is silence. changeset version would stop bumping the version and stop generating CHANGELOG.md while exiting successfully. Nothing in PR CI exercises the release path, so this PR's green cannot see it — the first observation point is the next release, which is a human-gated action.

Two more that need action in the same change: 3.0.0 requires Node ^22.11 || ^24 || >=26 while this repo declares "node": ">=22" (which admits 22.0–22.10), and changeset version now exits 1 rather than 0 when there is nothing to release — which compounds with the first finding.

Fourteen of the eighteen were measured against this repo and genuinely do not apply (the prettier option is unset here, changeset tag is never called, --sinceMaster is not used, pnpm is already 10.33.0, the CLI is never imported programmatically). Full breakdown on #1503 so it does not have to be re-derived.

⚠️ For the record: the private-package finding is a reading of the documented breaking change, not a measurement — this seat did not run changeset version against 3.0.1. Verifying it empirically is the first task on #1503, and "it does not affect a single-package repo after all" is a fine outcome that would shrink #1503 back to a plain bump and let this PR merge.

⛔ Not closing this PR. When a 3.x upgrade lands properly, dependabot will close it on its own.

Generated by Claude Code

@os-zhuang os-zhuang mentioned this pull request Sep 5, 2026
Closed
This was referenced Sep 5, 2026
Closed
Closed
@claude claude Bot mentioned this pull request Sep 7, 2026
Merged
10 tasks done
os-zhuang pushed a commit that referenced this pull request Sep 7, 2026
@claude
chore(deps-dev): take @changesets/cli 3.x properly, not as a bare bump
5a45d1f 
`@changesets/cli` 3.0.0 ships 18 breaking changes. Three land on this repo and
two of them land silently, which is why dependabot's bare bump (PR #1264) could
not be merged on its green.

Private packages are no longer versioned by default. `hotcrm` is `private: true`
and versions itself through changesets; `CHANGELOG.md` is written by
`changeset version` and by nothing else. Measured on a private single-package
fixture with a pending changeset and no `privatePackages` option: the command
exits 0, prints "All files have been updated. Review them and commit at your
leisure", and leaves the version untouched, writes no `CHANGELOG.md`, and does
not consume the changeset. `.changeset/config.json` now sets
`privatePackages: { version: true, tag: false }` — the 2.x default, restored
explicitly.

The formatter option was renamed, so #1602's ruling had to be re-stated under
the new name. A leftover `prettier` key is accepted in silence — measured
through `validateConfig` from the installed `@changesets/config` 4.0.0: no
error, no warning, and `format` resolves to its `auto` default. `format: false`
now carries what `prettier: false` used to.

`changeset version` exits 1 when there is nothing to release (2.x exited 0), so
`pnpm changeset:version` goes through `scripts/changeset-version.mjs`. It keys
on the sentinel line the CLI prints on exactly that path, never on the exit code
alone, so a misspelled `--ignore` package, a malformed config or an unwritable
tree still exit non-zero.

`engines.node` moves from `>=22` to `^22.11 || ^24 || >=26`, which 3.x requires;
`>=22` admitted 22.0-22.10, which it rejects. `docs/STATUS.md` follows, and the
guard that binds the two learns to unescape the `\|` that markdown requires
inside a table cell — without which a `||` range can never agree with
package.json.

`test/changeset-version-wrapper.test.ts` runs the real CLI against a private
fixture carrying this repo's own config, so a future default cannot quietly
move either half back.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TezFG8ZMrNH6n5VTNpPpdH
@claude claude Bot mentioned this pull request Sep 7, 2026
Merged
10 tasks done
@os-zhuang os-zhuang mentioned this pull request Sep 7, 2026
Closed
@os-zhuang Claude

os-zhuang commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Superseded by #1740, merged 2026-09-07 14:26 UTC

@changesets/cli is now on ^3.0.1 (resolving to 3.0.2) on main as of
6d9fd0a4, so this PR's version bump is already in the tree.

This PR was not merged, and should not be. The bump on its own is not safe
here — 3.x's breaking changes land on this repo in two ways that produce no
error and no warning:

  1. Private packages are no longer versioned by default. hotcrm is
    private: true and versions itself through changesets. Measured on a private
    single-package fixture under this repo's pre-bump config and the installed
    3.0.2: changeset version exits 0, prints "All files have been updated.
    Review them and commit at your leisure"    , and leaves the version untouched,
    writes no CHANGELOG.md, and does not even consume the changeset.
    chore(deps-dev): take @changesets/cli 3.x properly, not as a bare bump #1740 restores the 2.x behaviour explicitly with
    privatePackages: { version: true, tag: false }.

  2. The prettier config key was removed in favour of format, silently.
    PR fix(changesets): stop re-formatting release notes that already shipped #1739 (merged 14:11) set prettier: false to stop changeset version
    re-formatting release notes that had already shipped. Under 3.x that key is
    ignored — not rejected, not warned about — and format falls back to its
    "auto" default. Merging this PR on top of fix(changesets): stop re-formatting release notes that already shipped #1739 would have quietly
    re-enabled the formatting fix(changesets): stop re-formatting release notes that already shipped #1739 exists to stop. chore(deps-dev): take @changesets/cli 3.x properly, not as a bare bump #1740 carries the same intent
    under the new name, format: false.

Two further things #1740 does that a bare bump does not: engines.node moves to
^22.11 || ^24 || >=26 (3.x rejects 22.0–22.10, which the old >=22 admitted),
and pnpm changeset:version goes through scripts/changeset-version.mjs because
changeset version now exits 1 when there is nothing to release.

Full measurement and the 18-breaking-change walkthrough are on #1740; the card
is #1503.

⛔ This comment does not close this PR. No rule in AGENTS.md authorises an
agent seat to close a dependabot PR, and dependabot normally closes its own PR
once the bump it proposed is on main. If it does not, a human can close it —
or comment ·@·d·ependabot c·lose — which is also why hotcrm#1058 is still open:
agent seats cannot issue dependabot commands (a U+00B7 is injected into bot
mentions; measured at codepoint level by two seats in two repositories).

Generated by Claude Code

@os-bill os-bill mentioned this pull request Sep 8, 2026
Merged
4 tasks done
@os-project-manager Claude

os-project-manager commented Sep 20, 2026

Copy link
Copy Markdown
Collaborator

Closed by the director seat (session_012GcsUbuqFGBibkEDMRC1eE), 2026-09-20T14:59Z, under the maintainer's instruction today, verbatim: 「1天之前的pr都帮我诊断修复继续处理完,并跟进到合并」. This bump is superseded: @changesets/cli ^3.0.1 is on main since #1740 (6d9fd0a4, 2026-09-07T14:26Z), with the two 3.x breaking changes handled there (private-package versioning, engines.node); the repo:hotcrm seat's review (5520795217) and the follow-up (5572108450) both say this PR must not merge as a bare bump. Nothing here lands; the tracked work was #1503. Dependabot did not close it on its own, so a seat closes it under the maintainer's instruction.

Generated by Claude Code

@dependabot @github

dependabot Bot commented on behalf of github Sep 20, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/changesets/cli-3.0.1 branch September 20, 2026 14:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Dependency bumps and lockfile changes skip-changeset PR ships nothing to users (pure CI/docs chore) — changeset gate waived

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@hotlong @os-zhuang @os-project-manager