Why upgrades get skipped
Nobody is against upgrading. It gets skipped because it is tedious and it never feels urgent. Then a security flaw is published in a version you are three majors behind, and the upgrade that would have taken ten minutes last year takes a week.
Staying roughly current is the cheap way to be able to patch quickly.
What Bugstack does
Bugstack does autonomous software maintenance. For upgrades:
- It scans daily for packages with a newer version, across npm, PyPI, RubyGems and Go modules.
- It opens upgrade pull requests for npm packages. One pull request per package or group of related packages.
- It rebuilds the lockfile in the same pull request, so your install step does not fail on a mismatch.
- It reports the rest. Out-of-date Python, Ruby and Go packages are listed on your Dependencies page. Pull requests for those are not opened yet.
Your CI runs on every upgrade pull request, so a version that breaks your tests shows red before anyone merges it.
How it keeps the noise down
| Rule | What it means for you |
|---|---|
| At most five upgrade pull requests open per repository | You are never facing a wall of them |
| Security upgrades go first | The ones that matter are not stuck behind routine bumps |
| Major versions wait | A breaking upgrade is not opened on its own unless it is needed to close a security advisory |
| Test-only packages are left alone | Fewer pull requests that change nothing your users run |
Each pull request says why this version was chosen, what kind of upgrade it is, whether the package runs in production, and where to read the release notes.
Who merges
By default, you do. An upgrade has no failing test to prove it, so on Bugstack’s default proof setting it waits for a person even on Autopilot. If you want routine upgrades to merge when your CI is green, set that repository’s proof to your CI alone.
Limits
- Upgrade pull requests are for npm today.
- Bugstack never edits your CI configuration or package-manager settings.
- It does not judge whether you should adopt a new major version. It tells you one exists.
If you already use a dependency bot and are happy with it, keep it. Bugstack’s case is that upgrades are one job among several, done by the same system that fixes the crash and the failed build. See how Bugstack compares with Dependabot and Renovate.
How to start
- Sign in with GitHub and start the 14-day trial. It includes $50 of credit.
- Install the Bugstack GitHub App on your repository.
Scanning starts when the repository is connected. No SDK is needed.
Questions
Which package managers does Bugstack upgrade?
It opens upgrade pull requests for npm packages, including projects that use pnpm lockfiles. It scans and reports PyPI, RubyGems and Go modules.
Will it open a pull request for every new version?
No. It caps open upgrade pull requests at five per repository, puts security upgrades first, and holds major versions back by default.
Can upgrades merge automatically?
Yes, if you choose that. Set the repository to Autopilot and its proof setting to your CI alone, and an upgrade merges when your checks pass. Major versions still wait for you by default.