My Weird Prompts · Daniel Rosehill

SemVer, Changelogs, and the Social Contract of Code

April 6, 2026·21 min·1 clip
Conventional commits can drive semantic-release by turning commit text into version bumps and changelogs.
1. My Weird Prompts uses Daniel Sentevura-Prompter's prompt to connect semantic versioning, Keep a Changelog, and conventional commits. 2. Herman Poppleberry hosts the discussion, and Daniel Sentevura-Prompter's prompt matters because it frames release management as a user contract. 3. The episode asks what the SimViver spec is actually for: preventing dependency hell by making software distribution predictable. 4. The major, minor, patch model is explained with a house-and-bolt analogy, where a changed thread size breaks compatibility. 5. Version 0.x is described as the 'wild west phase,' where APIs are unstable and projects like React or Terraform can avoid the 1.0 contract. 6. The hosts call that 0.x behavior a 'legal shield' that lets maintainers bypass the expectations that come with stability. 7. A major version bump is described as an honest signal that users may need to rewrite code because of removed functions or changed data structures. 8. Keep a Changelog is introduced as a human-facing document with sections like added, changed, deprecated, removed, and fixed. 9. Conventional commits provide the automation layer with types like feat, fix, and breaking-change markers that tools can parse. 10. Semantic release can read those commit messages and decide whether to increment major, minor, or patch automatically. 11. The episode stresses that a missing exclamation point on a breaking change can accidentally ship a minor update that breaks users. 12. Simon Willison and Dataset are used as an example of release notes that explain why changes happened, not just what changed. 13. The show contrasts automated commit parsing with a human-maintained highlights section that acts like a movie trailer. 14. Yanked releases are framed as a reproducibility issue, because deleting version 2.1.0 can break a build that depended on it. 15. The keep-a-changelog approach is to mark a release as yanked and leave a warning in the notes rather than erase it. 16. Chrome, Firefox, and Angular are brought up to show that some version numbers function as calendar tracking or major rewrites rather than simple compatibility promises. 17. The tone is technical but conversational, with repeated analogies, clarifying back-and-forth, and some joking about 'fixed typo' entries. 18. The format is a host-led explanation with occasional direct questions, practical examples, and named tools like NPM, PIP, Git, Fossil, and Subversion. 19. Developers who maintain libraries or open-source projects will get the most value from this episode. 20. Casual listeners without software release experience may skip it.

As heard by us

Release notes as a social contract for people building on your code.

My Weird Prompts treats semantic versioning, keep a changelog, and conventional commits as more than housekeeping: they function as a social contract around release management.

Read the full review in PlayNext →

Why you'd press play

When a version number is supposed to be a contract, this episode makes the rules readable.

Read the full recommendation in PlayNext →
Listen to the show on