Roll back one PR
When a release breaks, every OTA service rolls back the whole release. If it had 12 pull requests and one broke checkout, you lose the 11 good ones too.
Healkite finds the change that broke it and rolls back only that change. The rest of the release stays live.
1. Know what's in each release
Publish with the Healkite CLI or GitHub Action from a git checkout. Each release then records its commit and the changes since the previous release: one entry per merged pull request (merge or squash) or direct commit, with the files it changed.
In CI, check out the full history so Healkite can list the changes:
- uses: actions/checkout@v4
with: { fetch-depth: 0 }2. Find the change that broke it
The SDK sends crash stacks with its error reports (a few per launch). When a
guarded rollout stops a release, and your CI is
connected, Healkite starts healkite blame in your CI. It:
- takes the errors that are new in this release (not seen on the previous one),
- rebuilds the release with a source map, to turn bundle positions into files and lines,
- runs
git blameon each failing line, and - matches the result to the pull request that changed it.
The release page then shows Why it stopped, for example:
PR #381 “Cart refactor” changed
src/screens/CartScreen.tsx:142, where 213 crashes (TypeError: undefined is not an object (evaluating 'cart.items.length')) happen. 87% of the evidence points at it.
The crashing line counts most; the functions that called it count less. Errors the previous release also had count a quarter. Without a source map, Healkite matches function names to changed files, which is less precise.
You can also run it yourself at the release's commit:
npx healkite blame rel_01j…If no new errors point at the release's code (for example a release stopped because checkouts dropped, without crashing), the page says so and lists the changes, so you can choose.
3. Roll back only that change
Click Roll back only this PR. Healkite starts your CI, which:
- checks out the release's commit,
- reverts that one change (
git revert, with-m 1for merge commits), - builds, signs and publishes the result as a guarded release, with the same steps and metrics as the release it replaces,
- pushes the revert as a branch and opens a pull request, so the next release doesn't bring the change back. (Allow GitHub Actions to create pull requests in the repository settings.)
The release page shows the progress and links the new release and the pull request:
Rolled back PR #381 only. v43 (v42 without #381) is rolling out, guarded. 11 other changes are still live.
Or from a terminal: npx healkite revert rvt_01j….
If later changes in the same release touch the same lines, the revert can't be applied cleanly. Healkite stops and tells you, and you roll back the whole release as before.
Requirements
- Releases published with the Healkite CLI (or GitHub Action) from a git checkout.
- The Healkite workflow in your repository, connected under Settings → CI, for the automatic analysis and the one-click rollback. Without it, the dashboard shows the commands to run yourself.
- React Native SDK with crash stacks (current version).