Issues found
Based on crates you own that have been published to crates.io. The best way to monitor these issues is to subscribe to the atom feed in your RSS reader.
quincy
Locked dependency version tun-rs =2.7.3
This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.
Dependency tun-rs =2.7.3 is outdated
Upgrade to 2.7.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Easy way to bump dependencies:
cargo install cargo-edit; cargo upgrade -i; Also check out Dependabot service on GitHub.Optional dependency 'jemallocator' exposed as an implicit feature
Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using
dep:syntax. Feature 'jemallocator' may have been unintentional.
quincy-server
Dependency rand_core ^0.6.4 is outdated
Consider upgrading to 0.9.5 to get all the fixes and improvements.
In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.
sbe-codegen
Dependency convert_case ^0.6.0 is outdated
Consider upgrading to 0.10.0 to get all the fixes and improvements.
Dependency genco ^0.17.0 is outdated
Consider upgrading to 0.19.0 to get all the fixes and improvements.
xml-include
Dependency xml ^0.8.10 is significantly outdated
Upgrade to 1.2.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency thiserror ^1.0.0 is outdated
Upgrade to 2.0.17 to get all the fixes, and avoid causing duplicate dependencies in projects.
No issues found in: quincy-gui quincy-client privesc
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance] to their
status = "deprecated"Cargo.toml.