Skip to content

feat(spec)!: standardize route hostnames - #199

Merged
vishr merged 1 commit into
mainfrom
fix/standardize-route-hostnames
Sep 20, 2026
Merged

vishr merged 1 commit into
mainfrom
fix/standardize-route-hostnames

Conversation

@vishr

@vishr vishr commented Sep 20, 2026

Copy link
Copy Markdown
Member

Summary

  • introduce the onebox.run/v2 project contract
  • replace domain and wildcard_suffix routing fields with routes[].hostname
  • accept exact hosts and literal leftmost wildcards such as *.example.com
  • preserve frozen v1 schema URLs and migrate v1 release snapshots only for rollback/recovery
  • update fixtures, generated schemas, docs, site examples, and CI smoke coverage

Breaking migration

  • domain + port becomes routes: [{hostname: host, port: port}]
  • wildcard_suffix: example.com becomes hostname: *.example.com
  • authored v1 projects are rejected by the v2 loader; immutable v1 release snapshots remain replayable

Verification

  • just ci
  • independent Astra review: no major+ findings
  • independent Cavecrew review: no findings
  • browser QA of every landing-page example toggle

Replace domain and wildcard_suffix with routes[].hostname in the onebox.run/v2 contract, retain immutable v1 schema URLs, and migrate v1 release snapshots only for lifecycle replay.

BREAKING CHANGE: onebox.run/v2 removes scalar domain routing and routes[].wildcard_suffix; declare exact and literal wildcard values through routes[].hostname.
@vishr
vishr merged commit e354fb1 into main Sep 20, 2026
5 checks passed
@vishr
vishr deleted the fix/standardize-route-hostnames branch September 20, 2026 16:43
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