gplay publish

gplay publish

Canonical Google Play release workflows.

gplay publish <subcommand> [flags]

Publish is the canonical high-level release entry point.

Use gplay publish track for the standard artifact -> track workflow. Lower-level commands such as release, promote, and rollout remain available for advanced control and debugging.

gplay publish track

Run preflight and publish to a Play track.

gplay publish track --package <name> --track <track> (--bundle <path> | --apk <path>) [flags]

Publish an artifact to a Play track using the canonical API-driven flow.

This command:

1. Builds the canonical readiness report
2. Stops on blocking issues (and optionally warnings with –strict)
3. Executes the lower-level release workflow if preflight passes

Flag	Description	Default
--apk	Path to .apk file	``
--bundle	Path to .aab bundle file	``
--changes-not-sent-for-review	Changes not sent for review	false
--listings-dir	Path to listings metadata directory	``
--output	Output format: json (default), table, markdown	json
--package	Package name (applicationId)	``
--poll-interval	Polling interval when waiting	10s
--pretty	Pretty-print JSON output	false
--release-notes	Release notes: plain text, JSON array, or @file	``
--rollout	Staged rollout fraction (0.0-1.0)	1
--screenshots-dir	Path to screenshots directory	``
--skip-metadata	Skip metadata sync even if –listings-dir is set	false
--skip-screenshots	Skip screenshot sync even if –screenshots-dir is set	false
--status	Release status: draft, inProgress, halted, completed	completed
--strict	Treat readiness warnings as publish blockers	false
--track	Target track	production
--version-name	Optional version name override	``
--wait	Wait for the published release to appear in the target track	false