You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cut v0.9.91: July 15, 2026 Play policy tracking, dependency health, and a docs/SEO refresh.
- bump @gpc-cli/cli 0.9.90 -> 0.9.91, @gpc-cli/core 0.9.75 -> 0.9.76 (changed packages only; api/auth/config/plugins unchanged)
- stamp version and test count (2,498) across README, docs, config JSON-LD, CLAUDE.md, and the LLM-facing files; historical entries left as-is
- add v0.9.91 changelog entries (root, docs, cli package)
Feature work landed in the prior commits this cycle: July 15 policy preflight + verify checklist, safe dependency minors, e2e assertion fix, and the docs/SEO pass.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,16 @@ Versioning: `0.9.x` pre-release series → `1.0.0` public launch.
7
7
8
8
---
9
9
10
+
## v0.9.91
11
+
12
+
Google Play July 15, 2026 policy update, dependency health, and a docs refresh.
13
+
14
+
- feat: `gpc preflight` and `gpc verify checklist` track Google's July 15, 2026 policy update. The `READ_CALL_LOG` finding notes that account verification via phone call is no longer an accepted use case and points to the Digital Credentials API (or SMS Retriever API). A new advisory and checklist step cover the mandate that every app on your account be registered in Play Console, since unregistered apps risk removal.
15
+
- chore: safe dependency updates (google-auth-library, protobufjs, yauzl, and dev tooling).
16
+
- docs: outcome-led homepage, answer-first intros on the Games and Android CLI pages, and benefit-led page metadata.
17
+
18
+
---
19
+
10
20
## v0.9.90
11
21
12
22
Release readiness, review insight, and Play Games sync.
- Current version: v0.9.90 — pre-release series (`0.9.x` → `1.0.0` public launch)
47
+
- Current version: v0.9.91 — pre-release series (`0.9.x` → `1.0.0` public launch)
48
+
- v0.9.91: Google Play July 15, 2026 policy update + dependency health + docs/SEO refresh. Preflight's `READ_CALL_LOG` finding now notes that account verification via phone call is no longer an accepted use case (points to the Digital Credentials API + SMS Retriever API); the `policy-developer-verification` advisory and `gpc verify checklist` add the mandate that every app on your account be registered in Play Console (unregistered apps risk removal). Safe dev/prod dependency minor bumps (google-auth-library 10.9, protobufjs 8.6.5, yauzl 3.4.0, eslint/vitest/turbo/tsx/prettier). Docs: outcome-led homepage, answer-first AEO intros, benefit-led meta. Dep majors (typescript 6, commander 15, ai 7) held to post-1.0.0. 2,498 tests.
48
49
- v0.9.90: release readiness, review insight, and Play Games sync. `gpc doctor --score` (A–F release-readiness grade) + `--badge` (shareable shields.io README badge). `gpc reviews list --sort newest|oldest|rating` presets + `gpc status --full` local review topic/sentiment breakdown. Games icon upload (`gpc games … set-icon`) and directory bulk sync (`gpc games … push/pull`); Games Management reset deferred (needs player-consent OAuth). Developer-verification advisory in preflight + `gpc verify checklist` (Sept 30 2026 enforcement). CI: Socket scan skips Dependabot PRs. Pre-soak security audit passed (Claude senior-security skill, this cycle). Last release before the stability soak. 2,495 tests.
49
50
- v0.9.89: preflight scanner reliability fix (GH #89). `gpc preflight` (and `preflight manifest` / `preflight permissions`) crashed with a `TypeError` and then hung when scanning an AAB/APK on the standalone (Homebrew) binary — yauzl's file-descriptor reader was handed a null fd under the Bun-compiled binary. The offline reader now loads the archive with `yauzl.fromBuffer` (no fd), so the standalone binary behaves the same as the npm (Node) install, and the ZIP read is guaranteed to settle with a bounded timeout backstop so it can never hang. 2,421 tests.
50
51
- v0.9.88: preflight compliance refresh for Google Play's October 28 2026 sensitive-permission deadlines (apps targeting Android 17/API 37+). Contacts check now cites the Oct 28 2026 date + Android Contact Picker (`Intent.ACTION_PICK_CONTACTS`); new `location-minimal-scope` rule flags `ACCESS_FINE_LOCATION` (info; warning at API 37+); geofencing date corrected from the stale May 15 2026 to Oct 28 2026; `gpc init` scaffolds `targetSdkMinimum: 36` (was 35, below the current Play floor). 2,418 tests.
@@ -66,7 +67,7 @@ e2e/ → End-to-end tests
66
67
- v0.9.72: API compliance patch (error reports endpoint, input validation).
67
68
- v0.9.71: `gpc doctor` quota proximity check (warns at >80% daily/per-minute API usage) and plugin health check (discovers, loads, reports each plugin).
68
69
- v0.9.70: `--in-app-update-priority <0-5>` and `--retain-version-codes <csv>` flags on upload, `default.txt` Fastlane-style changelog fallback via `--notes-dir`, promote preserves `inAppUpdatePriority` + `name`, GitHub Actions Node.js 22.
69
-
- 2,495 total tests, 7 packages building, 90%+ line coverage on all core packages
70
+
- 2,498 total tests, 7 packages building, 90%+ line coverage on all core packages
70
71
- Changelog-generation series (v0.9.61 → v0.9.64): complete. `gpc changelog generate --target play-store --locales auto --ai --apply` does commit → translated Play Store notes → written into draft release, one command.
71
72
- v0.9.63 highlight: AI-assisted Play Store translation. `gpc changelog generate --target play-store --locales auto --ai` translates non-source locales via the user's own LLM key. Auto-detects env priority `AI_GATEWAY_API_KEY` → `ANTHROPIC_API_KEY` → `OPENAI_API_KEY` → `GOOGLE_GENERATIVE_AI_API_KEY`. Non-reasoning model defaults. Gateway path unlocks cost-per-run in USD. All 4 AI SDK deps lazy-loaded (cold-start preserved).
72
73
- v0.9.62 highlight: multilingual Play Store release notes. `gpc changelog generate --target play-store --locales <csv|auto>` emits per-locale "What's new" text with 500-char budget enforcement.
@@ -76,7 +77,7 @@ e2e/ → End-to-end tests
76
77
77
78
## Testing
78
79
79
-
- Vitest for all tests (2,495 total across 7 packages + e2e)
80
+
- Vitest for all tests (2,498 total across 7 packages + e2e)
80
81
- Tests in `tests/` directory per package
81
82
- Mock external APIs — never call real Google APIs in tests
82
83
- Mock fetch with `vi.stubGlobal("fetch", mockFn)` for API tests
Copy file name to clipboardExpand all lines: apps/docs/guide/faq.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,7 +77,7 @@ See the [CI/CD guide](../ci-cd/) for copy-pasteable GitHub Actions, GitLab CI, B
77
77
78
78
### Is it stable enough for production CI/CD?
79
79
80
-
2,495 tests across 7 packages. 90%+ line coverage on all core packages. Every write operation supports `--dry-run`. Semantic exit codes for CI branching. Validated against production apps. The CLI is in a pre-release stability soak before v1.0.
80
+
2,498 tests across 7 packages. 90%+ line coverage on all core packages. Every write operation supports `--dry-run`. Semantic exit codes for CI branching. Validated against production apps. The CLI is in a pre-release stability soak before v1.0.
Copy file name to clipboardExpand all lines: apps/docs/guide/free-to-use.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -97,7 +97,7 @@ Not required. You may display a "Uses GPC" badge if you want (see `/users/` once
97
97
98
98
### What happens if the maintainer stops shipping?
99
99
100
-
The source is on GitHub. Forks are permitted for internal use. The current approach is single-maintainer by design — that gives us quality control today and succession risk tomorrow. We mitigate the succession risk by keeping the project fully documented, heavily tested (2,495 tests at 90%+ coverage), and publicly versioned.
100
+
The source is on GitHub. Forks are permitted for internal use. The current approach is single-maintainer by design — that gives us quality control today and succession risk tomorrow. We mitigate the succession risk by keeping the project fully documented, heavily tested (2,498 tests at 90%+ coverage), and publicly versioned.
0 commit comments