Add tag existence check to prevent duplicate release creation #77
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>
Co-authored-by: mkistler <800728+mkistler@users.noreply.github.com>
Co-authored-by: mkistler <800728+mkistler@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Address feedback on revised release and publish workflows
Add tag existence check to prevent duplicate release creation
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.
The
publish-release.ymlworkflow fails when triggered multiple times with the same version (retries, manual triggers) because it attempts to create a tag/release that already exists.Changes
git ls-remote --tags origin "refs/tags/$tag"to query remote for existing tags before release creationtag_exists == 'false'The workflow now handles idempotent execution gracefully while maintaining existing npm publish behavior.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.