{
  "id": 18661334,
  "title": "Varlock Releases Bumpy: A File-Based Versioning Alternative to Changesets",
  "url": "https://urgent.news/2026/11/07/varlock-releases-bumpy-a-file-based-versioning-alternative-to",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-07T06:54:00.000Z",
  "source": {
    "name": "InfoQ",
    "slug": "infoq",
    "url": "https://www.infoq.com/news/2026/11/bumpy-changesets-alternative/"
  },
  "original_language": "en",
  "account": "Varlock has unveiled Bumpy, a self-proclaimed successor to the popular changesets tooling, designed as a version management and changelog solution for monorepos. First introduced in April 2026 via a Show HN post, Bumpy now lives under the @varlock/bumpy package on npm. The tool aims to resolve over 120 issues from its predecessor, Bumpy adheres to the well-known changesets workflow, where contributors create small markdown bump files in the .bumpy directory to declare package releases, levels, and corresponding changelog descriptions. These files can be reviewed in the PR diff, consolidated in a release PR by CI, and consumed upon merge.\n\nBumpy distinguishes itself from changesets with its comprehensive support for workspace and catalog protocols across npm, pnpm, Yarn, and Bun. It also offers per-package custom publish commands for VS Code extensions, Docker images, and JSR targets, and a configurable three-phase dependency propagation algorithm for teams to control how peer dependency bumps propagate through their graph. The CI process is streamlined with only two commands, bumpy ci check and bumpy ci release, allowing for seamless integration into GitHub Actions workflows without the need for additional trust or separate action repos.\n\nVersion 1.14 introduced branch-based prerelease channels, allowing for prerelease versions to be generated automatically at publish time and never committed to the git repository. This feature addresses concerns raised in the original changesets prerelease documentation, which described the pre mode as \"very complicated\" with states that are \"very hard to fix.\"\n\nAnother notable feature is Bumpy's AI integration, which includes an agent skill that guides large language models (LLMs) in inspecting git changes, identifying affected packages, and generating bump files using the bumpy add command. This feature can be installed via various CLIs, such as the Vercel Labs skills CLI, GitHub CLI, or as a Claude Code plugin.\n\nInstallation is straightforward, requiring a single install and init command that automatically migrates existing changesets projects. Bumpy has already been adopted by Varlock and over 25 related libraries and plugins.\n\nThe tool's flexibility extends to polyglot monorepos, where Bumpy is seen as a solution that addresses some of the known issues with changesets regarding custom publishing. However, as teams evaluate migration, certain gaps remain, such as Yarn 4.10 catalog detection. Bumpy's documentation now compares it to the changesets v3 release, acknowledging it as a \"substantial cleanup\" while pointing out remaining gaps around configurable propagation, catalogs, custom publish targets, and prerelease workflows. Relative to semantic-release, Bumpy retains the file-based model but adds a bumpy generate command to produce bump files from branch commits when teams wish to adopt both styles. The tool is MIT-licensed, built in TypeScript, and available on npm via the @varlock/bumpy package, with the full source and documentation hosted on GitHub.",
  "summary": "Bumpy is an MIT-licensed, TypeScript tool for version management and changelogs in monorepos. It follows the changesets workflow, using markdown bump files, and adds support for workspace and catalog protocols, custom publish commands, and branch-based prereleases. Changesets v3, released in August 2026, closed many earlier gaps, though differences remain. By Daniel Curtis",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}