Lint to detect semantic versioning failures
Open
Nobody has claimed this yet.
A-new-subcommand
S-needs-design
- Dominant language
- Rust
- Stars
- 15.5k
- Forks
- 3k
- Avg merge
- 23h 30m
- Merged PRs (30d)
- 51
Description
It would be nice if cargo can give you warnings when you try to publish a new version of a package that obviously breaks the API of a previous version.
An important but easily overlooked part of this would be whether a type is sendable etc.
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
Start by reviewing Cargo's package publishing flow and how it could compare a new package version with a previous public API. The scope should include obvious API breaks and sendability concerns. Done means Cargo can warn before publishing when the proposed version violates semantic-versioning expectations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100