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.
logix
Dependency jiff 0.1.13 is significantly outdated
Upgrade to 0.2.10 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.
Dependency prettydiff 0.7.0 is significantly outdated
Upgrade to 0.8.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Published crate doesn't match its repository
Partially verified 37 files (includes 3 Cargo-generated).
Files in the crates.io crate compared to the repository:
Cargo.lock
not found.
Fetched
https://github.com/logix-tool/logix.git
b20dac2ed5998ed7a968794a821902354c7030e1.Checked on 2024-10-13
This check is experimental.
Dependency flexi_logger 0.29.1 is outdated
Upgrade to 0.30.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency thiserror 1.0.64 is a bit outdated
Consider upgrading to 2.0.12 to get all the fixes and improvements.
Easy way to bump dependencies:
cargo install cargo-edit; cargo upgrade -i
; Also check out Dependabot service on GitHub.Missing keywords
Help users find your crates. Add
keywords = ["logix", "config", "shell"]
(up to 5) to theCargo.toml
. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.
logix-type
Could not find the crate in the repository
Make sure the main branch of
https://github\.com/logix\-tool/logix\-type
contains theCargo.toml
for the crate. If you have forked the crate, change the repository property inCargo.toml
to your fork's URL.Dependency which 6.0.1 is significantly outdated
Upgrade to 7.0.3 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency smol_str 0.2.1 is a bit outdated
Consider upgrading to 0.3.2 to get all the fixes and improvements.
Dependency thiserror 1.0.58 is a bit outdated
Consider upgrading to 2.0.12 to get all the fixes and improvements.
Missing keywords
Help users find your crates. Add
keywords = ["logix", "logix-type", "token"]
(up to 5) to theCargo.toml
. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.
logix-vfs
Could not find the crate in the repository
Make sure the main branch of
https://github\.com/logix\-tool/logix\-vfs
contains theCargo.toml
for the crate. If you have forked the crate, change the repository property inCargo.toml
to your fork's URL.Dependency thiserror 1.0.61 is a bit outdated
Consider upgrading to 2.0.12 to get all the fixes and improvements.
Missing keywords
Help users find your crates. Add
keywords = ["logix", "logix-vfs", "vfs"]
(up to 5) to theCargo.toml
. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.
logix-xtask
Failed to verify create's content against its repository
Could not check any files
- warning: The crates.io package has no information about its path inside its repository.
- error: Repository doesn't exist: Can't checkout the repository. It's either gone or private: remote authentication required but no callback set; class=Http (34); code=Auth (-16).
- Make sure the
repository
URL inCargo.toml
is correct and works withgit clone
. The repository must be public.
- Make sure the
Checked on 2025-04-09
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["development-tools::build-utils"]
to theCargo.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.
Missing keywords
Help users find your crates. Add
keywords = ["xtask", "logix", "logix-xtask"]
(up to 5) to theCargo.toml
. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.
logix-type-derive
Could not fetch repository
We've had trouble cloning git repo from
https://github\.com/logix\-tool/logix\-type\.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.
README missing from crate tarball
Cargo sometimes fails to package the
README
file. Ensure the path to theREADME
inCargo.toml
is valid, and points to a file inside the crate's directory.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.