$gpc tracks

--json

Manage release tracks — internal, alpha, beta, production, and custom tracks.

usagegpc tracks <subcommand> [options]

Commands

Command	Description
tracks list	List all tracks with status
tracks create	Create a custom closed testing track
tracks update	Update track configuration

tracks list

List all tracks for the app, showing the current status and active release for each.

Synopsis

gpc tracks list [options]

Example

gpc tracks list --app com.example.myapp

{
  "tracks": [
    { "track": "internal", "releases": 1, "latestStatus": "completed", "latestVersion": "42" },
    { "track": "alpha", "releases": 0, "latestStatus": "none", "latestVersion": "-" },
    { "track": "beta", "releases": 1, "latestStatus": "completed", "latestVersion": "41" },
    { "track": "production", "releases": 1, "latestStatus": "completed", "latestVersion": "40" }
  ],
  "nextPageToken": null,
  "meta": { "count": 4 }
}

List output shape (v0.9.87+)

tracks list --json returns the unified list envelope { tracks, nextPageToken, meta.count }. Each row is a summary: releases is the release count (a number), and latestStatus / latestVersion describe the most recent release. Use gpc releases status --track <track> for the full release objects (versionCodes, userFraction, etc.).

---

tracks create

Create a custom closed testing track.

Synopsis

gpc tracks create <name> [options]

Options

Flag	Short	Type	Default	Description
--changes-not-sent-for-review		flag		Commit without sending for review
--error-if-in-review		flag		Fail if changes are already in review

Example

gpc tracks create my-qa-track --app com.example.myapp

---

tracks update

Update a track's configuration from a JSON file. This sets releases, status, and rollout fraction.

Synopsis

gpc tracks update <track> --file <path> [options]

Options

Flag	Short	Type	Default	Description
--file		string	(required)	Path to JSON track configuration
--dry-run		boolean	false	Preview changes without applying
--changes-not-sent-for-review		flag		Commit without sending for review
--error-if-in-review		flag		Fail if changes are already in review

Example

gpc tracks update beta --app com.example.myapp --file track-config.json

Preview without applying:

gpc tracks update beta --app com.example.myapp --file track-config.json --dry-run

Errors

Exit Code	Meaning
2	Invalid track name or missing required arguments
3	Authentication failure
4	API error (e.g., track not found, edit conflict)

Related

• releases -- Create, upload, and manage releases
• publish -- Upload + release in one command