refactor(version): consume dunite-update-check, drop bunyip copy #496
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/DEV-530-consume-update-check"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Consumes the
dunite-update-checkleaf crate (dunite #38, DEV-530) and removes bunyip's copy.version.rskeeps the bunyip-specific version identity -current_version()(the compiled version) andgit_revision()(theBUNYIP_GIT_SHAbuild SHA) - and re-exportsUpdateChecker/UpdateStatusfromdunite_update_check. The localUpdateChecker/UpdateStatus/ cache / semver helpers and their unit tests are removed (parity tests live in the crate). Everycrate::version::{UpdateChecker, UpdateStatus}path (routes/version.rs, main.rs) is unchanged.main.rsconstruction now passes the two new config args:UpdateChecker::new(url, token, current_version().to_string(), "bunyip-api/<ver>").Pins
Adds
dunite-update-checkat1f536a2as a leaf dep (no dunite-core dep), so it pins independently and does not move the dunite-core graph rev.Validation
just check-containergreen:cargo fmt --all --check,cargo clippy --workspace --all-targets -- -D warnings,cargo test --workspace --all-targets.#DEV-530