7079de9b15
* chore: manual `cargo update` Sometimes dependabot gets behind or confused with a few depndencies, so running a manual update from time to time is good: ```console ❯ cargo update Updating git repository `https://github.com/alamb/arrow-rs.git` Updating crates.io index Updating git repository `https://github.com/apache/arrow-datafusion.git` Updating git repository `https://github.com/mkmik/heappy` Updating async-trait v0.1.68 -> v0.1.69 Updating bitflags v2.3.2 -> v2.3.3 Updating cpp_demangle v0.4.1 -> v0.4.2 Updating fd-lock v3.0.12 -> v3.0.13 Updating h2 v0.3.19 -> v0.3.20 Updating half v2.2.1 -> v2.3.1 Updating ipnet v2.7.2 -> v2.8.0 Updating is-terminal v0.4.7 -> v0.4.8 Updating itoa v1.0.6 -> v1.0.7 Adding linux-raw-sys v0.4.3 Updating phf v0.11.1 -> v0.11.2 Updating phf_codegen v0.11.1 -> v0.11.2 Updating phf_generator v0.11.1 -> v0.11.2 Updating pin-project-lite v0.2.9 -> v0.2.10 Updating proc-macro2 v1.0.60 -> v1.0.63 Updating quote v1.0.28 -> v1.0.29 Adding rustix v0.38.2 Updating rustls-pemfile v1.0.2 -> v1.0.3 Updating syn v2.0.18 -> v2.0.23 Updating whoami v1.4.0 -> v1.4.1 Updating windows-targets v0.48.0 -> v0.48.1 ``` * chore: Run cargo hakari tasks --------- Co-authored-by: CircleCI[bot] <circleci@influxdata.com> |
||
---|---|---|
.. | ||
src | ||
.gitattributes | ||
Cargo.toml | ||
README.md | ||
build.rs |
README.md
workspace-hack
This crate is a "workspace hack" crate managed by cargo hakari
.
Its purpose is to unify the features used by all crates in the workspace so that the crates share more dependencies and rebuild crates less. There are more details in hakari's documentation.
CI failures
If the workspace_hack_checks
CI job is failing, there are two possible reasons and solutions:
- If
cargo hakari generate --diff
fails, that means a crate has started or stopped using a feature of some crate and that feature isn't up-to-date in theworkspace-hack
crate. To fix this, runcargo hakari generate
and commit the changes. - If
cargo hakari manage-deps --dry-run
fails, that means a crate in the workspace isn't depending on theworkspace-hack
crate. To fix this, runcargo hakari manage-deps
and commit the changes.