Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .bumpy/ci-comparison-docs.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
---
---
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,7 @@ Then set up CI to automate versioning and publishing (see below).

## CI / GitHub Actions

No separate action to rely on — just call `bumpy ci` directly in your workflows. Two commands handle the entire release lifecycle:
No GitHub App to install, no separate action to rely on — just call `bumpy ci` directly in your workflows. Two commands handle the entire release lifecycle:

- **`bumpy ci check`** — runs on every PR. Computes the release plan from pending bump files and posts/updates a comment on the PR showing what versions would be released. Warns if any changed packages are missing bump files.
- **`bumpy ci release`** — runs on push to main. If pending bump files exist, it opens (or updates) a "Version Packages" PR that applies all version bumps and changelog updates. If the current push _is_ the Version Packages PR being merged, it publishes the new versions, creates git tags, and creates GitHub releases.
Expand Down Expand Up @@ -232,7 +232,7 @@ Bumpy is built as a successor to [@changesets/changesets](https://github.com/cha
- **Workspace protocol resolution** — changesets uses `npm publish` even in pnpm/yarn workspaces, so `workspace:^` and `catalog:` protocols are NOT resolved, resulting in broken published packages.
- **Custom publish commands** — changesets is hardcoded to `npm publish`. Bumpy supports per-package custom publish for VSCode extensions, Docker images, JSR, etc.
- **Flexible package management** — changesets treats all private packages the same. Bumpy lets you include/exclude any package individually.
- **CI without a separate action** — just `bunx @varlock/bumpy ci check` in any workflow, no bot or action to install.
- **CI without a separate action or bot** — changesets requires installing a [GitHub App](https://github.com/apps/changeset-bot) _and_ using a [separate GitHub Action](https://github.com/changesets/action). Bumpy replaces both with two CLI commands (`bumpy ci check` + `bumpy ci release`) that run directly in your workflows — no extra repos to trust, no app installation requiring org admin approval.
- **Automatic migration** — `bumpy init` detects `.changeset/`, renames it to `.bumpy/`, migrates config, keeps pending files, and offers to uninstall `@changesets/cli`.

## Development
Expand Down
17 changes: 15 additions & 2 deletions docs/differences-from-changesets.md
Original file line number Diff line number Diff line change
Expand Up @@ -139,9 +139,22 @@ Custom changelog formatters with full context (release info, bump files, dates).
- [changesets#556](https://github.com/changesets/changesets/issues/556) — changelog formatting (11 thumbs-up)
- [changesets#995](https://github.com/changesets/changesets/issues/995) — getChangelogEntry API (12 thumbs-up)

### CI without a separate action
### CI without a separate action or bot

`bumpy ci check` and `bumpy ci release` handle PR checks and release automation without needing a separate GitHub Action or bot installation. Just `bunx @varlock/bumpy ci check` in any workflow. No extra repository to trust, audit, or pin — your CI runs the same package you already depend on.
Changesets requires **two** separate pieces of CI infrastructure beyond the CLI:

1. **[changeset-bot](https://github.com/apps/changeset-bot)** — a GitHub App you must install on your repo that watches PRs and posts "missing changeset" comments
2. **[changesets/action](https://github.com/changesets/action)** — a GitHub Action (separate repo) that handles creating the version PR and publishing

This means you're trusting and auditing two additional dependencies with write access to your repo. The bot requires GitHub App installation (org admin approval in many orgs), and the action is a separate repository with its own release cadence and issues.

Bumpy replaces all of this with two CLI commands you run directly in standard workflows — `bumpy ci check` (PR comments) and `bumpy ci release` (version PR + publishing). No GitHub App to install, no separate action to trust. Your CI runs the same `@varlock/bumpy` package you already depend on. Works on any CI provider that can run shell commands — not just GitHub Actions.

- [changesets#134](https://github.com/changesets/changesets/issues/134) — requests for GitHub check integration (only available via bot)
- [changesets#1812](https://github.com/changesets/changesets/issues/1812) — can't filter which PRs the bot watches
- [changesets#946](https://github.com/changesets/changesets/issues/946) — bot doesn't check for new changes
- [changesets#1242](https://github.com/changesets/changesets/issues/1242) — bot/action version upgrade issues
- [changesets#43](https://github.com/changesets/changesets/issues/43) — can't customize bot messages

### Local bump file verification

Expand Down