Send more

Releases and source maps

Install two API calls in your deploy pipeline

Set release on every SDK, then tell Blipit about each release and deploy from your pipeline. With a GitHub token saved on the project, Blipit fetches the commits and marks suspect commits on each issue. Upload source maps so browser stack traces point at your source.

1Register a release

sh
curl https://in.blipit.io/api/v1/releases \
  -H "Content-Type: application/json" -H "X-Blipit-Key: <secret key>" \
  -d '{"version":"$VERSION","commit":"$GIT_SHA","previous_commit":"$PREVIOUS_SHA","repo":"owner/name"}'

2Record a deploy

sh
curl https://in.blipit.io/api/v1/deploys \
  -H "Content-Type: application/json" -H "X-Blipit-Key: <secret key>" \
  -d '{"version":"$VERSION","environment":"production","url":"https://example.com"}'

3Upload source maps

From your build step, with the secret key. The CLI scans the folder for .map files and uploads them keyed by release; filenames are the paths the browser loads the bundles from.

sh
BLIPIT_KEY=<secret key> npx @blipit/cli sourcemaps upload dist --release "myapp@$GIT_SHA"
Release and deploy with the CLI
npx @blipit/cli releases new "myapp@$GIT_SHA" --commit $GIT_SHA --repo owner/name --previous-commit $PREVIOUS_SHA
npx @blipit/cli deploys new "myapp@$GIT_SHA" --env production --url https://example.com

Good to know

  • The GitHub token is saved per project under Code owners; it is encrypted and only used against api.github.com.

Stuck? Email support@blipit.io. Keys and the exact DSN for each project are under API keys in app.blipit.io.