Skip to content

fix: make release workflows resilient to existing tags#1731

Merged
OneStepAt4time merged 4 commits intodevelopfrom
fix/1730-release-please-duplicate-tag
Apr 12, 2026
Merged

fix: make release workflows resilient to existing tags#1731
OneStepAt4time merged 4 commits intodevelopfrom
fix/1730-release-please-duplicate-tag

Conversation

@OneStepAt4time
Copy link
Copy Markdown
Owner

Aegis version

Version field intentionally omitted; this PR fixes release workflow behavior.

Scope

Fix release automation so release-please does not fail when historical GitHub release tags already exist.

Changes

  • Set release-please to skip GitHub release creation
  • Add idempotent ensure-github-release step in tag-based release workflow
  • Gate artifact attach steps on release existence

@OneStepAt4time OneStepAt4time merged commit 20627e4 into develop Apr 12, 2026
9 checks passed
@OneStepAt4time OneStepAt4time deleted the fix/1730-release-please-duplicate-tag branch April 12, 2026 23:14
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