Skip to content

chore(deps): bump sha2 from 0.11.0 to 0.11.1 - #57

Merged
zoeyrose merged 1 commit into
mainfrom
dependabot/cargo/sha2-0.11.1
Oct 19, 2026
Merged

zoeyrose merged 1 commit into
mainfrom
dependabot/cargo/sha2-0.11.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 17, 2026 •

Copy link
Copy Markdown
Contributor

Bumps sha2 from 0.11.0 to 0.11.1.

Commits

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Oct 17, 2026
@github-actions

Copy link
Copy Markdown

Dependency Review

✅ No vulnerabilities or license issues found.

Scanned Files

  • Cargo.lock

@zoeyrose
zoeyrose marked this pull request as draft October 18, 2026 07:43
@zoeyrose

Copy link
Copy Markdown
Member

Back to draft until the merge-readiness gate passes: Protocol validation fails and the branch is behind main

@zoeyrose

Copy link
Copy Markdown
Member

Kept as a draft. Protocol validation fails in tools/crate_prepare.py check-version with package content changed without reviewed version bump. Main is green at a834a16, so the failure comes from this bump.

Cause: the version gate counts any Cargo.lock diff as a change to the published atrinik-protocol package. Here the only sha2 user is tools/rendezvous-conformance (publish = false, dev-dependency). The published atrinik-protocol-0.2.0.crate ships a pruned Cargo.lock that has no sha2 or hmac at all, so the packaged content does not change. The gate's path check is a false positive here, and rebasing alone will not fix it.

Needs an owner decision. Either:

  1. Narrow the gate so that a Cargo.lock-only diff counts only when the published crate's locked dependency closure changes. Release-time preparation would still compare the real packaged content against the owning archive.
  2. Or bump atrinik-protocol to 0.2.1. That automatically publishes a content-identical crate to crates.io, which can't be undone.

After either change lands on main, @dependabot rebase should be enough here.

@zoeyrose

Copy link
Copy Markdown
Member

@dependabot rebase

Bumps [sha2](https://github.com/RustCrypto/hashes) from 0.11.0 to 0.11.1.
- [Commits](RustCrypto/hashes@sha2-v0.11.0...sha2-v0.11.1)

---
updated-dependencies:
- dependency-name: sha2
  dependency-version: 0.11.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/cargo/sha2-0.11.1 branch from 1461b5d to f21aa7f Compare October 18, 2026 16:35
@zoeyrose
zoeyrose marked this pull request as ready for review October 18, 2026 16:38
@zoeyrose zoeyrose self-assigned this Oct 18, 2026
@zoeyrose
zoeyrose merged commit d298b1b into main Oct 19, 2026
5 checks passed
@zoeyrose
zoeyrose deleted the dependabot/cargo/sha2-0.11.1 branch October 19, 2026 05:13
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 2.21.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file released rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant