Skip to content

Promote dev → staging (Play listing publish is manual-only) - #807

Merged
patrickrb merged 2 commits into
stagingfrom
dev
Sep 8, 2026
Merged

patrickrb merged 2 commits into
stagingfrom
dev

Conversation

@patrickrb

Copy link
Copy Markdown
Owner

What's in this promotion

One PR since android-dev.1221:

  • Make the Play listing publish manual-only #806 — Make the Play listing publish manual-only. Removes the push: branches: [main] trigger from play-listings.yml, so a staging → main merge now reaches Google Play in no way at all: android.yml already uploaded no AAB there (CI: stop publishing to Play production on staging → main merges #794), and store-listing text was the last thing that still published as a side effect of the promotion. Listing copy is still validated on every PR that touches it, and now ships only on a deliberate workflow_dispatch run (dry-run default / check-permissions / publish) or by running .github/scripts/publish_listings.py locally. Docs updated in docs/release-pipeline.md and docs/store-listings.md.

What merging this does

Cuts the usual dev build — unchanged by #806:

  • android-dev.<run#> GitHub prerelease + the signed AAB and R8 mapping to the Play internal track, with Claude's semver + release notes.
  • desktop-dev.<run#> prerelease for the Tauri desktop bundles.

The diff since android-v0.149 touches 574 files under ft8af/, so android_changed is true and the Android release will be cut normally (this promotion's own change is workflow/docs only).

🤖 Generated with Claude Code

https://claude.ai/code/session_01XNDpfHeom9W1c7spiGxP6H

patrickrb and others added 2 commits September 8, 2026 11:21
A merge to `main` no longer touches Google Play in any way. `android.yml`
already uploaded no AAB on a main push (PR #794); `play-listings.yml` was the
last thing that did — a main push touching `fastlane/metadata/android/**`
published the changed locales to the store as a side effect of the promotion.

Drop that push trigger. Listing text still lands in the repo on the normal
feature -> dev -> staging -> main flow and is still validated on the way in
(the PR gate runs the completeness/character-limit tests unchanged), but it
reaches the store only when someone runs the publish on purpose: the manual
workflow_dispatch (dry-run / check-permissions / publish) or
`.github/scripts/publish_listings.py` locally.

Also make MODE fall back to the read-only `dry-run` instead of `publish`, so a
mode that somehow arrives empty sends nothing to Play.

No new code path to test: the change is workflow triggers plus docs, and the
135 publish_listings unit tests pass unchanged.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XNDpfHeom9W1c7spiGxP6H
Make the Play listing publish manual-only
@codecov

codecov Bot commented Sep 8, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 42.64%. Comparing base (dd0cbd6) to head (fe346e4).
⚠️ Report is 15 commits behind head on staging.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             staging     #807   +/-   ##
==========================================
  Coverage      42.64%   42.64%           
  Complexity       226      226           
==========================================
  Files            267      267           
  Lines          32068    32068           
  Branches        3664     3664           
==========================================
  Hits           13675    13675           
  Misses         18132    18132           
  Partials         261      261           
Flag Coverage Δ
desktop 63.95% <ø> (ø)
ios 97.71% <ø> (ø)
native 9.93% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@patrickrb
patrickrb merged commit 37f40fa into staging Sep 8, 2026
38 checks passed
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