Repository navigation
fix(publishing): validate application-owned release signers - #296
Conversation
Validate the strict direct publisher frame and its exact own-release matcher before the starter caller switch. Preserve the shared publisher paths and existing controls. Part of #289.
Validation at
User-path scope: I exercised the actual validator with the direct-publisher fixture and decoded Platform matcher, including rejected shared-only, explicit shared-revision, environment-override and branch-publication cases. This proves offline compatibility; it does not prove a real release, admission or reconciliation. The existing publisher remains selected, and #289 remains open. Hosted CI and an exact-head external review are still required before promotion. |
@coderabbitai review |
Action performed
|
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
Readiness at
Promoting this preparation for the normal protected merge path. |
Why
The template currently rejects the application-owned release signer that its publisher switch needs, keeping deployment updates waiting.
What
Validate that signer against the platform’s exact release rule while preserving the existing publication safeguards. The actual publisher switch and released application verification remain separate work.
Part of #289