Skip to content

chore(deps): bump the rust group with 2 updates - #73

Merged
zoeyrose merged 2 commits into
mainfrom
dependabot/cargo/rust-dce9df5c0f
Oct 17, 2026
Merged

zoeyrose merged 2 commits into
mainfrom
dependabot/cargo/rust-dce9df5c0f

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps the rust group with 2 updates: sha2 and zeroize.

Updates sha2 from 0.11.0 to 0.11.1

Commits

Updates zeroize from 1.9.0 to 1.9.1

Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the rust group with 2 updates: [sha2](https://github.com/RustCrypto/hashes) and [zeroize](https://github.com/RustCrypto/utils).


Updates `sha2` from 0.11.0 to 0.11.1
- [Commits](RustCrypto/hashes@sha2-v0.11.0...sha2-v0.11.1)

Updates `zeroize` from 1.9.0 to 1.9.1
- [Commits](RustCrypto/utils@zeroize-v1.9.0...zeroize-v1.9.1)

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

Signed-off-by: dependabot[bot] <support@github.com>
@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

Clears RUSTSEC-2026-0346 through RUSTSEC-2026-0349, which fail the
cargo-deny advisories check on every pull request against main.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016FyuSKkineBeVKbubYFsqd
@zoeyrose
zoeyrose merged commit bc9abcf into main Oct 17, 2026
10 checks passed
@zoeyrose
zoeyrose deleted the dependabot/cargo/rust-dce9df5c0f branch October 17, 2026 14:20
zoeyrose added a commit that referenced this pull request Oct 17, 2026
<!-- claude-projects-attribution: {"github_login":"zoeyrose"} -->
_Requested by **Zoey** · [project
thread](https://claude.ai/code/project/chan_01GqFGRfVxfKgHRxSgL4g4qr?thread=cmsg_01GqFGRfVxfKgHRxSgL4g4qr8QRmstGjD1db1c8HCp5KSi)_

## Summary

Before: when a RustSec advisory was published against a crate already in
`main`'s `Cargo.lock`, `cargo deny check` failed on every open pull
request. #72 (a GitHub Actions bump) and #73 went red on
RUSTSEC-2026-0346 through 0349 in `rustls` 0.23.45 even though neither
change caused them.

After: pull requests fail only on advisories they introduce. Advisories
already present on the base revision show up as warnings on the PR.
Pushes to `main`, local `tools/validate.sh` runs and the
released-dependency candidate stay strict, and a new daily `Dependency
advisories` workflow fails on `main` so a new advisory is visible in one
place instead of on every PR.

How: `tools/check-advisories.sh` runs `cargo deny check advisories` with
JSON output. When `ADVISORY_BASE_REVISION` is set, which `validate.yml`
does from the pull request's base SHA, it runs the same check in a
temporary worktree at that revision and fails only on the advisory IDs
the base does not have. `validate.sh` keeps running bans, licenses and
sources directly.

The `rustls` fix itself is on #72 and #73.

## Provenance and assets

- [x] Design inputs, authorship, reuse method, fixtures, and generated
inputs are recorded. (CI tooling only, newly authored)
- [x] No GPL source/test/fixture or unallowlisted asset was used.
- [x] Dependency/native/asset policy and notices are current. (no
dependency changes)

## Validation

- [ ] `tools/validate.sh` (CI)
- [x] Ran `tools/check-advisories.sh` locally with pinned cargo-deny
0.20.2 in each mode: strict on current `main` exits 1; with base =
`main` it exits 0 and warns about the four `rustls` advisories; with
`rustls` 0.23.46 it prints `advisories ok`; with base = a fixed lockfile
and head = `main`'s lockfile it exits 1 and lists the four as
introduced.
- [x] Bounds, authority, privacy, device loss, cancellation, and
recovery were reviewed. (no runtime change; temporary worktree removed
on exit)

---
_Generated by [Claude
Code](https://claude.ai/code/session_016FyuSKkineBeVKbubYFsqd)_

---------

Co-authored-by: Claude <noreply@anthropic.com>
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 rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants