docs(release): point the README at v0.1.1 - #38
Merged
Conversation
The install commands pinned @v0.1.0 and the table still called it Current, which would have shipped a main whose README advertises a version older than the package it ships. Adds the v0.1.1 row and demotes v0.1.0 to Previous. The v0.1.0 highlights paragraph stays as written — it describes that release's features, which v0.1.1 does not change. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Release prep for v0.1.1, following the same shape as #25 did for v0.1.0: README lands on
devfirst, then thedev→mainpromotion PR.Without this, the release cut would put a README on
mainthat pins@v0.1.0in its install commands and calls v0.1.0 "Current", while the package it ships reports0.1.1.@v0.1.1.The "v0.1.0 highlights" paragraph is left as written — it describes that release's features, and v0.1.1 is a patch that does not change them.
install.shis untouched: itsv0.1.0mention is an illustration of theCURATOR_REFformat, not a pin (the default still tracksmain).Note the tag
v0.1.1does not exist yet — it gets pushed immediately after thedev→mainmerge, per CONTRIBUTING.🤖 Generated with Claude Code