Version Packages #450
Merged
Version Packages #450
Conversation
This file contains 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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
github-actions
bot
force-pushed
the
changeset-release/master
branch
2 times, most recently
from
29ec971 to
731f1cc
Compare
Codecov Report
|
github-actions
bot
force-pushed
the
changeset-release/master
branch
5 times, most recently
from
4842d08 to
c704866
Compare
Andarist
approved these changes
Sep 14, 2020
github-actions
bot
force-pushed
the
changeset-release/master
branch
from
c704866 to
bb59dad
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 master, this PR will be updated.
Releases
@changesets/[email protected]
Major Changes
ab98fe3#454 Thanks @Andarist! - Returned releases in pre mode will have type of the highest bump type within the current release now, instead of having the highest bump type from among all changesets within this pre mode. So if you release a new prerelease including a major bump and later release the same package with a minor bump the assembled release will be of type minor - the final computed version will, of course, still be the next one for a major bump.Patch Changes
d1d987c#455 Thanks @Andarist! - Fixed an issue with linked package being assigned a non-none release type when another package from the linked set has been added to current releases and the package had just a none release type.9d99bd1#446 Thanks @Andarist! - Fixed an issue with dependant packages not being updated to their highest bump type in pre mode sometimes. This could happen when dependant packages were only versioned because of their dependencies being upgraded and not because of a dedicated changeset for those dependant packages.For the very same reason linked packages were also not always bumped correctly in pre mode to the highest bump type in a linked group.
@changesets/[email protected]
Patch Changes
d1d987c#455 Thanks @Andarist! - Fixed an issue with linked package being bumped when its dev dependency from the linked set was bumped during the versioning.9d99bd1#446 Thanks @Andarist! - Fixed an issue with dependant packages not being updated to their highest bump type in pre mode sometimes. This could happen when dependant packages were only versioned because of their dependencies being upgraded and not because of a dedicated changeset for those dependant packages.For the very same reason linked packages were also not always bumped correctly in pre mode to the highest bump type in a linked group.
Updated dependencies [
ab98fe3,d1d987c,9d99bd1]:@changesets/[email protected]
Patch Changes
ab98fe3,d1d987c,9d99bd1]: