ci: gate releases on CI/audit status, add RELEASING.md#17
Merged
Conversation
publish.yml triggers on any v* tag push with no dependency on ci.yml or audit.yml passing - GitHub Actions has no way for one workflow file to `needs:` a job defined in another, so this can't be wired up inside publish.yml itself. Add scripts/check-release-ready.sh, which queries the latest ci.yml/audit.yml runs for a commit via `gh run list -c` and fails if either hasn't run, is incomplete, or didn't succeed, and document it as a required step in a new RELEASING.md. Closes #16.
git rev-parse on an annotated tag returns the tag object's own SHA, not the commit it points at, so gh run list -c <sha> would never find a matching run when checking a tag ref (the script's primary intended use case).
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
opentimstdf-docs | f87c9de | Jul 18 2026, 10:54 PM |
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
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
publish.ymltriggers on anyv*tag push with no dependency onci.ymloraudit.ymlpassing. GitHub Actions has no way for one workflow file toneeds:a job defined in a separate workflow file, so this has to beenforced before the tag is created rather than inside
publish.ymlitself.scripts/check-release-ready.sh, which resolves a ref (defaultHEAD)to a commit SHA and checks the latest
ci.yml/audit.ymlruns for that SHAvia
gh run list -w <workflow> -c <sha> --json status,conclusion,url -L 1.Fails with a clear message (including the run URL when available) if either
workflow has no run for the commit, hasn't completed, or didn't succeed.
RELEASING.mddocumenting the release process (version bump in theworkspace
Cargo.toml, changelog, commit, tag, push, publish, verify),with the release-readiness check as an explicit required step before
tagging.
Closes #16.
Test plan
./scripts/check-release-ready.sh(defaultHEAD= currentmaintip) - bothci.ymlandaudit.ymlreportedOK, scriptexited 0.
audit.yml's introduction -ci.ymlreportedOK,audit.ymlcorrectly reported "no run found",script exited 1.