● Done. All five dependency bumps are applied to your working tree and verified. #524

Merged

navicore merged 1 commit from crypto-update into main

2026-06-01 13:49:36 +00:00

navicore commented

2026-06-01 13:45:12 +00:00

Owner

What changed

Manifests:

Cargo.toml — sha2 0.10→0.11, hmac 0.12→0.13, rand 0.9→0.10, pbkdf2 0.12→0.13
crates/runtime/Cargo.toml — rcgen 0.13→0.14

Code fixes for the breaking APIs:

crypto/hash.rs — new_from_slice moved from Mac to KeyInit (added the import, changed the call)
crypto/random.rs — rand 0.10 moved fill_bytes onto the Rng trait (use rand::{RngCore, rng} → use rand::{Rng,
rng})
http_client/integration_tests.rs — rcgen 0.14 renamed CertifiedKey.key_pair → signing_key (destructured as
signing_key: key_pair to leave the rest of the test untouched)

Cargo.lock resolved to hmac 0.13.0, pbkdf2 0.13.0, sha2 0.11.0, rand 0.10.1, rcgen 0.14.8. The old-generation
digest 0.10 / sha2 0.10 / crypto-common 0.1 still appear as duplicates — that's expected and harmless; aes-gcm
0.10 and ed25519-dalek 2.2 carry their own internal copies and don't share types with your code.

Verification

cargo check --workspace --all-targets --features full — clean
cargo clippy -p seq-runtime --features full --all-targets -- -D warnings — clean
crypto tests: 41 passed; TLS integration tests passed

What changed Manifests: - Cargo.toml — sha2 0.10→0.11, hmac 0.12→0.13, rand 0.9→0.10, pbkdf2 0.12→0.13 - crates/runtime/Cargo.toml — rcgen 0.13→0.14 Code fixes for the breaking APIs: - crypto/hash.rs — new_from_slice moved from Mac to KeyInit (added the import, changed the call) - crypto/random.rs — rand 0.10 moved fill_bytes onto the Rng trait (use rand::{RngCore, rng} → use rand::{Rng, rng}) - http_client/integration_tests.rs — rcgen 0.14 renamed CertifiedKey.key_pair → signing_key (destructured as signing_key: key_pair to leave the rest of the test untouched) Cargo.lock resolved to hmac 0.13.0, pbkdf2 0.13.0, sha2 0.11.0, rand 0.10.1, rcgen 0.14.8. The old-generation digest 0.10 / sha2 0.10 / crypto-common 0.1 still appear as duplicates — that's expected and harmless; aes-gcm 0.10 and ed25519-dalek 2.2 carry their own internal copies and don't share types with your code. Verification - cargo check --workspace --all-targets --features full — clean - cargo clippy -p seq-runtime --features full --all-targets -- -D warnings — clean - crypto tests: 41 passed; TLS integration tests passed

navicore added 1 commit

2026-06-01 13:45:12 +00:00

● Done. All five dependency bumps are applied to your working tree and verified.

CI - Linux / CI - Linux x86_64 (pull_request) Successful in 4m5s

Details

3d9463c164

What changed

  Manifests:
  - Cargo.toml — sha2 0.10→0.11, hmac 0.12→0.13, rand 0.9→0.10, pbkdf2 0.12→0.13
  - crates/runtime/Cargo.toml — rcgen 0.13→0.14

  Code fixes for the breaking APIs:
  - crypto/hash.rs — new_from_slice moved from Mac to KeyInit (added the import, changed the call)
  - crypto/random.rs — rand 0.10 moved fill_bytes onto the Rng trait (use rand::{RngCore, rng} → use rand::{Rng,
  rng})
  - http_client/integration_tests.rs — rcgen 0.14 renamed CertifiedKey.key_pair → signing_key (destructured as
  signing_key: key_pair to leave the rest of the test untouched)

  Cargo.lock resolved to hmac 0.13.0, pbkdf2 0.13.0, sha2 0.11.0, rand 0.10.1, rcgen 0.14.8. The old-generation
  digest 0.10 / sha2 0.10 / crypto-common 0.1 still appear as duplicates — that's expected and harmless; aes-gcm
  0.10 and ed25519-dalek 2.2 carry their own internal copies and don't share types with your code.

  Verification

  - cargo check --workspace --all-targets --features full — clean
  - cargo clippy -p seq-runtime --features full --all-targets -- -D warnings — clean
  - crypto tests: 41 passed; TLS integration tests passed

navicore merged commit 962458c6e0 into main

2026-06-01 13:49:36 +00:00

navicore deleted branch crypto-update

2026-06-01 13:49:36 +00:00

navicore referenced this pull request from a commit

2026-06-01 13:49:37 +00:00

Merge pull request '● Done. All five dependency bumps are applied to your working tree and verified.' (#524) from crypto-update into main