Skip to content

CI: release only green commits, don't re-check release tags - #22

Merged
Tarquinen merged 1 commit into
mainfrom
ci/release-guard
Nov 10, 2026
Merged

Tarquinen merged 1 commit into
mainfrom
ci/release-guard

Conversation

@Tarquinen

Copy link
Copy Markdown
Member
  • Scheduled release only tags green commits. It now skips unless main's push run of android.yml passed for that commit. Before, a broken main still got a GitHub release with no Play build behind it. A run still in progress just waits for the next release time.
  • Release tags don't rerun the full check. If main already passed the exact commit, the tag run skips scripts/check.sh and goes straight to the signed bundle, so releases reach Play about 5 minutes sooner. Tags on commits main never passed (e.g. cut by hand) still run the full check.

PR checks and the post-merge check on main are unchanged. The main run is what fills the Gradle cache that PRs read, and it catches PRs that only break in combination.

The tag path can't be exercised without cutting a release, so the first scheduled release after merging is the real test.

The scheduled release tagged main without looking at its CI, so a red main
still got a GitHub release (whose tag build then failed before Play). It now
skips unless the commit's push run of android.yml on main succeeded; a run
still in progress waits for the next release time.

Release tags reran scripts/check.sh on a commit main had already checked.
The tag run now skips the check (and the debug APK artifact) when main
already passed that exact commit, and goes straight to the signed bundle.
A tag on a commit main never passed (e.g. cut by hand) still runs the check.

PR and post-merge checks on main are unchanged: the main run writes the
Gradle cache PRs read, and catches PRs that break only in combination.

Verified: both workflows parse as YAML; the gh run list query returns
"success" for 993afa0 and empty for an unknown SHA (both paths handled).
The tag path can't run without cutting a release.
@Tarquinen
Tarquinen merged commit 6559227 into main Nov 10, 2026
3 checks passed

This branch was previously deployed

1 inactive deployment
release — 8442633f Deployed Nov 10, 2026 by Tarquinen via check #77
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