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.
rust-sc2
Dependency dirs ^3.0.1 is significantly outdated
Upgrade to 6.0.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.Dependency parking_lot ^0.11.0 is significantly outdated
Upgrade to 0.12.3 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 tungstenite ^0.13.0 is significantly outdated
Upgrade to 0.26.2 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency indexmap ^1.5.1 is outdated
Upgrade to 2.7.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency itertools ^0.10.0 is outdated
Upgrade to 0.14.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency ndarray ^0.15.1 is outdated
Consider upgrading to 0.16.1 to get all the fixes and improvements.
Dependency num-derive ^0.3.1 is outdated
Upgrade to 0.4.2 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency protobuf ^2.17.0 is a bit outdated
Consider upgrading to 3.7.0 to get all the fixes and improvements.
Dependency rand ^0.8.0 is a bit outdated
Consider upgrading to 0.9.0 to get all the fixes and improvements.
Dependency rustc-hash ^1.1.0 is a bit outdated
Consider upgrading to 2.1.0 to get all the fixes and improvements.
Latest stable release is old
It's been over 3 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"
).Users pay attention to the latest release date. Even if the crate is perfectly fine as-is, users may not know that.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["value-formatting", "web-programming"]
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 = ["starcraft", "bot", "ai", "ii", "low-level"]
(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.
sc2-macro
Buggy README path
The non-local path to readme specified as
\.\./README\.md
exposes a bug in Cargo. Please use a path inside the crate's directory. Symlinks are okay. Please verify the change doesn't break any repo-relative URLs in the README.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"
).Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["rust-patterns"]
to theCargo.toml
.Missing keywords
Help users find your crates. Add
keywords = ["rust-sc2", "macro", "procedural", "api", "proc-macro"]
(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.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.
sc2-proc-macro
Dependency syn ^1.0.33 is significantly outdated
Upgrade to 2.0.100 to get all the fixes, and avoid causing duplicate dependencies in projects.
Buggy README path
The non-local path to readme specified as
\.\./\.\./README\.md
exposes a bug in Cargo. Please use a path inside the crate's directory. Symlinks are okay. Please verify the change doesn't break any repo-relative URLs in the README.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"
).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
.