build: take libid-contracts 0.7.0 from crates.io, and follow the notary and libid-rs to their heads - #6
Merged
Conversation
libid-contracts v0.7.0 is published, so the lock entry that was resolved under a local path patch gains its registry source and checksum. Nothing else moves: the manifest already asked for 0.7.0, and the notary and libid-rs pins stay on their revs until those stacks release. Verified against the published crate: nightly fmt, cargo build --locked, clippy -D warnings, cargo test --all (18 unit, 4 integration incl. the Anvil end-to-end rotation). Assisted-by: Claude Fable 5.1 Signed-off-by: xgreenx <xgreenx9999@gmail.com>
xgreenx
marked this pull request as ready for review
September 8, 2026 18:39
xgreenx
changed the title
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
1 participant
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.
Stacked on #5. Two commits, manifests and lock only.
1.
libid-contracts0.7.0 from crates.io. The crate is published as of today (libid-org/libid-contracts v0.7.0), so the lock entry #5 resolved under a local path patch gains itssourceandchecksum. This is what #5's Rust job failed on (failed to select a version for the requirement libid-contracts = "^0.7.0").2. The notary and libid-rs at their branch heads.
notarymoves to the head of libid-org/notary#8 (cbf858a, stacked on #7), andlibid-crypto/libid-signermove with it to libid-rscc40b0c, the head offeat/ceremony-constructionsthat libid-rs#5 merged into, so the keeper and the notary share one copy of every libid-rs type. That head carries the reveal layouts that match what the verifier matches (libid-rs#8) and the refusal of a member that chunk framing runs through (libid-rs#9). Thetlsnpatch is unchanged. The manifest comments now name the branches the revs sit on.Verified locally at each commit:
cargo +nightly-2026-08-10 fmt --check,cargo build --locked,cargo clippy --locked --all-targets --all-features -- -D warnings,cargo test --locked --allwith anvil on PATH: 18 unit tests and 4 integration tests pass, includingkeeper_rotates_the_roots_then_reaches_steady_state, the end-to-end rotation against a deployedNotaryServiceandGoogleJwtRootsfrom the 0.7.0 artifacts.Merge order: notary#8 into its branch first is not required for this to build (the rev is reachable while notary#8's branch exists), but both pins return to tags only once the notary stack releases.