Skip to content

ci(e2e-release): trigger on CI completion, not release: published#14

Merged
solsson merged 1 commit intomainfrom
ci-release-event-race
May 2, 2026
Merged

ci(e2e-release): trigger on CI completion, not release: published#14
solsson merged 1 commit intomainfrom
ci-release-event-race

Conversation

@solsson
Copy link
Copy Markdown
Contributor

@solsson solsson commented May 1, 2026

No description provided.

Every release fired a failed e2e-release run before the assets
existed (e.g. run 25228614874 on v0.3.5). The cause is that
GitHub fires `release: published` the moment the Release object
becomes published -- which, when a maintainer creates the release
via the UI before pushing the tag (or in parallel), is BEFORE the
CI workflow's release-assets job has uploaded any binaries. The
e2e-release validator races in, finds nothing, and fails with
"no assets to download".

Switching the trigger to `workflow_run` on the upstream `CI`
workflow's completion eliminates the race: by the time CI
finishes successfully, release-assets has run and the binaries
+ checksums are attached. The job-level `if:` filters to
successful CI runs that came from a tag push (head_branch
starting with `v`), so PR/main runs of CI don't trigger an
empty validation pass.

`workflow_dispatch` with a tag input is preserved for ad-hoc
re-runs against any published tag.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@solsson solsson merged commit e7a7857 into main May 2, 2026
11 checks passed
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