Record security advisory changes in the transparency log#1780
Merged
Conversation
bf9b5f2 to
60dc4e5
Compare
Seldaek
reviewed
Jul 8, 2026
Seldaek
reviewed
Jul 8, 2026
3fc79ab to
46dda20
Compare
Add transparency log entries for the security advisory lifecycle: created, updated, withdrawn and reinstated. The update worker emits the records after resolving each run, classifying by the net state change so a transient withdraw/reinstate within one run collapses into a single edit. Advisory changes are attributed to the automation actor. Adds the SecurityAdvisory* audit record types (advisory category), AuditRecord factories, a shared display + template, factory wiring and translations.
46dda20 to
89feb96
Compare
89feb96 to
8d89e8c
Compare
Member
|
Thanks |
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.
Add transparency log entries for the security advisory lifecycle: created, updated, withdrawn and reinstated. The update worker emits the records after resolving each run, classifying by the net state change so a transient withdraw/reinstate within one run collapses into a single edit. Advisory changes are attributed to the automation actor.