Skip to content

ci: drop 'released' from release-workflow triggers #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rockfordlhotka merged 1 commit into from
May 9, 2026
Merged

ci: drop 'released' from release-workflow triggers #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ name: Release

on:
release:
types: [published, released]
types: [published]
workflow_dispatch:
inputs:
tag:
Expand Down
5 changes: 2 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -322,9 +322,8 @@ After 1.0 the standard SemVer rules kick in (breaking → major, additive → mi
### If the release workflow didn't fire

GitHub's `release: published` event is occasionally missed — usually
when the Release was created from a pre-existing tag via API. The
workflow listens for both `published` and `released` activity types as
a defensive measure, but it can still happen. Two recovery paths:
when the Release was created from a pre-existing tag via API. Two
recovery paths:

- **Manual dispatch** (preferred): trigger the workflow against the
existing tag without touching the Release.
Expand Down
Loading