LukeMathWalker / LukeMathWalker/zero-to-production
Cargo audit failing on config
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.5k
- Forks
- 585
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/LukeMathWalker/zero-to-production/blob/970987c5f793af6fc8e557731c9bbb23b620451e/Cargo.toml#L19C1-L20C1
Noticed cargo audit failing on `config`. When looking at that repo, it looks like its dependency was updated in the main branch, but they haven't released a new version yet.
This at least removes the warning in the meantime and pins to the commit containing the move to config using yaml-rust2.
```
[dependencies]
config = { git = "https://github.com/mehcode/config-rs.git", rev = "e3c1d0b452639478662a44f15ef6d5b6d969bf9b" }
```
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
Open Cargo.toml at the dependency lines linked in the issue and run cargo audit to reproduce the config warning. Update the config dependency to the specified revision, then rerun cargo audit; done means the warning is removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, security
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100