@devries-cameron20 / composio-1 / commits / 0454f423a
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

ci(docs): give the docs data sync its own production API key

`secrets.COMPOSIO_API_KEY` is shared with ts.test-e2e, py.test, py.check and ts.examples-nightly. Those pin COMPOSIO_BASE_URL to staging, and the nightly examples run is currently green against staging with this key — so the secret is a live staging credential, not an expired one. #3770 moved this job to production and added a guard rejecting any non-production base URL, but no production credential was provisioned. The staging key has returned 401 against backend.composio.dev on every run since, silently freezing the committed toolkit catalog. Repointing the shared secret at production would fix docs and break the staging suites, and py.check sets no base URL at all — a production key there would aim type-inference tests at production. So take a separate secret instead. Requires COMPOSIO_DOCS_API_KEY to be set with production read access. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

daksh committed Jul 24, 2026 at 18:41 UTC 0454f423a75a3c803a6befc656d9d37e531e7568
1 file changed +11 -4
.github/workflows/docs-update-data.yml
+11 -4
@@ -21,7 +21,13 @@ jobs:
21 pull-requests: write
22 issues: write
23 env:
24 - COMPOSIO_API_KEY: ${{ secrets.COMPOSIO_API_KEY }}
24 + # Deliberately NOT secrets.COMPOSIO_API_KEY. That secret is shared with
25 + # ts.test-e2e, py.test, py.check and ts.examples-nightly, all of which run
26 + # against staging — it is a staging-scoped credential. This job is the only
27 + # consumer that must reach production (scripts/production-api.mjs rejects any
28 + # non-production base URL), so it needs its own production key. Pointing the
29 + # shared secret at production instead would break the staging suites.
30 + COMPOSIO_API_KEY: ${{ secrets.COMPOSIO_DOCS_API_KEY }}
31
32 steps:
33 - name: Generate GitHub App token
@@ -56,7 +62,7 @@ jobs:
62 # generators default to the production API (docs/scripts/production-api.mjs).
63 # Previously this step pointed the fetch at STAGING, which published staging
64 # hosts (and unreleased content) into the committed docs.
59 - # NOTE: requires COMPOSIO_API_KEY to have PRODUCTION read access.
65 + # NOTE: requires COMPOSIO_DOCS_API_KEY to have PRODUCTION read access.
66
67 - name: Cache bun dependencies
68 uses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6.1.0
@@ -171,8 +177,9 @@ jobs:
177 toolkits added to production after the last successful run have no page and
178 return 404. The site stays up, which is why this fails silently.
179
174 - **First thing to check:** the \`COMPOSIO_API_KEY\` secret must have **production**
175 - read access against \`backend.composio.dev\`. A staging-only key returns 401 here.
180 + **First thing to check:** the \`COMPOSIO_DOCS_API_KEY\` secret must have
181 + **production** read access against \`backend.composio.dev\`. Note this job does
182 + not use the shared \`COMPOSIO_API_KEY\`, which is staging-scoped.
183
184 This issue is filed once and left open until the cause is fixed; it will not be
185 re-filed on every run."