Pre-release version numbers
Open
Nobody has claimed this yet.
A-dependency-resolution
A-semver
C-bug
E-hard
S-needs-design
- Dominant language
- Rust
- Stars
- 15.5k
- Forks
- 3k
- Avg merge
- 23h 30m
- Merged PRs (30d)
- 51
Description
Should Cargo do something special when a dependency has versions published with pre-release version numbers? Maybe not select them unless requested explicitly with cargo update --precise?
CC https://github.com/whitequark/rust-xdg/pull/9, @whitequark, @alexcrichton
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is named; begin by reading the issue discussion and the referenced rust-xdg pull request to understand the proposed pre-release selection rules. Define the expected behavior before locating Cargo's version-selection code and tests; done requires an agreed rule covering implicit and explicit pre-release requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100