RustCrypto / RustCrypto/actions
Add job for testing MSRV
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 5
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Right now we set crate MSRV manually in CI configs and use common Cargo.lock.
Instead we should retrieve rust-version from the tested crate's Cargo.toml and generate MSRV-compatible Cargo.lock.
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
Start by reviewing the current CI configs that set MSRV manually and use the shared Cargo.lock, then inspect each tested crate's Cargo.toml for its rust-version. The work is done when the CI job derives the MSRV from the crate and generates a compatible Cargo.lock for testing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100