You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Move all six EdgeZero crates to EdgeZero PR 275 in one change, following the spec in #1506. Every outbound request goes through EdgeZero's HttpClient, Fastly runs on EdgeZero's canonical lifecycle (send_request_with_registries_and_hooks), and EdgeZero follows redirects. Trusted Server's outbound layer (PlatformHttpClient, PlatformBackend, backend naming, the four adapter clients), its redirect loop, and its Fastly response delivery are deleted, with no compatibility layer.
main pins EdgeZero v0.0.11 today. Repinning to PR 275 head 8f82547b without code changes leaves 167 compile errors. Three runtime breaks also compile cleanly: inbound bodies arrive as streams, three of the four adapter clients reject streamed request bodies, and EdgeZero's response framing rejects Trailer.
The spec's commit sequence has 11 steps. Development pins 8f82547b. The merge pins the qualified candidate from #1508.
Done when
main pins the frozen PR 275 candidate that EdgeZero's qualification record names.
The spec's dependents inventory command prints nothing.
Every CI gate in AGENTS.md passes, along with the spec's new tests.
The Fastly response diff against the previous build shows only the Fastly differences the spec lists.
Activity
proxy.certificate_check#1556