ci: make the npm release last since it is not reversible#442
Merged
Conversation
|
Review changes with |
Contributor
|
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
3 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.
PR Goal?
Since GitHub releases can be delete but npmjs published packages cannot, the
npm publishsteps should be the very last ones we run.This way, when something fails, we can just delete the release on GitHub and push the tag again.
Feedback sought?
Sanity checking
Priority?
High - before we publish 1.6.0
How to test?
Can't test this without creating a fake repo and all, but I'm just interchanging two blocks in the workflow, so I think it's safe.
Confidence?
high
Version change?
no