gplay-release-flow

Name: gplay-release-flow
Author: hanamizuki

104stars8forks

How to install gplay-release-flow?

hanamizuki/solopreneur/gplay-release-flow

$npx -y skills add hanamizuki/solopreneur --skill gplay-release-flow

Installs into the current project.

Summary

End-to-end release workflows for Google Play tracks (internal, beta, production) using gplay release, promote, and rollout commands. Use when asked to upload a build, distribute to testers, or release to production.

Files · 1

View on GitHub

SKILL.md

1	# Release flow (Internal, Beta, Production)
2
3	Use this skill when you need to get a new build onto Google Play Store.
4
5	## Preconditions
6	- Ensure credentials are set (`gplay auth login` or `GPLAY_SERVICE_ACCOUNT` env var).
7	- Build must be an AAB (App Bundle) or APK.
8	- Version code must be higher than previous releases.
9	- Service account needs "Release Manager" permission in Play Console.
10
11	## Android Release
12
13	### Preferred end-to-end commands
14
15	Internal track (for internal testing):
16	```bash
17	gplay release \
18	--package com.example.app \
19	--track internal \
20	--bundle app-release.aab
21	```
22
23	Beta track (for beta testers):
24	```bash
25	gplay release \
26	--package com.example.app \
27	--track beta \
28	--bundle app-release.aab \
29	--release-notes @release-notes.json
30	```
31
32	Production with staged rollout (gradual release):
33	```bash
34	gplay release \
35	--package com.example.app \
36	--track production \
37	--bundle app-release.aab \
38	--release-notes @release-notes.json \
39	--rollout 0.1
40	```
41
42	Dry run (preview the release without executing):
43	```bash
44	gplay release \
45	--package com.example.app \
46	--track production \
47	--bundle app-release.aab \
48	--dry-run
49	```
50
51	### Release with metadata (listings and screenshots)
52
53	Include store listings from a directory:
54	```bash
55	gplay release \
56	--package com.example.app \
57	--track production \
58	--bundle app-release.aab \
59	--listings-dir ./metadata \
60	--screenshots-dir ./metadata
61	```
62
63	Skip metadata or screenshots:
64	```bash
65	# Upload bundle only, skip metadata sync
66	gplay release \
67	--package com.example.app \
68	--track production \
69	--bundle app-release.aab \
70	--skip-metadata
71
72	# Upload bundle and metadata, skip screenshots
73	gplay release \
74	--package com.example.app \
75	--track production \
76	--bundle app-release.aab \
77	--listings-dir ./metadata \
78	--skip-screenshots
79	```
80
81	Combine listings and screenshots directories:
82	```bash
83	gplay release \
84	--package com.example.app \
85	--track beta \
86	--bundle app-release.aab \
87	--listings-dir ./metadata/listings \
88	--screenshots-dir ./metadata/images \
89	--release-notes @release-notes.json
90	```
91
92	### Manual sequence (when you need more control)
93
94	1. Create edit session:
95	```bash
96	EDIT_ID=$(gplay edits create --package com.example.app \| jq -r '.id')
97	```
98
99	2. Upload bundle:
100	```bash
101	gplay bundles upload \
102	--package com.example.app \
103	--edit $EDIT_ID \
104	--file app-release.aab
105	```
106
107	3. Update track:
108	```bash
109	gplay tracks update \
110	--package com.example.app \
111	--edit $EDIT_ID \
112	--track production \
113	--releases @releases.json
114	```
115	`--releases` takes a JSON array of track releases (or `@file`).
116
117	4. Validate edit:
118	```bash
119	gplay edits validate --package com.example.app --edit $EDIT_ID
120	```
121
122	5. Commit edit (publishes changes):
123	```bash
124	gplay edits commit --package com.example.app --edit $EDIT_ID
125	```
126
127	## Track Promotion
128
129	Promote a release from one track to another:
130
131	```bash
132	# Promote from internal to beta
133	gplay promote \
134	--package com.example.app \
135	--from internal \
136	--to beta
137
138	# Promote from beta to production with 25% rollout
139	gplay promote \
140	--package com.example.app \
141	--from beta \
142	--to production \
143	--rollout 0.25
144	```
145
146	## Staged Rollout Management
147
148	Start with a 10% rollout (fraction `0.1`):
149	```bash
150	gplay release \
151	--package com.example.app \
152	--track production \
153	--bundle app.aab \
154	--rollout 0.1
155	```
156
157	Increase to 50% (fraction `0.5`):
158	```bash
159	gplay rollout update \
160	--package com.example.app \
161	--track production \
162	--rollout 0.5
163	```
164
165	Halt rollout (pause distribution):
166	```bash
167	gplay rollout halt --package com.example.app --track production
168	```
169
170	Resume rollout:
171	```bash
172	gplay rollout resume --package com.example.app --track production
173	```
174
175	Complete rollout (release to 100%):
176	```bash
177	gplay rollout complete --package com.example.app --track production
178	```
179
180	## Release Notes Format
181
182	The single `--release-notes` flag accepts three shapes: a JSON array (multi-locale), plain text (auto-assigned to `en-US`), or an `@file` path pointing to either. There is no separate locale flag.
183
184	### JSON array format (multi-locale)
185	`release-notes.json` — a JSON array of `{language, text}` entries:
186	```json
187	[
188	{ "language": "en-US", "text": "Bug fixes and performance improvements" },
189	{ "language": "es-ES", "text": "Correcciones de errores y mejoras de rendimiento" },
190	{ "language": "fr-FR", "text": "Corrections de bugs et améliorations des performances" }
191	]
192	```
193	Pass it with `--release-notes @release-notes.json`.
194
195	### Plain text format (single locale)
196	Provide release notes as plain text — it is auto-assigned to `en-US`:
197	```bash
198	gplay release \
199	--package com.example.app \

People who liked this also viewed

6 picks

Type

gplay-release-flow

104stars8forks

View on GitHub

How to install gplay-release-flow?

hanamizuki/solopreneur/gplay-release-flow

$npx -y skills add hanamizuki/solopreneur --skill gplay-release-flow

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Release flow (Internal, Beta, Production)
2
3	Use this skill when you need to get a new build onto Google Play Store.
4
5	## Preconditions
6	- Ensure credentials are set (`gplay auth login` or `GPLAY_SERVICE_ACCOUNT` env var).
7	- Build must be an AAB (App Bundle) or APK.
8	- Version code must be higher than previous releases.
9	- Service account needs "Release Manager" permission in Play Console.
10
11	## Android Release
12
13	### Preferred end-to-end commands
14
15	Internal track (for internal testing):
16	```bash
17	gplay release \
18	--package com.example.app \
19	--track internal \
20	--bundle app-release.aab
21	```
22
23	Beta track (for beta testers):
24	```bash
25	gplay release \
26	--package com.example.app \
27	--track beta \
28	--bundle app-release.aab \
29	--release-notes @release-notes.json
30	```
31
32	Production with staged rollout (gradual release):
33	```bash
34	gplay release \
35	--package com.example.app \
36	--track production \
37	--bundle app-release.aab \
38	--release-notes @release-notes.json \
39	--rollout 0.1
40	```
41
42	Dry run (preview the release without executing):
43	```bash
44	gplay release \
45	--package com.example.app \
46	--track production \
47	--bundle app-release.aab \
48	--dry-run
49	```
50
51	### Release with metadata (listings and screenshots)
52
53	Include store listings from a directory:
54	```bash
55	gplay release \
56	--package com.example.app \
57	--track production \
58	--bundle app-release.aab \
59	--listings-dir ./metadata \
60	--screenshots-dir ./metadata
61	```
62
63	Skip metadata or screenshots:
64	```bash
65	# Upload bundle only, skip metadata sync
66	gplay release \
67	--package com.example.app \
68	--track production \
69	--bundle app-release.aab \
70	--skip-metadata
71
72	# Upload bundle and metadata, skip screenshots
73	gplay release \
74	--package com.example.app \
75	--track production \
76	--bundle app-release.aab \
77	--listings-dir ./metadata \
78	--skip-screenshots
79	```
80
81	Combine listings and screenshots directories:
82	```bash
83	gplay release \
84	--package com.example.app \
85	--track beta \
86	--bundle app-release.aab \
87	--listings-dir ./metadata/listings \
88	--screenshots-dir ./metadata/images \
89	--release-notes @release-notes.json
90	```
91
92	### Manual sequence (when you need more control)
93
94	1. Create edit session:
95	```bash
96	EDIT_ID=$(gplay edits create --package com.example.app \| jq -r '.id')
97	```
98
99	2. Upload bundle:
100	```bash
101	gplay bundles upload \
102	--package com.example.app \
103	--edit $EDIT_ID \
104	--file app-release.aab
105	```
106
107	3. Update track:
108	```bash
109	gplay tracks update \
110	--package com.example.app \
111	--edit $EDIT_ID \
112	--track production \
113	--releases @releases.json
114	```
115	`--releases` takes a JSON array of track releases (or `@file`).
116
117	4. Validate edit:
118	```bash
119	gplay edits validate --package com.example.app --edit $EDIT_ID
120	```
121
122	5. Commit edit (publishes changes):
123	```bash
124	gplay edits commit --package com.example.app --edit $EDIT_ID
125	```
126
127	## Track Promotion
128
129	Promote a release from one track to another:
130
131	```bash
132	# Promote from internal to beta
133	gplay promote \
134	--package com.example.app \
135	--from internal \
136	--to beta
137
138	# Promote from beta to production with 25% rollout
139	gplay promote \
140	--package com.example.app \
141	--from beta \
142	--to production \
143	--rollout 0.25
144	```
145
146	## Staged Rollout Management
147
148	Start with a 10% rollout (fraction `0.1`):
149	```bash
150	gplay release \
151	--package com.example.app \
152	--track production \
153	--bundle app.aab \
154	--rollout 0.1
155	```
156
157	Increase to 50% (fraction `0.5`):
158	```bash
159	gplay rollout update \
160	--package com.example.app \
161	--track production \
162	--rollout 0.5
163	```
164
165	Halt rollout (pause distribution):
166	```bash
167	gplay rollout halt --package com.example.app --track production
168	```
169
170	Resume rollout:
171	```bash
172	gplay rollout resume --package com.example.app --track production
173	```
174
175	Complete rollout (release to 100%):
176	```bash
177	gplay rollout complete --package com.example.app --track production
178	```
179
180	## Release Notes Format
181
182	The single `--release-notes` flag accepts three shapes: a JSON array (multi-locale), plain text (auto-assigned to `en-US`), or an `@file` path pointing to either. There is no separate locale flag.
183
184	### JSON array format (multi-locale)
185	`release-notes.json` — a JSON array of `{language, text}` entries:
186	```json
187	[
188	{ "language": "en-US", "text": "Bug fixes and performance improvements" },
189	{ "language": "es-ES", "text": "Correcciones de errores y mejoras de rendimiento" },
190	{ "language": "fr-FR", "text": "Corrections de bugs et améliorations des performances" }
191	]
192	```
193	Pass it with `--release-notes @release-notes.json`.
194
195	### Plain text format (single locale)
196	Provide release notes as plain text — it is auto-assigned to `en-US`:
197	```bash
198	gplay release \
199	--package com.example.app \

People who liked this also viewed

6 picks

Type