Cut a new release to allow downstream users to be safe from RUSTSEC-2022-0090
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Review the recent rusqlite dependency bump and the project's release procedure first. The task is done when a new sqlite-cache version is uploaded to crates.io so downstream users receive the dependency update that avoids RUSTSEC-2022-0090.
Written by the indexing model from the issue text.
Description
The recent dependency bump on rusqlite means this crate's main development branch is no longer vulnerable to RUSTSEC-2022-0090 via older versions of rusqlite's dependency on a vulnerable version of libsqlite3-sys.
So if a new release could be uploaded to crates.io, downstream users of sqlite-cache can also benefit.
- Dominant language
- Rust
- Stars
- 25
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
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.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
TheLarkInn/aipm#2413 ·
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
alexgorbatchev/simple-ptt#15 ·
-
tooling
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
todo:ticket
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
taikoxyz/taiko-mono#22168 · 1 comment ·