0.15.0: restore the version free-names rolled backwards - #31
Merged
Conversation
The free-names branch was cut when master was 0.12.0 and bumped to 0.13.0 in its feature commit, the convention here. By the time it merged, `torrent` (#28) and porkbun's `check`/`register` (#29) had taken master to 0.14.0, and the squash replayed the older bump on top — so a release that added a command published a lower version than the one before it. 0.15.0 rather than 0.14.1: free-names is a new command, and a new command is a minor here. Worth knowing for next time: a hand-maintained version in the feature commit only works while one branch is in flight. A squash does not conflict on it when the surrounding lines still match, so nothing catches the regression at merge time — only reading the tag afterwards does. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XGe9mWC6FvUjT6p1HCVjba
ThreatCrush Security Scan16 finding(s) HIGH/CRITICAL: 5 | MEDIUM: 2 | LOW: 9
Snippets are redacted; ThreatCrush never prints matched credential material. |
This was referenced Aug 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
free-namesbranch (#30) was cut when master was 0.12.0 and bumped to 0.13.0 in its feature commit, the convention here. By the time it merged,torrent(#28) and porkbuncheck/register(#29) had taken master to 0.14.0, and the squash replayed the older bump on top — so a release that added a command published a lower version than the one before it.0.15.0rather than0.14.1:free-namesis a new command, and a new command is a minor here.Worth knowing for next time: a hand-maintained version in the feature commit only works while one branch is in flight. A squash does not conflict on it when the surrounding lines still match, so nothing catches the regression at merge time — only reading the tag afterwards does.
🤖 Generated with Claude Code
https://claude.ai/code/session_01XGe9mWC6FvUjT6p1HCVjba