"cargo publish" should error if there are path overrides
Open
Nobody has claimed this yet.
A-new-lint
A-overrides
Command-publish
S-needs-mentor
- Dominant language
- Rust
- Stars
- 15.5k
- Forks
- 3k
- Avg merge
- 23h 30m
- Merged PRs (30d)
- 51
Description
This might result in builds that succeed on the local machine, but fail when someone else tries to build the crate.
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 locating the cargo publish implementation and existing tests for path overrides; the issue does not name a file or entry point. Reproduce a publish attempt using a path override, then trace how publish validation reports errors. Done means cargo publish rejects crates with path overrides and the behavior is covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100