Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
TypeScript agentic-aiagentsaiai-agentsaiagentsdeveloper-toolsfunction-callinggpt-4javascriptjsllmllmopsmcppythonremote-mcp-serverssetypescript
ci(docs): give the docs data sync its own production API key
daksh0454f423a75a
diff --git a/.github/workflows/docs-update-data.yml b/.github/workflows/docs-update-data.ymlindex bee5e1666..1a93240d3 100644--- a/.github/workflows/docs-update-data.yml+++ b/.github/workflows/docs-update-data.yml@@ -21,7 +21,13 @@ jobs:pull-requests: writeissues: writeenv:- COMPOSIO_API_KEY: ${{ secrets.COMPOSIO_API_KEY }}+ # Deliberately NOT secrets.COMPOSIO_API_KEY. That secret is shared with+ # ts.test-e2e, py.test, py.check and ts.examples-nightly, all of which run+ # against staging — it is a staging-scoped credential. This job is the only+ # consumer that must reach production (scripts/production-api.mjs rejects any+ # non-production base URL), so it needs its own production key. Pointing the+ # shared secret at production instead would break the staging suites.+ COMPOSIO_API_KEY: ${{ secrets.COMPOSIO_DOCS_API_KEY }}steps:- name: Generate GitHub App token@@ -56,7 +62,7 @@ jobs:# generators default to the production API (docs/scripts/production-api.mjs).# Previously this step pointed the fetch at STAGING, which published staging# hosts (and unreleased content) into the committed docs.- # NOTE: requires COMPOSIO_API_KEY to have PRODUCTION read access.+ # NOTE: requires COMPOSIO_DOCS_API_KEY to have PRODUCTION read access.- name: Cache bun dependenciesuses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6.1.0@@ -171,8 +177,9 @@ jobs:toolkits added to production after the last successful run have no page andreturn 404. The site stays up, which is why this fails silently.- **First thing to check:** the \`COMPOSIO_API_KEY\` secret must have **production**- read access against \`backend.composio.dev\`. A staging-only key returns 401 here.+ **First thing to check:** the \`COMPOSIO_DOCS_API_KEY\` secret must have+ **production** read access against \`backend.composio.dev\`. Note this job does+ not use the shared \`COMPOSIO_API_KEY\`, which is staging-scoped.This issue is filed once and left open until the cause is fixed; it will not bere-filed on every run."