create_release
Publish an uploaded app bundle to a Google Play track using explicit version codes, replacing the current release for that track.
Instructions
Create a release on a track from explicit version codes, replacing whatever releases that track currently has. Use this to ship an already-uploaded bundle: get the version codes from list_bundles or list_apks first. Use promote_release instead when moving an existing release between tracks. Use validate_only first to check the change without committing.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| track | Yes | Track to release on: 'internal', 'alpha', 'beta', 'production' or a custom track | |
| status | No | Release status. Defaults to 'inProgress' when user_fraction is given, otherwise 'completed'. Use 'draft' to stage a release without publishing it. | |
| package_name | No | App package name, e.g. 'com.acme.app' (defaults to GOOGLE_PLAY_PACKAGE_NAME) | |
| release_name | No | Release name shown in the Play Console, e.g. '1.4.0 (415)' | |
| release_notes | No | Release notes per locale, e.g. [{language:'en-US',text:'Bug fixes'}]. Defaults to the source release's notes. | |
| user_fraction | No | Staged rollout fraction between 0 and 1 exclusive, e.g. 0.1 for 10%. Omit to release to all users. | |
| validate_only | No | Dry run: validate the change and discard the edit instead of committing it | |
| version_codes | Yes | Version codes of the bundles/APKs to release, as strings, e.g. ['415']. Get them from list_bundles or list_apks. | |
| country_targeting | No | Restrict the release to specific countries. Omit to keep the source targeting. | |
| in_app_update_priority | No | In-app update priority from 0 (default) to 5 (most urgent), read by the Play In-App Updates API. Omit to keep the source value. | |
| changes_not_sent_for_review | No | Commit without sending the changes for review (only for apps where changes are reviewed separately) |