Repository navigation
Version Packages - #375
Merged
Merged
Version Packages#375
Conversation
github-actions
Bot
force-pushed
the
changeset-release/master
branch
from
May 24, 2020 23:21
0c00167 to
debda3a
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
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]
Minor Changes
6d0790a#359 Thanks @ajaymathur! - Add support for snapshot flag to version command. Usage:changeset version --snapshot [tag]. The updated version of the packages looks like0.0.0[-tag]-YYYYMMDDHHMMSSwhere YYYY, MM, DD, HH, MM, and SS is the date and time of when the snapshot version is created. You can use this feature with the tag option in the publish command to publish packages under experimental tags from feature branches. To publish a snapshot version of a package under an experimental tag you can do:@changesets/[email protected]
Minor Changes
6d0790a#359 Thanks @ajaymathur! - Add support for snapshot flag to version command. Usage:changeset version --snapshot [tag]. The updated version of the packages looks like0.0.0[-tag]-YYYYMMDDHHMMSSwhere YYYY, MM, DD, HH, MM, and SS is the date and time of when the snapshot version is created. You can use this feature with the tag option in the publish command to publish packages under experimental tags from feature branches. To publish a snapshot version of a package under an experimental tag you can do:@changesets/[email protected]
Minor Changes
6d0790a#359 Thanks @ajaymathur! - Add support for snapshot flag to version command. Usage:changeset version --snapshot [tag]. The updated version of the packages looks like0.0.0[-tag]-YYYYMMDDHHMMSSwhere YYYY, MM, DD, HH, MM, and SS is the date and time of when the snapshot version is created. You can use this feature with the tag option in the publish command to publish packages under experimental tags from feature branches. To publish a snapshot version of a package under an experimental tag you can do:6d0790a#359 Thanks @ajaymathur! - Add support for tag flag to publish command. Usage:changeset publish --tag <tag>. This will publish the packages under passed npm tag.Patch Changes
6d0790a]: