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.
ext-php-rs
Dependency zip 6.0 is significantly outdated
Upgrade to 7.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.
ext-php-rs, cargo-php
Imprecise dependency requirement anyhow = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
anyhow = "1.0.100". IfCargo.lockends 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 theminimal-versionsflag, used by users of old Rust versions.This crate does not bump semver-minor when adding new features, so to be safe you get all the features/APIs/fixes that your crate depends on, require a more specific patch version.
bevy_ui_forms
Dependency bevy 0.13 is significantly outdated
Upgrade to 0.17.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.
Optional dependency 'bevy_ui_forms_form_proc' 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 'bevy_ui_forms_form_proc', 'wasm-bindgen-futures', 'web-sys', 'async-channel', 'arboard' may have been unintentional.
ext-php-rs-derive
Dependency darling 0.21 is outdated
Upgrade to 0.23.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
bevy_ui_forms_form_proc
Dependency darling 0.20.8 is outdated
Upgrade to 0.23.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
No issues found in: lsp_doc_stable
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance] to their
status = "deprecated"Cargo.toml.