Skip to content

all: Drop arrayref by bumping blake3 and stable-hash - #6715

Open
incrypto32 wants to merge 1 commit into
masterfrom
incrypto32/blake3-drop-arrayref
Open

all: Drop arrayref by bumping blake3 and stable-hash#6715
incrypto32 wants to merge 1 commit into
masterfrom
incrypto32/blake3-drop-arrayref

Conversation

@incrypto32

Copy link
Copy Markdown
Member

Removes arrayref from the tree. Its crates.io account was compromised on 2026-08-20 (RUSTSEC-2026-0260). We were never exposed since the lockfile pinned the clean 0.3.7, but the account is still locked, so removing it takes future releases out of our path.

blake3 1.8.7 dropped arrayref and is the only release that has. Needed blake3 bumped on both stable-hash branches first:

stable-hash is now pinned by rev instead of branch. The manifests tracked branches while the lockfile held 2023 commits, so any re-resolution would have silently jumped forward across a blake3 major version on a crate that computes PoIs.

Lockfile: 938 → 932 packages. Removed arrayref 0.3.7, blake3 0.3.8, blake3 1.8.5, arrayvec 0.5.2, cfg-if 0.1.10, constant_time_eq 0.1.5, crypto-mac 0.8.0, uint 0.8.5. Added blake3 1.8.7, uint 0.10.1.

Known-value digest tests pass unchanged: online_vs_reference (hardcoded Legacy and Fast PoI hashes) and big_decimal_stable (hardcoded legacy digests). Note the uint bump touches fast/fld.rs, which is on the Fast path.

Closes #6714

blake3 1.8.7 drops arrayref, whose crates.io account was compromised
(RUSTSEC-2026-0260). stable-hash requires it on both branches now.

Pin stable-hash by rev rather than branch so re-resolution cannot
silently move it.
@incrypto32
incrypto32 requested a review from lutter August 21, 2026 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

graph-node uses blake3 versions that install a potentially compromised arrayref dependency

1 participant