Repository navigation
Conversation
`v0.1.1` was tagged before any of this existed: it carried three files and one subcommand, `doctor`. Every command the README's table names landed on `main` afterwards and has never been published, so the installer's default `latest` still hands users the doctor-only binary. Bump both version sites together. `enforce_min_version` compares against `stackward.__version__`, so a binary distributed as 0.2.0 while reporting 0.1.1 would be refused by any repository setting `min_version = "0.2.0"` — the gate rejecting the very release that satisfies it. The README's CI pin named v0.1.1 as the version to install, which is the doctor-only build; it now names this one. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013MP39PKyGDvTm2ppVQT6jw
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.
v0.1.1was tagged before any of the current surface existed: it carriedthree files and one subcommand,
doctor. Every command the README's tablenames landed on
mainafterwards and had never been published, so theinstaller's default
latestwas still handing users the doctor-only binary.This bumps both version sites together.
enforce_min_versioncomparesagainst
stackward.__version__, so a binary distributed as 0.2.0 whilereporting 0.1.1 would be refused by any repository setting
min_version = "0.2.0"— the gate rejecting the very release thatsatisfies it.
The README's CI pin named
v0.1.1as the version to install, which is thedoctor-only build; it now names this one.
Note on ordering. The
v0.2.0tag is already pushed and the releaseworkflow has built from it, because the tag push succeeded where the
direct push to protected
maindid not. The tag points at this branch'scommit, so the published binaries already report
0.2.0— merging thisbrings
maininto agreement with what shipped rather than changing it.🤖 Generated with Claude Code
https://claude.ai/code/session_013MP39PKyGDvTm2ppVQT6jw