Document dependency versions without duplicating current requirements. - #40
Merged
Merged
Conversation
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.
Document how to maintain dependency versions in installation examples and compatibility guidance. Publish the shared guidelines in
socketry-project0.3.11.Installation examples prefer Cargo commands that select a dependency and write its manifest requirement. Manifests and lockfiles remain authoritative for supported requirements and resolved selections, while explicit numeric references continue to explain compatibility boundaries, historical changes, migration steps, and reproducible examples. The guidelines also cover manifest examples and generating repeated version references from metadata.
The setup and release guides now direct readers to the resolved task provider's manifest instead of repeating provider-version lists. The release guide distinguishes that installed provider from the current source manifest and uses
cargo metadata --lockedto locate it.