Changesets 3.0.0-next.6

3.0.0-next.6Pre-release
Added 4
  • Support {commit-short} placeholder for the snapshot.prereleaseTemplate config, which is a 7 character variant of {commit}
  • Add a changeset publish-plan command to inspect which packages would be published or tagged, with optional JSON output
  • Add a changeset pack command that writes publishable package tarballs plus an enriched publish-plan.json into a directory
  • Add changeset publish --from-pack-dir <dir> to publish packages from a previously created pack output directory
Changed 4
  • Set supported package manager versions in engines field, including npm >=10.9.0, pnpm >=10.0.0, and yarn >=4.5.2
  • Order releases into dependency-aware chunks so packages are grouped in publish order
  • Show if a package is private when selecting packages in changeset add
  • For pnpm projects, match pnpm's native registry behavior more closely during unpublished package checks by ignoring both scope-based publishConfig registry overrides and publishConfig.registry
Fixed 5
  • Fix changeset publish to respect ignored packages for both publishing and private package tagging
  • Fix publish error printing for pnpm 11
  • Auto-create the directory for the target publish plan file when executing changeset publish-plan --output <file>
  • Fix accidental success logs on failed npm publishes
  • Log New tag: ... messages when running changeset publish to fix compatibility with the Changesets release GitHub action

From Changesets

Major Changes
  • #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.
Minor Changes

  • #2068 d03ffc1 Thanks @bluwy! - Support {commit-short} placeholder for the snapshot.prereleaseTemplate config, which is a 7 character variant of {commit}

  • #2061 c2db1dd Thanks @Andarist! - Added a changeset publish-plan command to inspect which packages would be published or tagged, with optional JSON output.

  • #2100 90b4ad0 Thanks @Andarist! - Order releases into dependency-aware chunks so packages are grouped in publish order.

  • #2063 ed77176 Thanks @Andarist! - Added changeset publish --from-pack-dir <dir> to publish packages from a previously created pack output directory.

  • #2062 830443c Thanks @Andarist! - Added a changeset pack command that requires --out-dir and writes publishable package tarballs plus an enriched publish-plan.json into that directory, either from the current workspace or from a saved publish plan via --from-plan.

  • #2073 b9cbd80 Thanks @bluwy! - Show if a package is private when selecting packages in changeset add

Patch Changes

  • #2060 11bded4 Thanks @Andarist! - Fixed changeset publish to respect ignored packages for both publishing and private package tagging.

  • #2064 ffd65fc Thanks @Andarist! - For pnpm projects, Changesets now match pnpm's native registry behavior more closely during unpublished package checks. Both scope-based publishConfig registry overrides and publishConfig.registry are now ignored.

  • #2113 b8222e6 Thanks @Andarist! - Fixed publish error printing for pnpm 11.

  • #2111 124ad07 Thanks @Andarist! - Auto-create the directory for the target publish plan file when executing changeset publish-plan --output <file>

  • #2113 b8222e6 Thanks @Andarist! - Fixed accidental success logs on failed npm publishes

  • #2091 3918fe5 Thanks @bluwy! - Log "New tag: ..." messages when running changeset publish to fix compatibility with the Changesets release GitHub action to create GitHub releases and push the new tags

  • Updated dependencies [694396c, d03ffc1, 01f4da4, c2348fc]:

    • @changesets/apply-release-plan@8.0.0-next.6
    • @changesets/assemble-release-plan@7.0.0-next.6
    • @changesets/read@1.0.0-next.6
View original

Upgraded? How did it go?

Discussion