From f2e7fce8cdb997e26872e6186ab0134ee7bb5e60 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Mon, 27 Jul 2026 06:06:41 -0300 Subject: [PATCH] docs: fix stale API proxy filename in deployment runbook The runbook's 'API proxy not working' step referenced `functions/api/[[path]].ts`, but that catch-all was replaced by `functions/api/_middleware.ts` in #141 (fada676). An operator following the runbook would look for a file that no longer exists. Point the step at the current middleware entrypoint. Co-Authored-By: Claude Opus 4.8 --- docs/deployment-runbook.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/deployment-runbook.md b/docs/deployment-runbook.md index 5bf50300..c1b46203 100644 --- a/docs/deployment-runbook.md +++ b/docs/deployment-runbook.md @@ -124,7 +124,7 @@ The Content Security Policy is defined in `public/_headers`. If a new dependency ### API proxy not working -1. Verify `functions/api/[[path]].ts` is included in the deployment +1. Verify `functions/api/_middleware.ts` is included in the deployment 2. Check `_routes.json` includes `/api` and `/api/*` 3. Test: `curl -i https:///api/info` should return 400 4. Test: `curl -i -H "x-target-url: " https:///api/info` should return 200