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.

• microwave

  • Dependency async-std ^1.13 has issues

    It may not be actively developed any more. Consider changing the dependency.

    async-std crate

  • Dependency serde_yaml ^0.8 has issues

    It may not be actively developed any more. Consider changing the dependency.

    serde_yaml crate

  • Dependency bevy ^0.18 is outdated

    Consider upgrading to 0.19.0 to get all the fixes and improvements.

    In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.

    bevy versions

  • Dependency cpal ^0.17 is outdated

    Consider upgrading to 0.18.1 to get all the fixes and improvements.

    cpal versions

• tune-cli

  • Dependency async-std ^1.12 has issues

    It may not be actively developed any more. Consider changing the dependency.

    async-std crate

  • Dependency serde_yaml ^0.8 has issues

    It may not be actively developed any more. Consider changing the dependency.

    serde_yaml crate

• tune, tune-cli

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["multimedia::audio"] to the Cargo.toml.

    Even if there are no categories that fit precisely, pick one that is least bad. You can also propose new categories in crates.io issue tracker.

    List of available categories

• rocket_extra_codegen

  • Dependency quote ^0.6.3 is significantly outdated

    Upgrade to 1.0.46 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.

    quote versions

  • Dependency syn ^0.15.26 is significantly outdated

    Upgrade to 2.0.119 to get all the fixes, and avoid causing duplicate dependencies in projects.

    syn versions

  • Latest stable release is old

    It's been over 7 years. Is this crate still maintained? Make a new release, either to refresh it, or to set

    [badges.maintenance]
    status = "deprecated"
    

    (or "as-is", "passively-maintained").

    If the crate is truly stable, why not make a 1.0.0 release?

    Maintenance status field docs

No issues found in: magnetron fluid-xenth

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