b883c7c554
* chore: manual cargo update Dependabot seemed to have fallen behind a bit. ```console ❯ cargo update Updating crates.io index Updating git repository `https://github.com/apache/arrow-datafusion.git` Updating git repository `https://github.com/mkmik/heappy` Updating allocator-api2 v0.2.15 -> v0.2.16 Updating anyhow v1.0.71 -> v1.0.72 Updating async-compression v0.4.0 -> v0.4.1 Updating axum v0.6.18 -> v0.6.19 Updating blake3 v1.4.0 -> v1.4.1 Updating bstr v1.5.0 -> v1.6.0 Updating constant_time_eq v0.2.6 -> v0.3.0 Updating cpufeatures v0.2.8 -> v0.2.9 Updating dashmap v5.4.0 -> v5.5.0 Updating equivalent v1.0.0 -> v1.0.1 Updating http-range-header v0.3.0 -> v0.3.1 Updating hyper-rustls v0.24.0 -> v0.24.1 Updating itoa v1.0.7 -> v1.0.9 Updating num v0.4.0 -> v0.4.1 Updating pest v2.7.0 -> v2.7.1 Updating pest_derive v2.7.0 -> v2.7.1 Updating pest_generator v2.7.0 -> v2.7.1 Updating pest_meta v2.7.0 -> v2.7.1 Updating proc-macro2 v1.0.63 -> v1.0.66 Updating quote v1.0.29 -> v1.0.32 Updating rustversion v1.0.12 -> v1.0.14 Updating ryu v1.0.13 -> v1.0.15 Updating semver v1.0.17 -> v1.0.18 Updating seq-macro v0.3.3 -> v0.3.5 Updating stringprep v0.1.2 -> v0.1.3 Updating strum_macros v0.25.0 -> v0.25.1 Updating symbolic-common v12.2.0 -> v12.3.0 Updating symbolic-demangle v12.2.0 -> v12.3.0 Updating syn v2.0.26 -> v2.0.27 Updating toml_edit v0.19.12 -> v0.19.14 Updating ucd-trie v0.1.5 -> v0.1.6 Updating unicode-ident v1.0.9 -> v1.0.11 Updating winnow v0.4.7 -> v0.5.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.