Re-apply version bump to CHANGELOG and package.json #996
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
We turned on protection against pushes to `master`, but have not set up any automation to allow creation of releases via CI, so `release-it` got through the point where it had published to `npm`, then tried to push to GitHub, failed, and rolled this back. I'll let it merge, then tag the result as 6.1.0 for the repo.
|
So this is what we published, and I'm going to merge and tag it… but CI found a bug 🙃 so I will now… figure out… how to publish… again?!? 🙃 |
|
I trolled myself with |
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.
We turned on protection against pushes to
master, but have not set up any automation to allow creation of releases via CI, sorelease-itgot through the point where it had published tonpm, then tried to push to GitHub, failed, and rolled this back. I'll let it merge, then tag the result as 6.1.0 for the repo.