Repository navigation
Stop reading the dashboard's tag in the security-dash bridge - #1902
Merged
Merged
Conversation
apache/security-dash#62 reverted apache#58: the tag is the ASF Security team's internal name for a case, may change or disappear, and is not part of the reports API. Integrations identify a case by the Message-ID of the thread's first message. The bridge no longer reads or emits `tag`. Standing labels are still skipped by their `glasswing` / `non-fwd` states; the catch-all labels (`aaa-*`, `zzz-*`) cannot be told apart, so every untriaged case with no tracker issue stays `review`, never `import`. Generated-by: Claude Opus 5
potiuk
enabled auto-merge (squash)
October 29, 2026 22:38
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.
Summary
tagfield from the reports API (#58): the tag is the ASF Security team's internal name for a case, may change or disappear, and integrations should identify a case by theMessage-IDof the thread's first message.tools/asf-security-dashno longer reads or emitstag. Cases were already keyed byMessage-ID, so pairing with tracker issues is unchanged.glasswing/non-fwdstates. The catch-all labels (aaa-support,zzz-admin, …) are listed as untriaged cases and the API does not mark them, so an untriaged case with no tracker issue is alwaysreview(a human checks the thread), neverimport; that was already the behaviour whenever the API omitted the tag.specs/adapters.mdfollow; themagpie-security-toolsplugin copy is regenerated bycheck-family-plugins.Type of change
.claude/skills/<name>/) — eval fixtures updated belowtools/<system>/*.md)tools/*/withpyproject.toml)docs/,README.md,CONTRIBUTING.md)projects/_template/)prek, workflows, validators)Test plan
uv run pytestintools/asf-security-dash(68 passed), including a case where the API still returns atag: it is ignored and the case staysreview.prek runon the changed files passes."tag": nullfrom the case object; the expected proposal is unchanged.Linked issues
Follows apache/security-dash#62; amends #1780.
Generative AI tooling was used: Claude Code (Opus 5).
🤖 Generated with Claude Code