docs(playstore): record v0.4.14 production rollout (versionCode 151) (#171)

Tag pushes only reach the internal track; production is a separate manual
workflow_dispatch that rebuilds and gets its own versionCode. Document that
path and start a release-history table so the AGE-105 Sentry measurement
window has a real rollout date to anchor on.

v0.4.14: internal versionCode 150 (run 50), production versionCode 151
(run 51), submitted to the production track 2026-08-14 14:22 UTC.

Co-authored-by: engineer <engineer@macbookpro.lan>
Co-authored-by: Paperclip <noreply@paperclip.ing>
This commit is contained in:
Den
2026-08-14 07:39:21 -07:00
committed by GitHub
parent 61f4b1177b
commit 2652cc2ca9

View File

@@ -84,6 +84,29 @@ For full company facts (D-U-N-S, address, governor, etc.) see `~/.agents/skills/
After 14 days on Closed testing with 12+ active testers → promote to Production.
### Promoting a tagged release to Production
Pushing a `v*` tag only publishes to the **internal** track — the workflow
defaults `track: internal` for non-dispatch runs. Production is a second,
manual dispatch off `main`:
```bash
gh workflow run publish-play-store.yml --ref main -f track=production -f status=completed
```
That dispatch **rebuilds** the AAB, so it gets its own versionCode
(`github.run_number + 100`) — it does not promote the internal artifact in
place. Expect the production versionCode to be one higher than the internal
one from the tag push, and never equal to `app.json`'s committed
`android.versionCode`.
### Release history (production track)
| Version | Internal versionCode (tag push) | Production versionCode (dispatch) | Production rollout (UTC) | Notes |
|---|---|---|---|---|
| v0.4.13 | 148 (run 48, cancelled) | **149** (run 49) | 2026-08-14 09:20 | waitlist retry queue (#166) |
| v0.4.14 | 150 (run 50) | **151** (run 51) | 2026-08-14 14:22 | Sentry client-side noise gate (#169) — post-deploy Sentry measurement window for AGE-105 starts at this date, not at merge |
---
## Files in repo