Four kinds of tool

KindExamplesWhat it doesWhat it does not do
Dependency update botDependabot, RenovateOpens pull requests that update dependencies and lock files, on a schedule you set.Does not rewrite your source to follow an API change.
Update confidence signalDependabot compatibility score, Renovate Merge ConfidenceShows how an update fared for other projects. Renovate says it flags undeclared breaking releases from test and adoption data of its users.Does not show that your own use of the API is correct.
Codemod runnerjscodeshift, vendor codemods such as @ai-sdk/codemodRuns a transform over many JavaScript or TypeScript files and edits them. jscodeshift uses recast and tries to keep your code style.A transform only covers what its author wrote. The runner does not check the result.
API change scannerEmendantMatches your code to supported SDK changes, links each finding to release evidence, offers patches, and grades them against your typecheck and tests.Does not update dependency versions. Covers only the changes in its feed.

How to combine them

  1. Let a dependency update bot open the version PR.
  2. If the vendor ships a codemod for the release, run it and read the diff.
  3. Run an API change scanner on the PR branch. Emendant reports what changed at the call sites it covers. It reports changes it cannot patch.
  4. Run your own typecheck, tests and build. Read the vendor's migration guide for what the tools did not cover.

Where Emendant fits

Emendant is the right addition when the SDK you upgrade is in its feed and the release changed an API you use. Check supported projects and releases. If your SDK is not covered, request it.

For detail, see Emendant and Dependabot and Emendant and the AI SDK codemod.

Coverage. Emendant reports the changes in its feed. A clean scan does not show that an upgrade is complete. See supported projects and known limitations.