Stop naming versions the README cannot keep current - #41
Merged
Conversation
Three places named a specific version and all three had gone stale. The worst was a claim that npm "currently trails the website at 0.2.24" — npm serves 0.2.41, so the page was telling readers something false about our own distribution. The pin example and the attestation example both still pointed at 0.2.39, which is also the one recent release carrying two attestation predicates instead of three, so anyone following it got a weaker verification than we ship. Replaced with <version> placeholders, a link to npm for what npm actually serves, and codetruss-cli-latest.tgz for readers who just want the current release. Verified latest.tgz is a valid npm tarball, contains 0.2.45, and is byte-identical to the versioned archive. Co-Authored-By: Claude Opus 5 <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.
Three hardcoded versions, all stale. The npm line claimed we trail at
0.2.24when npm serves0.2.41— a false statement about our own distribution on the CLI's landing page. The pin and attestation examples both pointed at0.2.39, which is also the one recent release with 2 attestation predicates instead of 3.Now uses
<version>placeholders, links to npm for what npm actually serves, and offerscodetruss-cli-latest.tgz. Verified that archive is a valid npm tarball containing 0.2.45 and byte-identical tocodetruss-cli-0.2.45.tgz.Docs only.
🤖 Generated with Claude Code