Bumpsmith

Upgrade npm and PyPI dependencies across breaking changes, verified with your tests in a sandbox.

LLM Mart 0 views 39 listing impressions

Dependabot and Renovate open the pull request. Bumpsmith makes it green:
it reads the changelog, fixes your code in a sandbox, proves it with your own tests, and shows its work.

CI License: Apache-2.0 Node npm and PyPI PRs welcome

Quick start · MCP & skill · How it works · Benchmarks · Self-hosting · Security

A real upgrade from the benchmark, no cuts: node-fetch 2 → 3 went ESM-only and dropped timeout. Bumpsmith wrote the wrapper, mapped the option, ran the tests, and its reviewer flagged the one thing tests couldn't prove. Watch the MP4.


Why

Keeping dependencies current is easy until a major version lands. The bot opens a pull request, CI goes red, and someone has to read three changelogs, find every call site, and fix them. That PR sits for weeks; meanwhile you fall further behind on security fixes.

Bumpsmith does that someone's job, and it is built to be trusted with it:

  • It proves the fix. Your install, build, typecheck, lint and tests run in an isolated container before and after the upgrade. No passing check, no "ready".
  • It shows its sources. Every breaking change it acts on is quoted word for word from the release notes, the migration guide or the type definitions, with a link.
  • It gets a second opinion. A separate reviewer and plain-code safety rules check the diff before anything is written, and say what they could not verify.
  • A human always merges. Bumpsmith opens a pull request or stages a patch. It never pushes to your default branch.

Quick start

GitHub Action: rescue red bot PRs automatically

npx bumpsmith init     # writes .github/workflows/bumpsmith.yml (wired to your CI) and .bumpsmith.yml

Add your model key as a repository secret. When CI fails on a Dependabot or Renovate pull request, Bumpsmith opens a companion PR with the same upgrade plus the code changes, links the two, and comments on the bot PR. If it can't produce a verified fix, it says why and lists the affected code instead. Full example: examples/bumpsmith.yml.

CLI: on your machine

Needs Node 22.13+ and Docker.

npx bumpsmith scan                     # which dependencies are a major (or more) behind; no AI
npx bumpsmith explain zod@4.1.0        # what breaks and where your code is affected
npx bumpsmith fix zod@4.1.0            # upgrade + fix + verify; writes a patch and evidence
npx bumpsmith fix zod@4.1.0 --apply    # ...and stage the patch if it was verified
npx bumpsmith rescue --github owner/repo --provider claude-code   # fix red bot PRs as PRs

Dashboard: review, apply, and run upgrades live

npx bumpsmith dashboard                # http://127.0.0.1:4477

The first start prints a one-time link that creates the owner account. Model keys and GitHub are connected in the browser, so no environment variables are needed (they are all optional; see .env.example). Everything Bumpsmith did is there:

From the project's README.

Related servers

Fetch Official

Fetch a web page and hand the agent readable text instead of raw HTML.

stdio
mcp-server-fetch 33 views
Filesystem Official

Give an agent scoped read and write access to directories you choose.

stdio
@modelcontextprotocol/server-filesystem 29 views
Git Official

Read repository history, diffs and branches as tools an agent can call.

stdio
mcp-server-git 27 views

Read-only MCP server for the OrchestKit docs: full-text search + Markdown fetch. No auth.

24 views