docs(release): scope live gate to the deployed runtime #107

Merged

ada merged 1 commit from docs/release-process-direct-scope into master 2026-10-08 15:02:03 +00:00

Conversation 0 Commits 1 Files changed 3 +70 -25

ada commented 2026-10-08 14:54:55 +00:00

Collaborator

• Copy link
• Copy Markdown

Problem

The release playbook required a public relay-to-relay (Axis B, IVNP overlay) live gate for every release, but the reference deployment runs with overlay disabled. The gate needed a multi-relay mesh that is not available, so v2.5.1 and v2.6.0 stalled while the direct path that production actually serves was under-tested (a same-protocol client break was found outside the gate).

Change

• §1: verified scope follows the deployed runtime. Axis A is always a public live gate; Axis B is required only when overlay is deployed, upstream makes it default/mandatory, or direct transport becomes secondary. While out of scope: keep deterministic fixtures in PR CI, prove direct fallback for overlay-requesting clients, do not advertise overlay, state it in the release note.
• §6 step 5: concrete Axis A public gate (interop-window clients including newer upstream patch/default-branch clients, both reverse carriers, tenant TLS, version surface).
• §6: bounded live deploy procedure (preflight, quiesce, swap with rollback deadline, verify, sequential client restore) replacing the maintenance-window approval model.
• §6: operator autonomy; escalation only for scope/security-boundary changes or failed rollback.
• §6: repository hygiene rule: no credentials, private hosts/addresses, inventories, or run evidence in the public tree.
• Support matrix: overlay ships but is not live-verified in a public deployment.
• scripts/go-client-http-smoke.sh: require GO_REPO instead of defaulting to a host-specific path.

Validation

Docs plus one shell default; bash -n passes; diff scanned for private hostnames, addresses, and paths.

Risk

Overlay interoperability is no longer claimed for overlay-disabled deployments; operators enabling IVNP_CONFIG must run the conditional gate.

## Problem The release playbook required a public relay-to-relay (Axis B, IVNP overlay) live gate for every release, but the reference deployment runs with overlay disabled. The gate needed a multi-relay mesh that is not available, so v2.5.1 and v2.6.0 stalled while the direct path that production actually serves was under-tested (a same-protocol client break was found outside the gate). ## Change - §1: verified scope follows the deployed runtime. Axis A is always a public live gate; Axis B is required only when overlay is deployed, upstream makes it default/mandatory, or direct transport becomes secondary. While out of scope: keep deterministic fixtures in PR CI, prove direct fallback for overlay-requesting clients, do not advertise overlay, state it in the release note. - §6 step 5: concrete Axis A public gate (interop-window clients including newer upstream patch/default-branch clients, both reverse carriers, tenant TLS, version surface). - §6: bounded live deploy procedure (preflight, quiesce, swap with rollback deadline, verify, sequential client restore) replacing the maintenance-window approval model. - §6: operator autonomy; escalation only for scope/security-boundary changes or failed rollback. - §6: repository hygiene rule: no credentials, private hosts/addresses, inventories, or run evidence in the public tree. - Support matrix: overlay ships but is not live-verified in a public deployment. - `scripts/go-client-http-smoke.sh`: require `GO_REPO` instead of defaulting to a host-specific path. ## Validation Docs plus one shell default; `bash -n` passes; diff scanned for private hostnames, addresses, and paths. ## Risk Overlay interoperability is no longer claimed for overlay-disabled deployments; operators enabling `IVNP_CONFIG` must run the conditional gate.

ada added 1 commit 2026-10-08 14:54:55 +00:00

docs(release): scope live gate to the deployed runtime ... 4fc7d8c304

Make Axis A the always-required public live gate and Axis B a conditional gate that applies only when overlay is deployed. Replace the maintenance-window approval model with a bounded live deploy procedure, define operator autonomy and the narrow escalation cases, and add a repository hygiene rule that keeps operational data out of the public tree. Mark overlay as not live-verified in the support matrix and stop defaulting a smoke script to a host-specific path.

ada merged commit e12afcd1fb into master 2026-10-08 15:02:03 +00:00

ada deleted branch docs/release-process-direct-scope 2026-10-08 15:02:03 +00:00

ada referenced this pull request from a commit 2026-10-08 15:02:04 +00:00

docs(release): scope live gate to the deployed runtime (#107)

ada referenced this pull request 2026-10-08 15:03:37 +00:00

docs(release): gate newer upstream clients on non-regression #108

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

gofix/portal-tunnel-rs!107

No description provided.