Repository navigation
Make major release decisions maintainer-owned and explicit - #396
Conversation
|
|
Security/source review: PASS for exact The one-paragraph change is a coherent clarification of the existing maintainer-owned release model. It replaces the ambiguous blanket phrase "human decision" with a concrete major-release record: proposed versions, migration/rollback impact, required checks and conformance, plus the responsible maintainer's decision. It explicitly preserves any approval reserved for the particular release, so it does not authorize credentials, spending, reserved administrative actions, or a release that lacks its issue-specific decision. No workflow, policy parser, runtime, publication permission, or protected gate changes. This source verdict does not itself make a Chart 2.0.0 decision; the responsible maintainer must record that concrete decision on the existing major-release issue after this guide successor is accepted. Normal checks and merge/main verification remain required. |
|
Delivered normally as All nine PR checks passed before merge. All three actual-main workflows passed: repository controls, Sonar and main analysis. Remote topic absence is verified. Only the major-release decision paragraph changed. Release-specific reserved approvals and all technical/publication gates remain. General's separate concrete Chart 2.0.0 decision is recorded on Server #1014; this guide merge does not itself claim chart publication or consumer acceptance. |
Major releases need an explicit decision by the responsible release maintainer in the owning issue. The record must cover proposed versions, migration and rollback impact, required checks and conformance. This replaces the guide's blanket human decision requirement while retaining every specifically reserved approval.
Validation:
git diff --check. The normal repository checks remain required. No runtime, policy code, workflow, release artifact or publication gate changes.