play-developer-console
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChinesePlay Developer Console
Google Play开发者控制台
Use the local Bun TypeScript CLI at:
bash
/Users/jyo/projects/tools/play-cliThe CLI is linked locally with Bun and exposes:
bash
play --helpFor Moshi Android, run commands from:
bash
/Users/jyo/projects/ai/moshi/marketingThe Play assets live in:
bash
play/
.env
metadata/
images/
release-notes/使用本地的Bun TypeScript CLI,路径为:
bash
/Users/jyo/projects/tools/play-cli该CLI通过Bun本地链接,可执行以下命令查看帮助:
bash
play --help针对Moshi Android应用,需在以下目录运行命令:
bash
/Users/jyo/projects/ai/moshi/marketingPlay Store相关资源存放在:
bash
play/
.env
metadata/
images/
release-notes/Workflow
工作流程
- Inspect and relevant local files before changing store assets.
play/CLAUDE.md - Run one Play edit-backed command at a time. Do not parallelize ,
play metadata,play app-info,play images, orplay bundlecommands.play tracks - Validate local listing text before upload:
bash
play metadata validate- Use read-only checks before and after changes:
bash
play metadata list
play app-info show
play tracks list --json
play tracks show production --json
play reviews list --limit 5- 修改商店资源前,请先查看及相关本地文件。
play/CLAUDE.md - 每次仅运行一个基于Play编辑会话的命令。请勿并行执行、
play metadata、play app-info、play images或play bundle命令。play tracks - 上传前验证本地列表文本:
bash
play metadata validate- 在修改前后执行只读检查:
bash
play metadata list
play app-info show
play tracks list --json
play tracks show production --json
play reviews list --limit 5Release Workflow
发布工作流程
Use the built-in track commands for release operations. Do not write ad hoc scripts against for normal release tasks.
src/api.tsAttach or update a release already uploaded to Play:
bash
play tracks release internal \
--version-code 6 \
--status completed \
--name "Moshi 2.8.2" \
--notes en-US=play/release-notes/en-US.txtPrepare a production draft with release notes:
bash
play tracks release production \
--version-code 6 \
--status draft \
--name "Moshi 2.8.2" \
--notes en-US=play/release-notes/en-US.txtIf a draft app has stale releases that block validation, clear the track first, then create the intended release:
bash
play tracks clear internal
play tracks release internal --version-code 6 --status draft --name "Moshi 2.8.2"When no flag is provided, reads all files in as localized release notes. Use only when intentionally omitting notes.
--notesplay tracks releaseplay/release-notes/--no-notes- For bugs or missing Play API behavior, patch , then run:
/Users/jyo/projects/tools/play-cli
bash
cd /Users/jyo/projects/tools/play-cli
bun run typecheck
bun testRetry from after the fix.
/Users/jyo/projects/ai/moshi/marketing使用内置的track命令执行发布操作。日常发布任务请勿针对编写临时脚本。
src/api.ts附加或更新已上传至Play Store的版本:
bash
play tracks release internal \
--version-code 6 \
--status completed \
--name "Moshi 2.8.2" \
--notes en-US=play/release-notes/en-US.txt准备带发布说明的生产环境草稿:
bash
play tracks release production \
--version-code 6 \
--status draft \
--name "Moshi 2.8.2" \
--notes en-US=play/release-notes/en-US.txt如果草稿应用存在过期版本导致验证受阻,请先清空发布轨道,再创建目标版本:
bash
play tracks clear internal
play tracks release internal --version-code 6 --status draft --name "Moshi 2.8.2"若未提供参数,会读取目录下的所有文件作为多语言发布说明。仅当有意省略说明时才使用参数。
--notesplay tracks releaseplay/release-notes/--no-notes- 若遇到Play API相关的bug或功能缺失,请修改,然后运行:
/Users/jyo/projects/tools/play-cli
bash
cd /Users/jyo/projects/tools/play-cli
bun run typecheck
bun test修复完成后,回到目录重试操作。
/Users/jyo/projects/ai/moshi/marketingAuth
认证
Moshi uses keyless local auth via ADC and a quota project in .
Do not create or require service account JSON keys unless the user explicitly asks.
gcloudplay/.envExpected env keys:
bash
PLAY_AUTH_MODE=gcloud
PLAY_QUOTA_PROJECT=play-cli-moshi-260429103059
PLAY_PACKAGE_NAME=app.getmoshi.androidMoshi通过 ADC及中的配额项目实现无密钥本地认证。除非用户明确要求,否则请勿创建或要求使用服务账号JSON密钥。
gcloudplay/.env预期的环境变量:
bash
PLAY_AUTH_MODE=gcloud
PLAY_QUOTA_PROJECT=play-cli-moshi-260429103059
PLAY_PACKAGE_NAME=app.getmoshi.android