CLAUDE.md: correct two release facts learned during v0.1.13 - #159
Merged
Conversation
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.
Docs only — no code, no CI-relevant change.
Two things the v0.1.13 release turned up that CLAUDE.md got wrong or didn't say:
The tap is one release behind, not four. The "v0.1.8 and v0.1.9 did not get one" note reads as an ongoing state; it's historical. v0.1.10, v0.1.11 and v0.1.12 were hand-synced (tap PRs roost 0.1.10 homebrew-tap#3, Fleet features: jump-to-attention, zoom, float, raw mode, keyboard copy, layouts, activity feed, broadcast #4, C2: tab-bar gutter — breathing room around every separator #5). Only v0.1.13 was outstanding — now open as roost 0.1.13 homebrew-tap#6.
Keep the version bump as a separate second commit. v0.1.13 landed on
mainashelp overlay: … (C41) (#158)instead ofv0.1.13 everywhere: …. GitHub defaults a squash subject to the sole commit's subject when a PR has exactly one commit; the PR title only wins with two or more. Nothing downstream breaks (the release keys off Cargo.toml), but the log stops being readable by release.