sha3 breaking changes
Every breaking API change we have recorded in sha3 on crates.io: 3 breaking changes in 1 version. Below are its newest version, removals and renames first, each with its source.
Newest change May 15, 2026
On this page
0.12.0
- Removed
sha3::block_api
sha3::block_api was removed in sha3 0.12.0 crates.io - Removed
sha3::CollisionResistance
sha3::CollisionResistance was removed in sha3 0.12.0 crates.io - Removed
sha3::CustomizedInit
sha3::CustomizedInit was removed in sha3 0.12.0 crates.io
Check your code
These are the changes. To see which of them reach your code, scan a public repository, or have your coding agent call check_code with your manifest or lockfile over MCP. The API reads every change in every version, not only the newest. On Team and up, a fix pull request opens for the changes that reach a connected repository. Nothing merges or deploys.
Put your code on continuous management.
Scan a public repository now, or give your agent one line.
See how out of date your code is.
Tell your agent what changed since it was trained.
claude mcp add --transport http since https://api.since.dev/mcp