Releases, source maps & suspect commits

1 · Tag events

Set release: 'web-app@1.4.2' in your SDK init (or service.version via OTel). That alone lights up first-seen/last-seen per release and release filters.

2 · Register the release (commits + deploys)

curl -X POST https://jentry.app/api/v1/projects/<projectId>/releases \
  -H "Authorization: Bearer <api token>" -H "Content-Type: application/json" \
  -d '{
    "version": "web-app@1.4.2",
    "commits": [{ "sha": "abc123", "message": "fix checkout", "author": "dev@team.com",
                   "filesChanged": ["src/checkout.ts"] }],
    "deploys": [{ "environment": "production" }]
  }'

With commits + changed files registered, each issue shows a suspect commit — the commit whose files intersect the crashing stack frames.

3 · Upload source maps (browser builds)

curl -X POST https://jentry.app/api/<projectId>/artifacts \
  -H "Authorization: Bearer <secretKey>" -H "Content-Type: application/json" \
  -d '{ "release": "web-app@1.4.2",
        "files": [{ "name": "app.min.js.map", "content": "<map json>" }] }'

Note the auth: artifacts use the project secret key, never the public DSN key. Frames are de-minified server-side for events carrying that release.

Release health

• Session pings from the SDKs feed crash-free rate and adoption per release (both Sentry and native session formats are accepted).
• Resolve an issue 'in release X' or 'in next release' — a recurrence in a newer release re-opens it as regressed.
• The Releases page ranks releases by adoption, crash-free %, new issues and events.