Repository navigation
Conversation
Explain independent subscriptions for active and reviewed policy violation message changes, including the configuration flow, structured fields, filter and template examples, and retained review decisions. Keep the feature marked unreleased and regenerate its notification schema from the implementation so readers can prepare without assuming availability in existing releases. Signed-off-by: WenFeng Gao <bd007xf@gmail.com>
This was referenced Nov 7, 2026
This branch has not been deployed
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.
Description
Document the proposed component policy violation update notifications, including the separate
opt-in group for approved or suppressed violations. Add a task-oriented guide and navigation,
and extend the group, filter, template, and policy expression references.
Addressed Issue
Companion documentation for DependencyTrack/dependency-track#7908, addressing
DependencyTrack/dependency-track#7649. The corresponding API server change must land before
these groups become available. The new documentation marks the feature as unreleased.
Frontend companion: DependencyTrack/frontend#2074.
Additional Details
The guide uses the frontend's alert workflow and a stable message expression containing all
matching KEV identifiers. The reference explains creation versus message changes, ordinary
versus reviewed subscriptions, preserved decisions, no historical replay, optional field presence,
and snake_case versus JSON/Pebble field names. Filter examples explicitly check captured values.
Document message-based limits, removals and wording changes, existing retry semantics,
notification-ID deduplication, permanent-failure diagnostics, and custom-template/consumer support.
Regenerate the notification schema and downloadable Protobuf file through the repository's
make generate-proto-docstarget from the API server implementation. No generated file wasedited by hand, and the policy schema has no unrelated changes.
Validation:
make buildpassed on Python 3.14.7 with the locked dependencies.make lintpassed: Markdown checks covered 120 files with no errors, YAML andPython checks passed, and prose checks covered 119 files with no errors. The 392 existing
prose warnings exactly match an isolated copy of the unchanged main branch using the same
styles. No added line or new guide has a prose warning; lint rules are unchanged.
variables enabled. All six ordinary/reviewed, null-message, and optional-boolean cases passed.
Commands:
The API server source is a sibling checkout containing the implementation proposed in
DependencyTrack/dependency-track#7908. The source schema matches the downloadable schema byte
for byte. The commit includes the contributor's DCO sign-off.