Skip to content

Publish app-changing merges to Play production - #37

Merged
seenu-k merged 7 commits into
mainfrom
codex/production-releases
Nov 2, 2026
Merged

seenu-k merged 7 commits into
mainfrom
codex/production-releases

Conversation

@seenu-k

@seenu-k seenu-k commented Oct 29, 2026 •

Copy link
Copy Markdown
Collaborator

App-changing merges currently upload Android to closed testing. This change submits them to Play production alongside the existing web/backend deployment. Every app-changing PR, including cosmetic fixes and app dependency updates, must include a Cider version bump and finalized release notes. Backend-only, public website, documentation, tests and release tooling changes need no Android release.

The existing required Analyse and test job compares PRs with their base SHA and main pushes with the previous push. It checks shipped app inputs, requires a higher stable Cider version and finalized Play-compatible release notes, and leaves published changelog history alone. AGENTS.md documents the release steps and links to the full runbook; CLAUDE.md imports those instructions.

The production Fastlane lane fixes the production track and full rollout status. Play update priority is derived from the Cider version relative to the last submitted release tag: major 5, minor 2, patch 0. Automatic and manual production runs follow the same rule. The app requests Play's immediate flow for a major update; minor and patch releases keep the existing dismissible flexible prompt. No client lockout is added, and Play availability, eligibility, cancellation and review still apply.

Existing v tags record accepted Play submissions. Pending app releases and their urgency survive failed uploads, backend-only merges and unsubmitted follow-up patches. Full checkout history lets the workflow find the previous submitted tag along main's first-parent history. A patch after a submitted major returns to priority 0. Manual artifact-only builds and testing lanes remain available; testing lanes retain explicit priority configuration.

Validation: all 42 Dart release-tool tests passed. Offline tests exercise the actual Fastlane lanes, eight version-delta cases, invalid/non-increasing versions, ignored legacy production overrides, and the actual workflow build-number/tag-selection shell step with real Git history. Ruby, workflow YAML/shell syntax, artwork provenance and diff checks passed. All four required hosted CI checks passed on the priority-mapping commit, including release tooling, full app and Chrome/WASM tests, backend integration and the production web build.

The app version remains 4.1.0, which already has a release tag. This tooling-only PR therefore deploys the web/backend without submitting Android. The next app-changing PR must bump and release its app version; merging it submits the first new production version, subject to Play review and publishing settings.

@seenu-k seenu-k changed the title Automate production releases with required Cider version checks Publish Android to production on app version changes Oct 29, 2026
@seenu-k seenu-k changed the title Publish Android to production on app version changes Publish versioned Android releases to production Oct 29, 2026
@seenu-k seenu-k changed the title Publish versioned Android releases to production Publish app-changing merges to Play production Oct 30, 2026
@seenu-k
seenu-k merged commit faf4460 into main Nov 2, 2026
4 checks passed
@seenu-k
seenu-k deleted the codex/production-releases branch November 2, 2026 04:35
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