v0.1.14 everywhere: version badge, pin examples, landing page, release request - #161
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
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.
Cuts v0.1.14, whose reason to exist is the C41 wheel bug: v0.1.13 shipped a keymap palette whose mouse wheel scrolled the view out from under the cursor, leaving
↵one keypress from running a row off screen. Fixed in #160 — onmain, but not in any binary anyone can install.In this release
Bumped
Cargo.toml+Cargo.lock, README badge and both pin examples,docs/index.html(header tag + download blurb).CLAUDE.md'sv0.1.13is left alone deliberately — it cites that release as the worked example of the squash-subject rule.Two commits, on purpose
The bump and the release request are separate so the PR title becomes the squash subject. #158 landed under its feature's subject because a one-commit PR hands GitHub the commit subject instead — the rule #159 just wrote into CLAUDE.md, applied here first.
After merge
.github/release-requestdispatches Release, which tagsv0.1.14from Cargo.toml itself and publishes four targets withSHA256SUMS.txt. The Homebrew sync will skip again (HOMEBREW_TAP_TOKENstill unset) — the tap needs its usual hand-rendered PR, the tenth in a row.