Skip to content

deps: bump sha2 from 0.10.9 to 0.11.0#77

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/sha2-0.11.0
Open

deps: bump sha2 from 0.10.9 to 0.11.0#77
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/sha2-0.11.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Apr 13, 2026

Copy link
Copy Markdown
Contributor

Bumps sha2 from 0.10.9 to 0.11.0.

Commits

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot @github

dependabot Bot commented on behalf of github Apr 13, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: dependencies, rust. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot dependabot Bot changed the title deps: Bump sha2 from 0.10.9 to 0.11.0 deps: bump sha2 from 0.10.9 to 0.11.0 Apr 22, 2026
@dependabot dependabot Bot force-pushed the dependabot/cargo/sha2-0.11.0 branch from 34ab0df to ee8d21c Compare April 22, 2026 17:47
Bumps [sha2](https://github.com/RustCrypto/hashes) from 0.10.9 to 0.11.0.
- [Commits](RustCrypto/hashes@sha2-v0.10.9...sha2-v0.11.0)

---
updated-dependencies:
- dependency-name: sha2
  dependency-version: 0.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot force-pushed the dependabot/cargo/sha2-0.11.0 branch from ee8d21c to f1e64d2 Compare April 27, 2026 16:15
@sionsmith

Copy link
Copy Markdown
Contributor

Reviewed locally. The direct sha2 0.11 bump compiles and the targeted evidence/signing/validation tests I ran passed (cargo test -p kafka-backup-core evidence --locked, cargo test -p kafka-backup-core validation --locked, cargo test -p kafka-backup-cli validation --locked). It does not reduce the current cargo audit findings by itself, and it touches hashing/signing paths, so I would hold it for a deliberate crypto/dependency refresh rather than merging it casually with unrelated work.

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.

1 participant