Reverse workflow order: publish to npm before creating GitHub release #78
Conversation
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
Co-authored-by: mkistler <800728+mkistler@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] WIP Address feedback on revised release and publish workflows
Reverse workflow order: publish to npm before creating GitHub release
Jan 27, 2026
Contributor
|
I'm going to start over on this. |
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.
Addresses feedback from PR #73 where the workflow could leave the repository in an inconsistent state if
npm publishfailed after the GitHub release was already created.Changes
.github/workflows/publish-release.yml:This ensures GitHub releases only exist when the corresponding npm package is successfully published.
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.