Add check if the latest patch version is used in the `compiler` field
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 36
- Forks
- 9
- Avg merge
- 1h 46m
- Merged PRs (30d)
- 1
Description
In most cases people don't realize the compiler field is a minimum version, and just specify the latest compiler version, e.g. currently 0.14.2. This is a bit unfortunate, because it will require the latest patch version to use the package and even just slightly outdated compiler versions such as 0.14.1 and 0.14.0 will refuse to compile the package.
Contributor guide
No contributing guide indexed for this repository
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
The issue names the package compiler field but no implementation file or test. Start by locating the validation entry point for package metadata and the existing compiler-version checks. Done means the checker detects compiler values that require only the latest patch version and reports the problem consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100