Lib.rs

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.

• socketioxide-redis

  • Imprecise dependency requirement fred = 10

    Cargo does not always pick latest versions of dependencies! Specify the version as fred = "10.1.0". If Cargo.lock ends up having an unexpectedly old version of the dependency, you might get a dependency that lacks features/APIs or important bugfixes that you depend on. This is most likely to happen when using the minimal-versions flag, used by users of old Rust versions.

    If you want to keep using truly minimal dependency requirements, please make sure you test them in CI with -Z minimal-versions Cargo option, because it's very easy to accidentally use a feature added in a later version.

    fred versions

• engineioxide

  • Optional dependency 'itoa' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Features 'itoa', 'memchr', 'unicode-segmentation' may have been unintentional.

    Crate features

No issues found in: socketioxide-core socketioxide socketioxide-parser-common socketioxide-parser-msgpack

If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
status = "deprecated" to their Cargo.toml.