Skip to content

fix: generate stable hostnames on the managed project domain - #23

Merged
uartnet merged 1 commit into
mainfrom
codex/regional-project-stable-hostname
Nov 6, 2026
Merged

uartnet merged 1 commit into
mainfrom
codex/regional-project-stable-hostname

Conversation

@uartnet

@uartnet uartnet commented Nov 6, 2026

Copy link
Copy Markdown
Member

Use the managed project's public domain when generating a stable published hostname. A project connected to an explicit region must still connect to the authorized regional endpoint. A region mismatch continues to fail. Explicit hostnames and direct engine connections retain their existing behavior.

The previous wheel generated a hostname under the regional engine domain and the managed service rejected publication. The corrected source successfully published and served HTTP requests in staging.

Validation included 187 local tests, lint and type checking, distribution builds, and six live staging tests covering certificate authentication and the network integration suite. The temporary credentials and tunnels were removed after testing.

@uartnet
uartnet merged commit b331e9a into main Nov 6, 2026
13 checks passed
@uartnet
uartnet deleted the codex/regional-project-stable-hostname branch November 6, 2026 13:25
@uartnet uartnet mentioned this pull request Nov 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant