demo · v140

Release Tagging

Crash reports without a deploy SHA are noise. Set git_sha, release, cohort once at page load — every future crash from this document carries them, which means your dashboard can finally answer "did the spike start when we shipped X?"

tags to attach

no tags set

future crash payload

awaiting crash
// At bootstrap, before any feature code runs.
crashReport.set("git_sha", "a7c3f2d1");
crashReport.set("release", "2026.05.31-canary");
crashReport.set("cohort", "us-west-rollout-12pct");

// Crash dashboards can now bucket by SHA.
// (Reports are delivered via the existing Reporting API endpoint.)

operational story

A regression dashboard that can't bucket by deploy SHA forces engineers to bisect by hand. The KV API closes the loop: the build pipeline injects the SHA into the bundle, the bundle calls crashReport.set on boot, the SRE dashboard groups by it. The same trick generalises to A/B bucket, locale, feature-flag set — anything that determines "which version of the code ran". Per-Document scope means crashes in a popup window carry its own tags, not the opener's.

see also