chore: release v0.3.3 - #15
Merged
Merged
Conversation
kkomelin
approved these changes
Jun 1, 2022
Member
|
We got some problems with NPM during release trigger. |
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
2 participants
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 pull request prepares the following release:
0.3.2→0.3.3Release Summary
This is going to be published with the following command:
npm_config_registry=https://registry.npmjs.org/ npm publish --tag latest --access public --tag latestMerging Instructions
When merging this pull request, you need to Squash and merge and make sure that the title starts with
chore: release v0.3.3.See details
After that, a commit
chore: release v0.3.3will be added and you or your CI can runshipjs triggerto trigger the release based on the commit.This pull request is automatically generated by Ship.js.