fix(deps): upgrade SHA-256 chain to patched block-buffer0.12.1 #46
No reviewers
Labels
No labels
waiting-on-julian
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jlxq0/jmap-mcp!46
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/block-buffer-advisory-20261029"
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?
OSV blocks the current
block-buffer0.10.4 dependency for GHSA-qwgh-2vcv-g2f7 even though RustSec audit passes. Upgrade the sole reverse chain to released sha2 0.11.1 → digest0.11.3 → patched block-buffer0.12.1, retaining pinned Rust1.93.0 and all advisory gates. Only required crypto dependencies change; old generic-array/version_check and cpufeatures0.2 are removed. No application runtime logic, credentials, profiles or deployment changes.Validation: pinned fmt/clippy(all targets/features, locked) and244tests pass. Fixed token-hash vectors (including Unicode and block/padding boundaries) pass before and after upgrade. Cargo audit0vulnerabilities (existing allowed chacha20 yankedwarning), deny bans/licenses/sources pass. Checksum-pinned OSV2.5.1 reports No issues found. Fresh independent Claude Code print review (claude-opus-5-5), separate read-only context, APPROVE exact
54eb8b2c2f52dd4848bd84daa1596596f933f613; all ACs pass, no blocking security/data-loss issue. Forgejo CI156 all success: cargo (including OSV), tag-ancestry and Docker build/scan. Reviewer did not run tests; cited log provenance plus exact-headCI provides execution evidence. This prerequisite is separate from draft safety PR45; no release/tag/deploy performed.