OpenZeppelin / OpenZeppelin/Event-Scanner
Specify Minimal Dependency Versions Compatible with `event-scanner` Instead of Latest Versions
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 19
- Forks
- 7
- Avg merge
- 2h 15m
- Merged PRs (30d)
- 4
Description
We currently specify the latest dependency versions compatible with the scanner, even though older versions would be compatible with it too.
This reduces the number of potential users of our crate, as some users are in one way or another "forced" to use specific older versions of particular dependencies.
To address this, we should find the minimal compatible versions for both Rust itself and the crates the scanner depends on and update Cargo.toml to use those.
We should also update our CI to test the scanner:
- With minimally compatible versions of dependencies (specified in Cargo.toml)
- With latest versions of dependencies.
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 with Cargo.toml to inventory the scanner's Rust and crate dependencies, then inspect the repository's CI configuration. Determine the minimal compatible versions and configure CI to test both those versions and the latest dependency versions. Done means Cargo.toml and CI cover both compatibility ranges.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100