move from changesets to bumpy

Author: theoephraim

.bumpy/README.md

@@ -0,0 +1,63 @@
+# 🐸 Bumpy
+
+This directory is used by [bumpy](https://bumpy.varlock.dev) to manage versioning and changelogs.
+
+Bumpy is a modern versioning tool for JavaScript/TypeScript projects (monorepos and single packages). It uses **bump files** — small markdown files in this directory — to declare pending version changes. These files are consumed during the release process to compute version bumps, update changelogs, and publish packages.
+
+## How it works
+
+1. When you make a change that should trigger a release, create a bump file (typically one per PR)
+2. Bump files accumulate on your main branch until you're ready to release
+3. At release time, bumpy merges all pending bumps into a release plan, updates versions and changelogs, and publishes packages
+
+## Creating bump files
+
+### Interactive
+
+```bash
+bunx bumpy add
+```
+
+### Non-interactive (useful for AI-assisted development)
+
+```bash
+bunx bumpy add --packages "package-name:minor,other-package:patch" --message "Description of changes" --name "my-change"
+```
+
+### By hand
+
+Create a `.md` file in this directory with YAML frontmatter mapping package names to bump levels (`major`, `minor`, `patch`, or `none`), and a markdown body for the changelog entry:
+
+```markdown
+---
+'package-name': minor
+---
+
+Added a new feature.
+```
+
+### From conventional commits
+
+```bash
+bunx bumpy generate
+```
+
+### Empty bump files
+
+For PRs that intentionally don't need a release (docs, CI, etc.):
+
+```bash
+bunx bumpy add --empty --name "docs-update"
+```
+
+## Keeping bump files up to date
+
+As a PR evolves, make sure its bump file stays in sync. If the scope of changes grows (e.g., a patch becomes a new feature), update the bump level and description to match. Reviewers and AI assistants should treat the bump file as part of the PR — just like tests and docs.
+
+## Files in this directory
+
+- `_config.json` — bumpy configuration
+- `README.md` — this file
+- `*.md` (other than README.md) — pending bump files
+
+📖 Full documentation: https://bumpy.varlock.dev

.bumpy/_config.json

@@ -0,0 +1,12 @@
+{
+  "$schema": "../node_modules/@varlock/bumpy/config-schema.json",
+  "baseBranch": "main",
+  "changelog": [
+    "github",
+    {
+      "internalAuthors": [
+        "theoephraim"
+      ]
+    }
+  ]
+}

.changeset/README.md

@@ -1,6 +1,6 @@
 ---
 name: work-on
-description: Work on an issue or PR - implement changes, add tests, update docs, lint, add changesets, and create a PR
+description: Work on an issue or PR - implement changes, add tests, update docs, lint, add bump file, and create a PR
 ---
 
 You are given an issue or external PR to implement. The input may be a URL, pasted issue text, or pasted PR diff/description.

.changeset/config.json

@@ -32,6 +32,10 @@ jobs:
       - name: Lint
         run: bun run lint --format junit -o reports/junit/js-lint-results.xml
 
+      - run: bunx @varlock/bumpy ci check
+        env:
+          GH_TOKEN: ${{ github.token }}
+
       - name: Test
         run: bun run test
         env:

.claude/skills/work-on/SKILL.md

@@ -38,12 +38,7 @@ jobs:
         run: bun run build
 
       - name: Create Release PR or Publish
-        uses: changesets/action@v1
-        with:
-          version: bunx changeset version
-          publish: bunx changeset publish
-          title: "[Changesets] Versioned release"
-          commit: "[Changesets] Create versioned package(s) for publishing"
+        run: bunx @varlock/bumpy ci release
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          NPM_CONFIG_PROVENANCE: true
+          GH_TOKEN: ${{ github.token }}
+          BUMPY_GH_TOKEN: ${{ secrets.BUMPY_GH_TOKEN }}

.github/workflows/ci.yml

@@ -1,5 +1,8 @@
 {
   "editor.formatOnSave": true,
+  "files.associations": {
+    "**/.bumpy/_config.json": "jsonc",
+  },
   "[typescript]": {
     "editor.defaultFormatter": "dbaeumer.vscode-eslint"
   },

.github/workflows/release.yml

@@ -11,7 +11,8 @@ Goal of the project is to provide a simplified, more ergonomic interface compare
 - Tested with `vitest`
 - Linted with `eslint`
 - Uses `bun` as package manager
-- Versioning/releases managed with `changesets`
+- Env vars (for testing) managed with `varlock`
+- Versioning/releases managed with `@varlock/bumpy`
 
 ## Common Commands
 - `bun test` — run tests (vitest in watch mode)