Keep retained package approvals out of routine warning logs #505
No reviewers
Labels
No labels
code-review
correctness
dos
performance
security
severity/high
severity/low
severity/medium
tech-debt
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
h-dv/code-index!505
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/production-followups-044"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Automatic plugin upgrades retain earlier approvals. Startup currently logs each superseded digest as a warning, with a lengthy witness, although the selected digest is healthy and is the only one executed. Move that expected condition to debug logging and keep all structured refusal/approval diagnostics intact.
Also record the completed #119 producer-identity mutation check beside its existing regression test. The dispatcher was already shipped; #119 is closed after the database identity assertion failed under the temporary attribution collapse and all eight tests passed after restoration.
Validation: duplicate_package_id 15/15; embedded_region_producer 8/8; csharp_extension_safety 5/5; git diff --check. No resolver, approval-selection, storage or activation behavior changes. #313 and #410 remain open; no experimental resolver code is included.