Refresh session window for authenticated publication
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 4m38s
Foundation / server-image (push) Successful in 6m15s
Foundation / postgres-tools (push) Successful in 6m21s
Foundation / image (push) Successful in 7m42s

This commit is contained in:
dingo
2026-10-27 09:38:54 -04:00
parent d0e0e2cf87
commit d46de25bef
2 changed files with 10 additions and 9 deletions
@@ -12,7 +12,7 @@ spec:
env:
- {name: REGION_SESSION, value: "dev"}
- {name: REGION_SESSION_LISTEN, value: "0.0.0.0:7400"}
- {name: REGION_SESSION_WINDOW, value: "dev-20261027T131324-ed040353:1793121204"}
- {name: REGION_SESSION_WINDOW, value: "dev-20261027T133850-778f1d68:1793122730"}
- {name: REGION_M10_MAX_GRANT_LIFETIME, value: "14400"}
ports:
# QUIC (ADR-0090): UDP only; nothing listens on TCP 7400.
+9 -8
View File
@@ -10405,11 +10405,12 @@ reset a region, deploy, prune or operate on World0. Unrelated drafts and untrack
files remain untouched. The mandatory pre-push session-window refresh is desired
Git configuration only, not a claim of live reachability.
Publication limit for this gate: the validated feature commit was created locally.
Its required session window was refreshed immediately before the push attempt,
with a unique activation and absolute UTC expiry four hours ahead. The configured
remote rejected authentication ("Failed to authenticate user"); publication did
not succeed. No remote URL, stored credential or credential helper was changed,
and no repeated authentication attempts or deployment were made. Refresh Git
authentication before retrying publication, with a fresh session window included
in that retry as required by AGENTS.md.
Publication history: the initial push followed the required session-window
refresh but the remote rejected authentication ("Failed to authenticate user").
The maintainer subsequently supplied an external local credential file and
authorized a retry. An authenticated read-only remote check passed. The retry
uses per-command askpass credentials with the stored helper disabled for that
command, and another unique session activation expiring four hours ahead. No
credential values, credential file, remote URL change or credential-store change
are included in the repository; temporary helpers stay in ignored build output.
No deployment or live-reachability claim follows from publication.