fix: create GitHub Release before uploading VSIX if it does not exist#11
Merged
fix: create GitHub Release before uploading VSIX if it does not exist#11
Conversation
gh release upload fails with "release not found" when no release object exists for the tag. This can happen when the tag is pushed without semantic-release, or when re-running a failed job after the release was not yet created. The new step runs gh release view first and only creates the release if it is absent, so existing releases (created by semantic-release) are left untouched. https://claude.ai/code/session_01V2Cfo3mjjVxW1iuVhavsXp
|
🎉 This PR is included in version 1.0.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
gh release upload fails with "release not found" when no release object
exists for the tag. This can happen when the tag is pushed without
semantic-release, or when re-running a failed job after the release was
not yet created. The new step runs gh release view first and only creates
the release if it is absent, so existing releases (created by
semantic-release) are left untouched.
https://claude.ai/code/session_01V2Cfo3mjjVxW1iuVhavsXp