docs: use a version requirement that does not go stale - #23
Merged
Conversation
The install snippets pinned `= "1.9"`, which was already a release behind the moment 1.10.0 published — semantically fine (^1.9 resolves to 1.10.0) but it reads as stale on a 1.10.0 crate page, and would need a version bump of its own to correct each time. `= "1"` resolves the same way and never needs touching.
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.
The install snippets pinned
= "1.9", already a release behind once 1.10.0 published. Semantically fine (^1.9resolves to 1.10.0) but it reads stale on the crate page, and correcting it would need a bump each time.= "1"resolves identically and never needs touching.Docs only. Rides whatever ships next — no bump required for this.