{{ message }}
Repository navigation
Version Packages (next) - #2192
Merged
Merged
Conversation
changesets-org-version-bot
Bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
July 29, 2026 09:06
094cb00 to
b552f42
Compare
changesets-org-version-bot
Bot
force-pushed
the
changeset-release/main
branch
from
August 3, 2026 08:33
b552f42 to
53eb4bd
Compare
✅ Deploy Preview for changesets ready!To edit notification comments on pull requests, go to your Netlify project configuration. |
bluwy
approved these changes
Aug 3, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Aug 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
@changesets/apply-release-plan@8.0.0-next.10
Major Changes
#2190
96b65eeThanks @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.jsonfile. Existingpre.jsonwill auto-migrate to this new structure on the next run ofchangeset versionor when callingchangeset 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 inpre.jsonif certain changesets are deleted.Patch Changes
96b65ee,3910adf,96b65ee]:@changesets/assemble-release-plan@7.0.0-next.10
Major Changes
#2190
96b65eeThanks @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.jsonfile. Existingpre.jsonwill auto-migrate to this new structure on the next run ofchangeset versionor when callingchangeset 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 inpre.jsonif certain changesets are deleted.Patch Changes
96b65ee]:@changesets/cli@3.0.0-next.11
Major Changes
#2190
96b65eeThanks @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.jsonfile. Existingpre.jsonwill auto-migrate to this new structure on the next run ofchangeset versionor when callingchangeset 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 inpre.jsonif certain changesets are deleted.#2186
3910adfThanks @Andarist! - Private packages are no longer versioned by default. SetprivatePackagestotrueto opt into versioning and tagging them, or setprivatePackages.versiontotrueto version them without tagging.Minor Changes
fd7724aThanks @youdie006! - Allow comma-separated values in array-valued CLI flags: the--major,--minor, and--patchflags of theaddcommand, and the--ignoreflag of theversioncommand. For example,--minor pkg-a,pkg-bis now equivalent to--minor pkg-a --minor pkg-b. Surrounding whitespace is trimmed and empty entries are ignored.Patch Changes
96b65ee,3910adf,96b65ee]:@changesets/config@4.0.0-next.9
Major Changes
3910adfThanks @Andarist! - Private packages are no longer versioned by default. SetprivatePackagestotrueto opt into versioning and tagging them, or setprivatePackages.versiontotrueto version them without tagging.Patch Changes
96b65ee]:@changesets/git@4.0.0-next.9
Major Changes
#2190
96b65eeThanks @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.jsonfile. Existingpre.jsonwill auto-migrate to this new structure on the next run ofchangeset versionor when callingchangeset 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 inpre.jsonif certain changesets are deleted.Minor Changes
96b65eeThanks @bluwy! - Follow file renames forgetCommitsThatAddFilesso it returns the commit that added the file first, instead of the commit that renamed it, if it was renamedPatch Changes
96b65ee]:@changesets/pre@3.0.0-next.9
Major Changes
#2190
96b65eeThanks @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.jsonfile. Existingpre.jsonwill auto-migrate to this new structure on the next run ofchangeset versionor when callingchangeset 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 inpre.jsonif certain changesets are deleted.Patch Changes
96b65ee]:@changesets/read@1.0.0-next.10
Major Changes
#2190
96b65eeThanks @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.jsonfile. Existingpre.jsonwill auto-migrate to this new structure on the next run ofchangeset versionor when callingchangeset 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 inpre.jsonif certain changesets are deleted.Patch Changes
96b65ee,96b65ee]:@changesets/release-utils@1.0.0-next.10
Major Changes
#2190
96b65eeThanks @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.jsonfile. Existingpre.jsonwill auto-migrate to this new structure on the next run ofchangeset versionor when callingchangeset 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 inpre.jsonif certain changesets are deleted.Patch Changes
96b65ee]:@changesets/types@7.0.0-next.9
Major Changes
#2190
96b65eeThanks @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.jsonfile. Existingpre.jsonwill auto-migrate to this new structure on the next run ofchangeset versionor when callingchangeset 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 inpre.jsonif certain changesets are deleted.@changesets/changelog-git@1.0.0-next.9
Patch Changes
96b65ee]:@changesets/changelog-github@1.0.0-next.9
Patch Changes
96b65ee]:@changesets/get-dependents-graph@3.0.0-next.9
Patch Changes
96b65ee]:@changesets/get-release-plan@5.0.0-next.10
Patch Changes
96b65ee,3910adf]:@changesets/parse@1.0.0-next.10
Patch Changes
96b65ee]:@changesets/should-skip-package@1.0.0-next.9
Patch Changes
96b65ee]:@changesets/write@1.0.0-next.9
Patch Changes
96b65ee]: