Skip to content

Five steps for every change

From a provider change to a tested pull request.

  1. Watch

    Specs, releases and changelogs

  2. Match

    The exact calls a change touches

  3. Fix

    Only the affected call is rewritten

  4. Prove

    Checked against the provider's rule

  5. Deliver

    A pull request, ready for review

  1. Watch

    Specs, releases and changelogs

  2. Match

    The exact calls a change touches

  3. Fix

    Only the affected call is rewritten

  4. Prove

    Checked against the provider's rule

  5. Deliver

    A pull request, ready for review

More than changelogs

Eight sources, matched to the lines in your code.

FixApi reads changelogs, GitHub releases, OpenAPI specs, GraphQL schemas, Google API docs and SDK registries, and it can also read your CI logs and runtime traces. Every change it finds is matched to your code.

Only the calls that break

A mention is not a match. Only calls the change breaks get a fix.

Example: an integration change is mentioned in three places. The call to the removed endpoint breaks and gets a fix. A comment and a call that is not affected are held, with no pull request.

Only the broken call is rewritten

The model sees just the code around it.

A source file. Only the imports and the code around the broken call are sent to the model, and the broken call is rewritten into the fixed one.

Proven against the provider

The old request must break the rule and the fixed one keep it. With your test key, both can also run on the real API.

The old request is checked against the provider’s rule and breaks it. The fixed request keeps it.

Your keys, only for tests

Test keys are encrypted and only used to test your fixes.

Your test keys are stored encrypted and used only to test your fixes.

Then your own checks

In an isolated sandbox, with the network off.

Every fix runs your install, then the network is cut, then type check, lint, tests and build, in an isolated sandbox.

Every fix runs in a fresh sandbox

Installs reach package registries only. The tests run offline, and the sandbox is deleted after.

Every fix runs in a fresh sandbox. While dependencies install, it can reach package registries only. The internet is then turned off for the tests, and the sandbox is deleted after the run.

Your code, fixed for the new SDK

The affected call is rewritten. The version and lockfile change in the same pull request.

Example pull request: the rewritten call, package.json with the SDK version raised, and the lockfile from the tested install, together.

Only you merge

Each fix goes on a new branch as a pull request. FixApi never pushes to your main branch and never merges.

FixApi creates a new fixapi branch from the latest commit on your default branch and opens a pull request into it. It never pushes to your default branch and never merges: merging is your call.