CRT/storebound
1
0
Fork 0
Code Issues Pull requests Releases 1 Packages 1 Activity Actions

play managed publishing: console plan/verify play-publish-changes, ready-to-publish items in play status, desktop hint

Browse source
This commit is contained in:
CRTkafa 2026-10-24 11:56:07 +08:00
parent 29a9683ab7
commit 1bb43fd4a0
20 changed files with 184 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

11
skills/store-pitfalls/SKILL.md
View file

@ -1365,3 +1365,14 @@ that fails without the fix (see CONTRIBUTING.md).
with what was found. Opening waits up to 15 s: on Windows for a visible top-level window of a process
from the installed path (a running `--hidden` tray copy is shown by the single-instance handler, so a second start
without `--hidden` opens it), elsewhere for a non-`--hidden` process or a handoff (`tests/desktop-proc.test.ts`).
## 114. Managed publishing: approved, but nothing went live
- **What happens:** with `play.managedPublishing: true` Google approves the release and it waits in Publishing overview
("Changes ready to publish", button "Publish N changes", e.g. production plus Data safety). `play status` only said
"In review / ready to publish".
- **Do:** `storebound console plan play-publish-changes`, drive to Publishing overview, then the owner's "Publish N
changes" and its confirm dialog. Never "Discard changes" or "Stop managed publishing". Check with
`storebound console verify play-publish-changes` (API: no production release left ready to publish).
- **Guard:** `cli/lib/play-publish.ts` (ready list from tracks plus the public store page, the only signal the API
gives), the plan, the verify, the hint in `play status` / `status` / the desktop Releases tab. Non-track changes are
not visible to the API.