Skip to content

Skip the release workflow when the release already has assets - #730

Draft
pmatseykanets wants to merge 1 commit into
rancher:mainfrom
pmatseykanets:release-skip-duplicate-runs
Draft

pmatseykanets wants to merge 1 commit into
rancher:mainfrom
pmatseykanets:release-skip-duplicate-runs

Conversation

@pmatseykanets

Copy link
Copy Markdown
Collaborator

Problem

A duplicated tag push event started two Release runs for the same tag. Both ran in parallel, and the second one failed on uploading assets that the first had already uploaded.

Solution

Release runs for one tag now execute one at a time. A new check job looks up the release first, and the release job is skipped when the release already has assets. Assets are never overwritten.

A duplicated tag push event started two Release runs for the same tag.
Both ran in parallel, and the second one failed on uploading assets
that the first had already uploaded.

Release runs for one tag now execute one at a time. A new check job
looks up the release first, and the release job is skipped when the
release already has assets. Assets are never overwritten.
@pmatseykanets pmatseykanets self-assigned this Oct 13, 2026
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.

2 participants