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
12 changes: 6 additions & 6 deletions .bumpy/_changelog-formatter.ts
Original file line number Diff line number Diff line change
@@ -1,17 +1,17 @@
import type { ChangelogFormatter } from '@varlock/bumpy';

const formatter: ChangelogFormatter = (ctx) => {
const { release, changesets, date } = ctx;
const { release, bumpFiles, date } = ctx;
const lines: string[] = [];
lines.push(`## 🐸 ${release.newVersion}`);
lines.push('');
lines.push(`_${date}_`);
lines.push('');

const relevantChangesets = changesets.filter((cs) => release.changesets.includes(cs.id));
const relevantBumpFiles = bumpFiles.filter((bf) => release.bumpFiles.includes(bf.id));

if (relevantChangesets.length > 0) {
for (const cs of relevantChangesets) {
if (relevantBumpFiles.length > 0) {
for (const cs of relevantBumpFiles) {
if (cs.summary) {
const summaryLines = cs.summary.split('\n');
lines.push(`- ${summaryLines[0]}`);
Expand All @@ -24,11 +24,11 @@ const formatter: ChangelogFormatter = (ctx) => {
}
}

if (release.isDependencyBump && relevantChangesets.length === 0) {
if (release.isDependencyBump && relevantBumpFiles.length === 0) {
lines.push('- Updated dependencies');
}

if (release.isCascadeBump && !release.isDependencyBump && relevantChangesets.length === 0) {
if (release.isCascadeBump && !release.isDependencyBump && relevantBumpFiles.length === 0) {
lines.push('- Version bump via cascade rule');
}

Expand Down
5 changes: 4 additions & 1 deletion .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -20,4 +20,7 @@ env.d.ts

ignore

.claude/worktrees
.claude/worktrees

.DS_Store
images-raw
16 changes: 8 additions & 8 deletions DIFFERENCES_FROM_CHANGESETS.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Key differences from changesets:
- Out-of-range peer dep bumps match the triggering bump level (not always major) — a minor bump on `core` → minor bump on `plugin`, not major
- Dev deps never propagate by default (configurable per-package for bundled devDeps)
- `cascadeTo` config for source-side "when I change, cascade to these packages"
- Per-changeset `none` and `patch-isolated` to suppress propagation on specific changes
- Per-bump-file `none` and `patch-isolated` to suppress propagation on specific changes
- Warns about `^0.x` caret range gotchas and `workspace:*` on peer deps

See [docs/version-propagation.md](docs/version-propagation.md) for the full algorithm.
Expand Down Expand Up @@ -121,19 +121,19 @@ Bumpy includes the release date in every changelog heading by default.

### Migration tool

`bumpy migrate` converts `.changeset/` config and pending changesets to `.bumpy/`.
`bumpy migrate` converts `.changeset/` config and pending bump files to `.bumpy/`.

- (Previously listed under Planned)

### Conventional commits bridge

`bumpy generate` scans git history and auto-generates changeset files from conventional commits (`feat(scope): ...` → minor, `fix(scope): ...` → patch, `feat!(scope): ...` → major). Scope is mapped to package names automatically. Not a replacement for explicit changesets — a bridge for teams migrating from semantic-release, or a convenience when you want both.
`bumpy generate` scans git history and auto-generates bump files from conventional commits (`feat(scope): ...` → minor, `fix(scope): ...` → patch, `feat!(scope): ...` → major). Scope is mapped to package names automatically. Not a replacement for explicit bump files — a bridge for teams migrating from semantic-release, or a convenience when you want both.

- [changesets#862](https://github.com/changesets/changesets/issues/862) — conventional commits integration (70 thumbs-up, 21 comments)

### Pluggable changelog formatters

Custom changelog formatters with full context (release info, changesets, dates). Built-in `"default"` and `"github"` (with PR links + author attribution) formatters. Users can write custom formatters in TypeScript or JavaScript. Changesets' API is limited to two awkward string-returning functions — bumpy gives you the full context and you return the complete entry.
Custom changelog formatters with full context (release info, bump files, dates). Built-in `"default"` and `"github"` (with PR links + author attribution) formatters. Users can write custom formatters in TypeScript or JavaScript. Changesets' API is limited to two awkward string-returning functions — bumpy gives you the full context and you return the complete entry.

- [changesets#658](https://github.com/changesets/changesets/issues/658) — changelog titles not customizable (12 thumbs-up)
- [changesets#556](https://github.com/changesets/changesets/issues/556) — changelog formatting (11 thumbs-up)
Expand All @@ -143,19 +143,19 @@ Custom changelog formatters with full context (release info, changesets, dates).

`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.

### Local changeset verification
### Local bump file verification

`bumpy check` verifies that all changed packages on the current branch have corresponding changesets. Designed for pre-push hooks — compares your branch to the base branch, maps changed files to packages, and exits non-zero if any are missing. No GitHub API needed.
`bumpy check` verifies that all changed packages on the current branch have corresponding bump files. Designed for pre-push hooks — compares your branch to the base branch, maps changed files to packages, and exits non-zero if any are missing. No GitHub API needed.

Changesets has no built-in equivalent — users rely on the CI bot comment to catch missing changesets after pushing.
Changesets has no built-in equivalent — users rely on the CI bot comment to catch missing bump files after pushing.

---

## Planned / Not Yet Implemented

### Prerelease mode that actually works

Changesets' prerelease mode is described in their own docs as "very complicated" with "mistakes that can lead to repository and publish states that are very hard to fix." Key problems: no target on changesets, multi-branch corruption, exiting pre bumps ALL packages, bad interactions with linked/fixed groups.
Changesets' prerelease mode is described in their own docs as "very complicated" with "mistakes that can lead to repository and publish states that are very hard to fix." Key problems: no target on bump files, multi-branch corruption, exiting pre bumps ALL packages, bad interactions with linked/fixed groups.

- [changesets#729](https://github.com/changesets/changesets/issues/729) — exiting pre mode bumps all versions (14 comments)
- [changesets#786](https://github.com/changesets/changesets/issues/786) — can't control dist-tag in pre mode (13 comments)
Expand Down
21 changes: 21 additions & 0 deletions LICENSE
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
MIT License

Copyright (c) 2026 DMNO Inc.

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
Loading