docs(release): gate newer upstream clients on non-regression #108
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/release-newer-client-nonregression"
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?
Problem
#107 required newer upstream clients (newer patch release or default branch) to pass the public live gate. A newer client can also fail against the current production relay; blocking the candidate in that case keeps production on an older release with the same break and stalls the release line.
Change
Run the newer client against both the candidate and the current production relay and gate on non-regression: the candidate must not do worse than production. A failure shared with production is recorded as a known incompatibility in the release note and opens the next retarget.
Validation
Docs only;
git diff --checkclean.Risk
A known newer-client incompatibility can ship, but only when production already has it and it is disclosed.