# Varlock Releases Bumpy: A File-Based Versioning Alternative to Changesets

Bumpy offers a modern, monorepo-friendly approach to version management and automated changelog generation.

- **Source:** [InfoQ](https://brifing.si/source/68ac18af-a4f3-4f7c-9c2c-44d4af8f89dd)
- **Published:** 2026-11-07
- **Topic:** [technology](https://brifing.si/c/technology)
- **Original article:** <https://www.infoq.com/news/2026/11/bumpy-changesets-alternative/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global>
- **On Brifing:** https://brifing.si/s/6d820a7d-588d-41d4-979b-cc5c18f87791

## Modern Monorepo Versioning

Bumpy has emerged as a specialized tool for managing versions and changelogs in monorepo environments. Developed by the Varlock team and introduced in April 2026, it functions as a successor to the popular changesets utility. The project specifically aims to resolve over 120 long-standing issues identified within its predecessor's codebase.

## Workflow and File Structure

The tool utilizes a familiar workflow where contributors place markdown bump files into a dedicated directory. These files specify package release levels and changelog descriptions, which are then reviewed within pull requests. A continuous integration process consolidates these files into a single release pull request, simplifying the overall versioning lifecycle for teams.

## Advanced Dependency Propagation

Bumpy distinguishes itself through a configurable three-phase dependency propagation algorithm. This mechanism allows development teams to precisely control how peer dependency updates cascade through their package graphs. It provides native support for workspace and catalog protocols across major package managers including npm, pnpm, Yarn, and Bun, ensuring broad compatibility for developers.

## Lean CI Integration

The tool simplifies CI operations by requiring only two commands, bumpy ci check and bumpy ci release. These run directly within standard GitHub Actions workflows, eliminating the need for external GitHub Apps or third-party action repositories. This design choice reduces security concerns and simplifies the maintenance burden for engineering teams managing complex projects.

## AI-Driven Automation Features

Bumpy integrates AI capabilities by providing an agent skill that allows Large Language Models to inspect git changes. The agent identifies affected packages and automatically generates the necessary bump files via the bumpy add command. It is compatible with the Vercel Labs skills CLI, GitHub CLI, and as a Claude Code plugin.

## Prerelease and Branch Management

Version 1.14 introduced branch-based prerelease channels, where versions are calculated at publish time rather than being committed to git. This approach addresses common frustrations regarding the complexity of state management in previous tools. By avoiding git commits for prerelease states, the workflow remains cleaner and less prone to merge conflicts or errors.

## Migration and Ecosystem Adoption

The project supports automated migration for existing changesets users through a simple initialization command. Currently, it is used to manage the Varlock project alongside more than 25 related libraries and plugins. While some users have reported minor gaps regarding specific catalog detection, the team actively maintains the project to address community feedback.

## Competitive Landscape and Future

Following the release of changesets v3 in August 2026, the competitive landscape has tightened significantly. Bumpy continues to differentiate itself through specialized features like custom publish commands for Docker images or JSR targets. It remains an MIT-licensed, TypeScript-based solution, positioning itself as a flexible alternative for teams requiring advanced monorepo orchestration.

## Sources covering this story

- https://www.infoq.com/news/2026/11/bumpy-changesets-alternative/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global — 

---

_Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._
