Only the upgrades your checks prove safe.
Dependabot opens a PR for every major and lets CI find out. JamiePulls runs your type-check, build, lint and tests before and after the upgrade, tries to fix what breaks, and only opens the pull request when everything that passed before passes again.
Free on public repos. Private repos: 14 days free, then $49/mo.
Two clicks to install. A green PR the same day.
No config file, no CI changes. Pick the repos, and JamiePulls works through your outdated majors one pull request at a time.
Learns what “working” means
Clones your repo into a sandbox and runs your type-check, build and tests before touching anything. Only checks that pass here count.
Tries the fix
Bumps the major and re-runs the checks. When they fail, it reads the errors and the upstream release notes and attempts a patch to your code. Up to 3 rounds.
Opens the PR only when green
Every baseline check passes again, or you never hear about it. Each PR lists exactly what changed and which checks it ran.
What you get that version bumpers don’t give you
| JamiePulls | Dependabot / Renovate | |
|---|---|---|
| Bumps the version and lockfile | Yes | Yes |
| Attempts to fix breaking changes | Yes, ships only if green | No |
| Runs your checks before opening the PR | Yes | No, CI finds out after |
| Red PRs in your queue | Never | Often, on majors |
Pricing
Per GitHub account or organization. Cancel any time from the dashboard.
- Public repositories
- Up to 5 repos
- 2 open upgrade PRs per repo
- 2 fix rounds per upgrade
- Private and public repositories
- Up to 25 repos
- 4 open upgrade PRs per repo
- 3 fix rounds per upgrade
- 14 days free, card required, cancel before day 14 and pay nothing
Questions
How is this different from Dependabot or Renovate?
They open a PR for every new version and let your CI find out whether it breaks. JamiePulls runs your checks first, on the untouched code and again after the upgrade, and only sends the upgrades that pass. When an upgrade breaks something, it reads the errors and the release notes and tries to fix your code; if it can’t get back to green, you never see that PR.
What if it can’t fix the upgrade?
Then you never see a PR. We only open one when every check that passed on your default branch before the upgrade also passes after it. A red PR is noise, so we don’t send them.
Does my code leave GitHub?
Your repo is cloned into a throwaway container to run install, build and tests, then deleted. Relevant files and error output are sent to the AI model that writes the fix. Nothing is kept after the job ends.
What languages?
JavaScript and TypeScript on npm, pnpm or yarn today. The package.json must be at the repo root.
What permissions does the app need?
Read and write access to code and pull requests on the repos you pick, nothing else. It pushes only to branches named jamiepulls/*, never to your default branch.