Repository navigation
chore(deps): bump hyperlane and hyperlane-core to 21.12.0 - #22
Merged
Merged
Conversation
hyperlane-core 21.12.0 changes Server::route to take path: impl AsRef<str>; this repository registers routes through the #[route] attribute macro (inventory-based), which never calls Server::route, so no call sites change here. The same release also reduces http-constant's DATE header-name constant to pub(crate) visibility (rust-standards section 18), so the response header middleware now carries its own local DATE copy in application/middleware/request/const.rs per the section 18 consumer guidance. Cargo.lock intentionally still pins 21.11.0: crates.io serves 21.12.0 only after hyperlane-dev/hyperlane#43 merges and the publish workflow runs. Run cargo update -p hyperlane after that to refresh the lockfile.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bump
hyperlaneandhyperlane-corerequirements to21.12.0(from21.3.6/21.7.6).hyperlane-core 21.12.0 changes
Server::routetopub fn route<S>(&mut self, path: impl AsRef<str>)(hyperlane-dev/hyperlane#43). This repository registers all 131 routes through the#[route]attribute macro, which usesinventory::submit!+HookType::Routeand never callsServer::route— so no route call sites change here (grep -rn 'route::<'returns 0).One adaptation is required for a different change shipping in the same release: 21.12.0 reduces
http-constant'sDATEheader-name constant topub(crate)(hyperlane §18 const-visibility sweep, commit684f3c0). The response header middleware used that constant, so it now carries its own local copy:application/middleware/request/const.rs(new) —pub(crate) const DATE: &str = "date";application/middleware/request/mod.rs— wiremod r#const;+pub(crate) use r#const::*;Cargo.lockintentionally still pins 21.11.0: crates.io only serves 21.12.0 after hyperlane-dev/hyperlane#43 merges and the publish workflow runs. Refresh withcargo update -p hyperlaneafterwards.Verification
Verified locally with a temporary
[patch.crates-io]pointing at the hyperlane 21.12.0 working tree (patch section removed before commit):cargo build --workspace— clean (21.12.0 path-patched)cargo clippy --workspace --all-targets— 0 code warnings/errorscargo test --workspace --all-features— all suites pass (0 tests exist in this workspace)cargo fmt --all+--check— 0 diff, idempotentstaged_file_gate.py(pre-commit hook) — 0 new violationsroute::<T, P>patterns exist anywhere in the codebaseNotes
hyperlane = "21.12.0"until that PR merges and the publish job uploads 21.12.0 to crates.io. Merge this only after the lockfile refresh succeeds.