ci: fix duplicate release runs and npm-publish CI race#24
Merged
StefanSteiner merged 2 commits intoMay 18, 2026
Merged
Conversation
- Remove push:tags trigger from release.yml — with the PAT, both release:published AND push:tags fire, causing duplicate runs. Keep only release:published + manual workflow_dispatch. - Make publish step skip already-published crates instead of failing, so re-runs are safe. - Replace instant CI status check in npm-build-publish with a wait/retry loop (30 attempts × 60s) since the release:published event fires before CI completes on the merge commit. - Update GITHUB_OPERATIONS.md to reflect automated publish flow.
Forks inherit workflow files but not secrets, causing spurious failures when syncing main. Add repository guard conditions so release-please, release, and npm-build-publish only run on the upstream repo.
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
1 participant
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.
Summary
Fixes two issues from the v0.1.3 release:
release: publishedANDpush: tagsevents, causing two concurrent publish attempts. The second fails because crates are already on crates.io. Fix: removepush: tagstrigger (useworkflow_dispatchfor emergency releases instead).release: publishedevent fires before CI finishes on the merge commit. Theverify-cistep checks status immediately and findspending. Fix: replace instant check with a retry loop (polls every 60s for up to 30 min).Also makes
cargo publishskip already-published crates instead of failing, so manual re-runs are safe.Test plan
ci:prefix — no version bump)release.ymlrunnpm-build-publish.ymlshould wait for CI before building