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.

• l10n

  • Dependency indoc 1.0 is outdated

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

    indoc versions

• identifier

  • Latest stable release is old

    It's been over 4 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

• identifier, l10n_core, l10n_impl

  • Dependency thiserror 1.0 is a bit outdated

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

    thiserror versions

• l10n_core

  • Dependency self_cell 0.10 is outdated

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

    self_cell versions

  • Dependency toml 0.5 is outdated

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

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

    toml versions

• identifier_derive

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/mathieutricoire/identifier\.git

    At the moment we only support git, and attempt fetching when we index a new release. Cloning is necessary for lib.rs to gather data that is missing on crates.io, e.g. to correctly resolve relative URLs in README files, which depend on repository layout and non-standard URL schemes of repository hosts.

  • Dependency syn 1.0 is significantly outdated

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

    syn versions

  • README missing from crate tarball

    Cargo sometimes fails to package the README file. Ensure the path to the README in Cargo.toml is valid, and points to a file inside the crate's directory.

  • Latest stable release is old

    It's been over 4 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").

    Maintenance status field docs

• l10n_impl

  • Dependency syn 1.0 is significantly outdated

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

    syn versions

  • Dependency toml 0.5 is outdated

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

    toml versions

No issues found in: macro_files

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