Say Goodbye to Changelog Chaos: Introducing changesetgoo

If you ship libraries or APIs, you’ve undoubtedly felt the release day pain: “What actually changed in this release?” “Did we bump major, minor, or patch correctly?” “Wait, who was supposed to update the changelog?” Tracking these changes manually is tedious and error-prone, which is exactly why the Changesets workflow was created. By letting you record each change (along with its semver impact and a description) as you work, these entries are automatically merged into a single changelog at release time. This guarantees that users and tools know exactly what changed and how "breaking" a release actually is. Having spent time in the JS ecosystem working heavily with frameworks like React and Next.js, I've come to rely on the standard JS Changesets workflow. It provides a fantastic developer experience. But when stepping outside of that ecosystem, I hit a snag: I wanted that exact same workflow, but I didn't want to drag Node.js and npm into non-JavaScript projects. So, I built a solutio