Guard README install versions against drift #293
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/install-version-guard"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The README hard-codes the release in five places (the badge, the tarball URL and directory, and
cargo install --tag), and nothing ties them toCargo.toml. A release that forgets them ships a README pointing at the previous version.readme_install_snippets_match_cargo_versionnow fails when any of those snippets disagrees withCARGO_PKG_VERSION, listing each stale line. It only reads versions behind the four install markers, sofj release create v1.2.3and names likefj-claude-pluginare left alone, and it fails if it finds no snippets at all rather than passing on nothing. BumpingCargo.tomlalone to 0.6.1 locally fails it with all five lines. docs/release.md names the README in the bump step.Also corrects CLAUDE.md, which said tokens are never written to disk. They fall back to a 0600
tokens.tomlin the config dir when the keychain is unavailable orFJ_NO_KEYCHAIN=1is set.This is the fj half of the 0.7.0 "stop doc drift" work; the docs.fjord.sh half lands in fjord-docs.
Stacked on #292 (the rustls bump the audit gate needs); merge that first.