Influxdata
/
influxdb
mirror of https://github.com/influxdata/influxdb.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
influxdb/workspace-hack
History
dependabot[bot] 18c2ca1bb5
chore(deps): Bump tower from 0.4.11 to 0.4.12 (#3817) 
* chore(deps): Bump tower from 0.4.11 to 0.4.12

Bumps [tower](https://github.com/tower-rs/tower) from 0.4.11 to 0.4.12.
- [Release notes](https://github.com/tower-rs/tower/releases)
- [Commits](https://github.com/tower-rs/tower/compare/tower-0.4.11...tower-0.4.12)

---
updated-dependencies:
- dependency-name: tower
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

* chore: update workspace-hack

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Raphael Taylor-Davies <r.taylordavies@googlemail.com>
Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
 		2022-02-23 11:14:15 +00:00
..
src feat: Results of using cargo hakari init workspace-hack 2021-11-19 09:20:35 -05:00
.gitattributes feat: Results of using cargo hakari init workspace-hack 2021-11-19 09:20:35 -05:00
Cargo.toml chore(deps): Bump tower from 0.4.11 to 0.4.12 (#3817) 2022-02-23 11:14:15 +00:00
README.md feat: Add CI jobs and documentation for the workspace-hack crate 2021-11-19 11:05:34 -05:00
build.rs feat: Results of using cargo hakari init workspace-hack 2021-11-19 09:20:35 -05:00

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 the workspace-hack crate. To fix this, run cargo 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 the workspace-hack crate. To fix this, run cargo hakari manage-deps and commit the changes.