Bumpy Moves Package Versioning Into Markdown Files
Engineering teams using npm, pnpm, Yarn or Bun can now declare releases in committed bump files instead of manual version edits.
Updated on Nov. 7, 2026 in Job Search

Varlock has released Bumpy, a file-based version management tool published under the @varlock/bumpy npm package. It is aimed at JavaScript and TypeScript teams that manage package releases across npm, pnpm, Yarn and Bun workspaces.
Why it matters
Release versioning is routine overhead for any team maintaining multiple packages, and Bumpy's approach moves that work into small markdown files that contributors commit alongside their code. For engineering-led businesses, this shifts how release responsibility is distributed across developers and how release approvals are logged.
Bumpy's maintainers say it addresses more than 120 open issues from the Changesets project, and the Varlock team uses it to release more than 25 related libraries and plugins. The figures are self-reported, and the source does not include independent adoption data or a head-to-head comparison with Changesets.
The players
Varlock
Varlock is the developer behind Bumpy and uses the tool internally to release its own library and plugin ecosystem.
Changesets
Changesets is an open-source versioning and changelog tool for JavaScript monorepos, and Bumpy positions itself as an alternative that addresses many of its open issues.
The details
Contributors add a markdown bump file to the .bumpy/ directory that declares which packages should be released and at what version level. CI then gathers these files into a release pull request, and the bump files are consumed when that PR merges. Bumpy also supports workspace: and catalog: protocols across npm, pnpm, Yarn and Bun, and ships an agent skill that teaches LLMs to generate the bump files.
Timeline
April 2026: Bumpy was first unveiled in a Show HN post.
August 2026: Changesets released v3, the competing tool it is positioned against.
Version 1.14 of Bumpy, which added branch-based prerelease channels, followed the initial launch.
Market Landscape
Bumpy enters a space where Changesets is the established file-based option for JavaScript monorepos, and its v3 release in August 2026 set the current baseline. Tools in this category compete on workflow friction and support for package-manager variants such as pnpm, Yarn and Bun.
Engineering managers running multi-package JavaScript repositories should evaluate whether a file-based release workflow would reduce coordination overhead for their teams. Review how release approvals and bump files would fit into existing CI pipelines before adopting either Bumpy or Changesets.
The takeaway
Teams weighing a versioning tool should track whether Bumpy's maintainers can substantiate the 120-issue figure through public issue resolution. Operators can test a file-based release workflow on a small set of packages before committing it across a full monorepo.
Further reading
For more on how engineering teams organize their work, browse the Job Search section.
Source note: This article includes information reported by InfoQ.


