fix(ci): call publish workflow directly from release workflow#22
Merged
fix(ci): call publish workflow directly from release workflow#22
Conversation
GitHub Actions events created by GITHUB_TOKEN do not trigger other workflows. The release workflow creates a GitHub Release using GITHUB_TOKEN, so the `release: published` event never fires, and publish.yml is never triggered. Fix by having release.yml call publish.yml as a reusable workflow via workflow_call, bypassing the event chain entirely. The publish workflow still supports direct triggering from manual releases. https://claude.ai/code/session_01HPY8vSqa2iu9GnNY4w8DdW
Allow manual re-triggering of the publish workflow from the GitHub Actions UI. This is needed for re-publishing releases when the automated chain was broken (e.g., v0.2.1). https://claude.ai/code/session_01HPY8vSqa2iu9GnNY4w8DdW
chaliy
added a commit
that referenced
this pull request
Feb 8, 2026
## What Prepare patch release v0.2.2. ## Why Maintenance release including dependency updates, model profile refreshes, and a CI fix. ## How - Bumped version in `Cargo.toml` to 0.2.2 - Updated `CHANGELOG.md` with v0.2.2 section ### Changelog #### Highlights - Updated dependencies and model profiles for routine maintenance - Fixed CI release workflow to call publish workflow directly #### What's Changed * chore: routine maintenance - update deps, models, and specs (#23) by @chaliy * fix(ci): call publish workflow directly from release workflow (#22) by @chaliy **Full Changelog**: v0.2.1...v0.2.2 ## Risk - Low - Standard maintenance release with no API changes ## Checklist - [x] `cargo fmt --check` passes - [x] `cargo clippy -- -D warnings` passes - [x] `cargo test` passes (125 tests) - [x] `cargo publish --dry-run` succeeds - [x] CHANGELOG.md updated - [x] Cargo.toml version bumped https://claude.ai/code/session_01XGsYuzj6E4H1womTZL6Ygh Co-authored-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Fix the publish workflow not being triggered after automated releases.
Why
GitHub Actions events created by
GITHUB_TOKENdo not trigger other workflows. The release workflow creates a GitHub Release usingGITHUB_TOKEN, so therelease: publishedevent never fires andpublish.ymlis never triggered.This is why v0.2.1 was released on GitHub but never published to crates.io, while v0.1.0 and v0.2.0 (created manually) were published successfully.
How
workflow_calltrigger topublish.ymlwith atag_nameinput parameterpublishjob torelease.ymlthat callspublish.ymlas a reusable workflow after the release is createdinputs.tag_name || github.event.release.tag_nameso publish.yml works from both triggerssecrets: inheritsoCARGO_REGISTRY_TOKENis availableThe publish workflow still supports direct triggering from manually-created releases via the
release: publishedevent.Risk
Checklist
cargo test- 120 tests)cargo fmt --check)cargo clippy)https://claude.ai/code/session_01HPY8vSqa2iu9GnNY4w8DdW