I’m the author of Bumpy, a zero-config CLI tool for automating versioning and changelogs in monorepos.
The Problem: Monorepo tooling often feels too heavy. While tools like Changesets are excellent, they rely on a file-based workflow (creating "intent" markdown files), which adds extra steps. Nx Release is powerful but feels heavy if you aren't already fully bought into the Nx ecosystem.
The Solution: I wanted something that treats Git history as the source of truth without extra metadata files. Bumpy is designed for small to medium monorepos that already use Conventional Commits.
How it works:
- Auto-discovery: Finds packages (pnpm/npm workspaces, apps/*, etc.).
Analysis: Detects the last tag (e.g., project@version) and reads commits since then.
- Suggestion: Proposes the next version based on commit messages (Conventional Commits).
- Generation: Updates package.json and writes a clean, per-package CHANGELOG.md.
Key Features:
- Zero-config default (but configurable via bumpy.json).
- Supports independent versioning with per-project tags.
- Interactive mode + Dry-run support.
It’s meant to stay out of your way and just automate the release step.
I’d love to get your feedback:
- Does the "Git history as source of truth" flow feel robust enough for your workflows compared to the "intent file" model of Changesets?
- Are there edge cases in per-project tagging you've encountered with other tools?
At work, we recently started conducting retrospectives using Miro, but I found it to be a bit inconvenient for our needs. About a month ago, I stumbled upon Reddit post where someone shared an interesting tool for retrospectives. Inspired by that, I decided to create something similar but with a key difference—making it open source.
I'm excited to introduce Scrumlens, an Agile Retrospective Tool. The project is still in its early stages, with about a month of development behind it, and there's a lot more to come. I'm passionate about continuing to build and improve this tool, and I’d love to get your feedback and contributions.
GitHub seems to be going in the direction of solving the problem. Access to the repo only if you're a sponsor. But I think for people to start donating to you, you or your repo has to be known. It's a closed circle...
In many ways I agree. But one thing I can not understand because if we talk in the context of GitHub, the project users are users of GitHub and they are probably the developers themselves and know the value of labor, well, I think they do.
I am excited that massCode is released to version 2.0 .
What it is and why
massCode is a snippet manager for developers that helps you conveniently organize pieces of code and have quick access to them. Multilevel folders and tags are used for organization, and each snippet has fragments for even more granular structuring. The app supports Markdown so it can be used as a notebook if needed.
What's New
The new version of massCode is built on Electron 16, Vue 3 and TypeScript.
Electron v16 which gives you the ability to create a build for M1, Vue 3 & Vite is a very fast development and the final build of the frontend of the application.
In the new version of the application I am abandoning Monaco editor in favor of Ace editor, as it is a more lightweight library. Ace also supports much more language syntax highlighting and TextMate, which is more common than the proprietary Monarch for Monaco editor. The current version of massCode supports syntax highlighting for more than 170 languages.
The new version features a database based on plain JSON. The new version has API server available on localhost, which allows integration with other third party applications, e.g. Raycast or Alfred. Raycast extension is already ready.