Skip to content

Serialize Play publishing to prevent edit-expired races #166

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
patrickrb merged 2 commits into from
Jun 8, 2026
+19 −0
Merged

Serialize Play publishing to prevent edit-expired races #166

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cd4da68
Serialize Play publishing to prevent edit-expired races
patrickrb Jun 8, 2026
e9da591
Potential fix for pull request finding
patrickrb Jun 8, 2026
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
19 changes: 19 additions & 0 deletions .github/workflows/build-release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,25 @@ on:
permissions:
contents: write

# Google Play allows only one active "edit" per app, so two release builds
# publishing at once make the second fail with "This edit has expired, please
# create a new Edit." Serialize the release-publishing runs (pushes to dev/main
# and v* tags) into a single queue so they never overlap on the Play API.
# cancel-in-progress is false so an in-flight publish finishes rather than being
# killed mid-upload. Pull request runs get a unique group keyed to run id, so
# they never queue and CI stays fast.
concurrency:
group: >-
${{
(github.event_name == 'push'
&& (github.ref == 'refs/heads/main'
|| github.ref == 'refs/heads/dev'
|| startsWith(github.ref, 'refs/tags/v')))
&& 'play-publish'
|| format('build-{0}', github.run_id)
}}
cancel-in-progress: false

jobs:
test:
name: Unit tests & coverage
Expand Down
Loading