Skip to main content

Releases

Introduction​

The Releases page answers the question every deploy raises: is the version I just shipped healthier than the one before it?

Every version of your app gets a row with its adoption, crash-free rate, and issue record — so a bad release shows itself within hours, not after the reviews come in.

The Releases Page​

Each release row shows:

  • Version — the app version, from your sessions, your CI, or a GitHub release tag.
  • Source — how Shipbook learned about the release: auto (detected from session traffic), api (reported by your CI), or github (a published GitHub release).
  • First seen — when the first session running this version arrived.
  • Adoption (24h) — the share of sessions in the last 24 hours running this version. This is a live number: right after a rollout you can watch it climb.
  • Crash-free sessions (7d) — the percentage of this version's sessions over the last 7 full days that ended without a crash.
  • New issues — issues that first appeared in this version, over the release's lifetime.
  • Regressed — issues that were marked Fixed and came back in this version (see Loglytics issue statuses).

Note that the columns deliberately cover different time spans — adoption tells you about right now, crash-free about the recent stable window, and the issue counts about the release's whole life.

Deploy Markers on the Bridge​

Every release also appears as a vertical marker on the Bridge graphs, at the moment it was deployed. When errors spike, one glance tells you whether the spike started at a deploy.

Markers use the exact deploy time when Shipbook knows it (api and github releases) and fall back to the first session observed (auto releases).

How Releases Are Created​

You don't have to do anything — and you can do more if you want exact deploy times:

Automatic​

Shipbook notices any new version appearing in your session traffic and creates the release for you. No setup. Detection runs from daily statistics, so a brand-new version's first seen date fills in within a day.

From GitHub​

If your account is connected to GitHub and the app is mapped to its repository (see Code Repositories), publishing a GitHub release records it in Shipbook instantly — with the exact publish time, the tag, and a link back to the release. A leading v in the tag is stripped, so tag v2.4.0 matches app version 2.4.0.

From Your CI​

Report a deploy from any build pipeline with one request, using an authentication key:

curl -X POST https://api.shipbook.io/v2/apps/<appId>/releases \
  -H "Authorization: Bearer <auth key>" \
  -H "Content-Type: application/json" \
  -d '{"version": "2.4.0", "notes": "Checkout redesign"}'

version is required; deployedAt (ISO date, defaults to now) and notes are optional. Posting the same version again updates it, so the call is safe to keep in your pipeline.

For AI Agents​

The same data is available over MCP through the get-releases tool — so your AI agent can answer "did crash-free drop after the last release?" directly from your logs.