Skip to content

fix: handle existing releases when creating with artifacts#24

Merged
thoroc merged 2 commits intomainfrom
fix/release-please-outputs
Feb 7, 2026
Merged

fix: handle existing releases when creating with artifacts#24
thoroc merged 2 commits intomainfrom
fix/release-please-outputs

Conversation

@thoroc
Copy link
Owner

@thoroc thoroc commented Feb 7, 2026

Problem\nThe workflow failed because release v0.4.5 already existed from a previous failed run, causing gh release create to fail with "a release with the same tag name already exists".\n\n## Solution\nAdded logic to check if a release already exists and delete it before recreating with all artifacts:\n\nbash\nif gh release view "${TAG}" &>/dev/null; then\n echo "Release ${TAG} already exists, deleting it to recreate with artifacts..."\n gh release delete "${TAG}" --yes\nfi\n\n\nThis ensures the release is atomic with all artifacts, handling retries and failed partial runs gracefully.

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@github-copilot Please review this PR focusing on:

  1. Code quality, best practices, and potential bugs
  2. Security vulnerabilities and unsafe patterns
  3. Performance implications
  4. Documentation accuracy and completeness
  5. Test coverage and edge cases

Please provide specific, actionable feedback.

@thoroc thoroc merged commit 8a47164 into main Feb 7, 2026
1 check passed
@thoroc thoroc deleted the fix/release-please-outputs branch February 7, 2026 05:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant