Skip to content

Add RUSTSEC-2026-0173 exception#882

Merged
RobertZ2011 merged 1 commit into
OpenDevicePartnership:mainfrom
RobertZ2011:proc-macro-error2-exception
Jun 8, 2026
Merged

Add RUSTSEC-2026-0173 exception#882
RobertZ2011 merged 1 commit into
OpenDevicePartnership:mainfrom
RobertZ2011:proc-macro-error2-exception

Conversation

@RobertZ2011

Copy link
Copy Markdown
Contributor

No description provided.

@RobertZ2011 RobertZ2011 self-assigned this Jun 8, 2026
@RobertZ2011 RobertZ2011 force-pushed the proc-macro-error2-exception branch from ef9aa7a to 4af64e1 Compare June 8, 2026 17:11
@RobertZ2011 RobertZ2011 marked this pull request as ready for review June 8, 2026 18:22
@RobertZ2011 RobertZ2011 requested a review from a team as a code owner June 8, 2026 18:22

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the workspace cargo-deny configuration to ignore the newly reported RustSec advisory RUSTSEC-2026-0173. The intent is to keep advisory checks green while the dependency tree still pulls in an unmaintained crate with no safe upgrade path available. This fits the repo’s existing pattern of documenting and temporarily ignoring advisories that are not immediately actionable.

Changes:

  • Add RUSTSEC-2026-0173 to [advisories].ignore in deny.toml with a brief rationale.

Review Guide

  1. Advisory ignore list update
    • Confirm the new entry is placed under [advisories].ignore alongside other ignored RustSec IDs and uses the same table format ({ id = "...", reason = "..." }).
    • Validate the stated rationale aligns with how the repo has handled similar “unmaintained / no safe upgrade” advisories (e.g., the existing proc-macro-error ignore entry nearby).

Potential issues

No issues identified.

@RobertZ2011 RobertZ2011 merged commit 576034c into OpenDevicePartnership:main Jun 8, 2026
16 checks passed
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.

4 participants