Repository navigation
Conversation
Rotate only the data product canonical approval pair, retaining the legacy deployed signer and the prior reviewed publisher. Regenerate its matcher and exercise exact acceptance, retired and malformed identity refusal, and unrelated consumer isolation. Part of #5377.
Publisher review and validation at
Correctness and simplification self-review found no remaining issue in the three-file diff. This remains a draft pending hosted CI and substantive review. After protected deployment, run the unchanged complete observation refresh and verify input stability; #5377 remains open until that evidence is collected. |
CI diagnosis at Use the maintained authorization approval generator to record only that reviewed source change, verify the complete ledger diff remains limited to it, and rerun the authorization regressions plus required CI. The current three-file diff remains incomplete until those checks pass. Evidence: Validate Complete Go Regressions and Validate Production Authorization. The separate observation-refresh PR #5378 changes publication receipts and does not change this approval ledger, so its merge alone will not repair this failure. This is a diagnosis of the current draft; no branch or approval record was changed. |
Closing this draft as superseded. KHoist #500 restored the already approved publisher at I re-read this draft at |
Why
The publication refresh stops when the data product selects its current publisher, delaying verified source updates for other applications.
What
Approves the reviewed publisher for the data product while preserving the running publication and keeping every other application’s approval unchanged. The complete observation refresh follows protected deployment.
Part of #5377