Conversation
634aa6f to
7a5501e
Compare
7a5501e to
0c9c5c1
Compare
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.
Releases
@changesets/cli@2.31.0
Minor Changes
#1889
96ca062Thanks @mixelburg! - Error on unsupported flags for individual CLI commands and print the matching command usage to make mistakes easier to spot.#1873
42943b7Thanks @mixelburg! - Respond to--helpon all subcommands. Previously,--helpwas only handled when it was the sole argument; passing it alongside a subcommand (e.g.changeset version --help) would silently execute the command instead. Now--helpalways exits early and prints per-command usage when a known subcommand is provided, or the general help text otherwise.Patch Changes
d2121dcThanks @Andarist! - Fix npm auth for path-based registries during publish by preserving configured registry URLs instead of normalizing them.#1888
036fdd4Thanks @mixelburg! - Fix severalchangeset versionissues with workspace protocol dependencies. Valid explicitworkspace:ranges and aliases are no longer rewritten unnecessarily, and workspace path references are handled correctly during versioning.#1903
5c4731fThanks @Andarist! - Gracefully handle stalenpm infodata leading to duplicate publish attempts.#1867
f61e716Thanks @Andarist! - Improved detection forpublishedstate of prerelease-only packages withoutlatestdist-tag on GitHub Packages registry.Updated dependencies [
036fdd4,036fdd4,036fdd4]:@changesets/apply-release-plan@7.1.1
Patch Changes
#1888
036fdd4Thanks @mixelburg! - Fix workspace protocol dependency updates for explicit ranges, aliases, and path references. Validworkspace:dependency forms are now preserved and only rewritten when the referenced release leaves the supported range or path.Updated dependencies []:
@changesets/assemble-release-plan@6.0.10
Patch Changes
#1888
036fdd4Thanks @mixelburg! - Fix dependent bump detection for workspace path references. Dependencies declared with specifiers likeworkspace:packages/pkgare now resolved correctly when deciding whether dependents need a release.Updated dependencies [
036fdd4]:@changesets/config@3.1.4
Patch Changes
036fdd4]:@changesets/get-dependents-graph@2.1.4
Patch Changes
036fdd4Thanks @mixelburg! - Fix dependency graph validation for workspace path references. Validworkspace:packages/pkgspecifiers are now treated as local dependencies instead of being rejected as invalid ranges.@changesets/get-release-plan@4.0.16
Patch Changes
036fdd4]: