Promote to production via track promotion instead of creating a new release#23143
Open
oguzkocer wants to merge 1 commit into
Open
Promote to production via track promotion instead of creating a new release#23143oguzkocer wants to merge 1 commit into
oguzkocer wants to merge 1 commit into
Conversation
`promote_version_code_to_production` now uses `upload_to_play_store` with `track_promote_to` (the Play Console "Promote" action) instead of building a new production release via `update_track`. This extends the already-reviewed beta release to the production track — same versionCode, no new binary — so the beta release's notes and name carry over automatically. Ships as a live staged rollout (`inProgress` at 0.1%); `advance_production_rollout` grows it from there.
oguzkocer
force-pushed
the
task/promote-to-production-via-promotion
branch
from
July 23, 2026 21:27
9c80d8d to
88ae20c
Compare
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
1 participant
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.
With the move to static release notes, the production step no longer needs to build its own release just to attach per-version notes — so we can simplify it.
promote_version_code_to_productionnow promotes the existing beta build to production viaupload_to_play_store(track_promote_to:)— the scripted equivalent of the Play Console Promote button — instead of hand-building a new production release viaupdate_track.Why this is better:
versionCode, no new binary), so it most likely bypasses a second Play Store review and removes manual steps.TrackRelease, so its release notes and name carry over automatically — beta and production show the same notes with no extra wiring.begin_edit/update_track/commit).Rollout: ships as a live staged rollout (
inProgressat 0.1%);advance_production_rolloutgrows it from there.The guards around it are unchanged —
gather_production_candidatestill derives the candidate from the beta track and enforces the WordPress/Jetpack version-code match, and the Yes/No confirmation block step remains the go/no-go gate.Follow-up: the release notes themselves will be chosen during beta promotion in the next PR.