Skip to content

v1.0.0-rc.2 — Vitals Gates That Fire

Choose a tag to compare

@yasserstudio yasserstudio released this 10 Oct 11:08
· 24 commits to main since this release

What's Changed

This release candidate fixes vitals gates that could not fire, found by running rc.1 against a real app. If you gate releases on vitals in CI, read the two breaking changes first.

Vitals gates

  • fix: gpc watch now reads vitals and breaches. Before, it never read a value, so --on-breach halt could not halt a rollout.
  • fix: gpc watch and gpc status no longer ask for days Google has not published yet, which failed silently when data lagged three days or more.
  • breaking: vitals rate thresholds are fractions (--threshold 0.02 means 2%). A value of 1 or more is refused with THRESHOLD_INVALID (exit 2). Our docs showed --threshold 2.0, which can never fire; change it to the fraction.
  • breaking: gpc train advance stays on its stage and exits 6 (TRAIN_GATE_NO_DATA) when a gate has no data, instead of advancing.
  • fix: --threshold compares the worst value of the most recent day (worst start type, report type or --dim value), not whichever row came last.
  • fix: gpc releases rollout increase --vitals-gate blocks the increase when it has no threshold, cannot read vitals or gets no data. Its vitals.thresholds.crashRate is now a fraction like everywhere else.
  • fix: gpc watch shows an unreadable metric with the reason and exits 4 if the final round could not check it.
  • fix: gpc status and gpc watch report the worst start type for slow starts instead of an average.

Vitals commands

  • fix: gpc vitals startup --dim and vitals error-count --dim work; slow starts appear again in overview, compare, compare-versions and status.
  • fix: gpc vitals rendering on a non-game app explains that the metric is games-only instead of blaming credentials.
  • fix: gpc vitals overview names metrics it could not read and exits 4 when all fail.
  • fix: a malformed --app value fails at once with INVALID_PACKAGE_NAME.

Docs

  • docs: every command in the docs now exists. 105 documented commands and flags that did not exist were fixed, and a check now runs with the tests.
  • docs: the SDK guide and core README show the real API; gpc train and CI vitals-gate pages describe what the commands really do.
  • docs: GPC collects no telemetry, now stated in the security guide and FAQ; the homepage leads with the standalone binary install.
  • docs: the blog has an RSS feed, cover images, and the earlier articles from Dev.to and X.

Full Changelog: v1.0.0-rc.1...v1.0.0-rc.2