Version Packages - #514
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/master
branch
2 times, most recently
from
January 14, 2021 15:09
67596ae to
a73171e
Compare
github-actions
Bot
force-pushed
the
changeset-release/master
branch
from
January 14, 2021 15:50
a73171e to
6490c57
Compare
Andarist
approved these changes
Jan 14, 2021
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 master, this PR will be updated.
Releases
@changesets/cli@2.13.0
Minor Changes
412b4b9#504 Thanks @vitorbal! -changeset statuscommand no longer errors when no packages have been changed.24d7bc9#495 Thanks @RoystonS! - Automatically deepen shallow clones in order to determine the correct commit at which changesets were added. This helps Git-based changelog generators to always link to the correct commit. From now on it's not required to configurefetch-depth: 0for youractions/checkoutwhen using Changesets GitHub action.Patch Changes
24d7bc9,24d7bc9]:@changesets/git@1.1.0
Minor Changes
24d7bc9#495 Thanks @RoystonS! - Automatically deepen shallow clones in order to determine the correct commit at which changesets were added.24d7bc9#495 Thanks @RoystonS! - Deprecate thegetCommitThatAddsFilefunction. It's replaced with a bulkgetCommitsThatAddFilesoperation which will safely deepen ashallow repo whilst processing multiple filenames simultaneously.
@changesets/changelog-github@0.2.8
Patch Changes
3436c53#510 Thanks @tuanddd! - Added validation rule for invalidrepoarguments.Updated dependencies [
3436c53]:@changesets/get-github-info@0.4.5
Patch Changes
3436c53#510 Thanks @tuanddd! - Added validation rule for invalidrepoarguments.