Repository navigation
Assigned RUSTSEC-2026-0437 to azure_security_keyvault_certificates, RUSTSEC-2026-0438 to azure_security_keyvault_secrets, RUSTSEC-2026-0439 to azure_security_keyvault_keys, RUSTSEC-2026-0440 to astral-tokio-tar, RUSTSEC-2026-0441 to pin-utils and 1 more - #3497
Merged
Merged
Conversation
github-actions
Bot
changed the title
github-actions
Bot
force-pushed
the
assign-ids
branch
2 times, most recently
from
November 3, 2026 20:35
a0cce10 to
d07ded7
Compare
github-actions
Bot
changed the title
djc
approved these changes
Nov 3, 2026
jdx
added a commit
to jdx/mise
that referenced
this pull request
Nov 3, 2026
…rgo-deny (#15352) `cargo deny check` now fails `lint` on every branch. Two crates were marked unmaintained today, and both come in through rattler: - `astral-tokio-tar`, via `rattler_package_streaming`, which the conda backend uses to unpack conda packages - `pin-utils`, via `wasmtimer` in `rattler_repodata_gateway` Neither advisory reports a vulnerability, and no upgrade drops either crate until rattler does. This adds ignore entries with those reasons, like the other transitive advisories in `deny.toml`. Both advisories are still unnumbered (`RUSTSEC-0000-0000`). [rustsec/advisory-db#3497](rustsec/advisory-db#3497) assigns them RUSTSEC-2026-0439 and RUSTSEC-2026-0437, and this ignores those IDs too. Until then, the placeholder entry is what keeps `lint` green. It ignores every unnumbered advisory, so it should be removed once the IDs are published. ## Test plan - With a fresh advisory database, `cargo deny check advisories` fails on main with cargo-deny 0.19.4 (CI's version) and passes on this branch. *AI-assisted — Tool: Claude Code; model: anthropic/claude-opus-5-5; version: 2.1.309.* 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Config-only change to cargo-deny ignores; no application logic or dependency upgrades. > > **Overview** > **Restores green `cargo deny check advisories` lint** after two new *unmaintained* (not vulnerable) RustSec entries for transitive rattler dependencies: `astral-tokio-tar` (conda package unpacking via `rattler_package_streaming`) and `pin-utils` (via `wasmtimer` in `rattler_repodata_gateway`). > > Adds documented ignore entries in `deny.toml` for the upcoming IDs **RUSTSEC-2026-0439** and **RUSTSEC-2026-0437**, plus a **temporary** `RUSTSEC-0000-0000` ignore so CI passes while those advisories are still unnumbered in the advisory DB—intended to be removed once [rustsec/advisory-db#3497](rustsec/advisory-db#3497) lands. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 60965ff. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY --> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…USTSEC-2026-0438 to azure_security_keyvault_secrets, RUSTSEC-2026-0439 to azure_security_keyvault_keys, RUSTSEC-2026-0440 to astral-tokio-tar, RUSTSEC-2026-0441 to pin-utils and 1 more
github-actions
Bot
changed the title
github-actions
Bot
force-pushed
the
assign-ids
branch
from
November 5, 2026 08:35
d07ded7 to
144cb05
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated changes by create-pull-request GitHub action