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
docs(changelog): drop 'on master' git lingo from auth-config migration note
Anshu Garg7c1ea128275c
diff --git a/docs/content/changelog/04-22-26-composio-managed-credentials-masking.mdx b/docs/content/changelog/04-22-26-composio-managed-credentials-masking.mdxindex b3a7c386d..a9e2f5d63 100644--- a/docs/content/changelog/04-22-26-composio-managed-credentials-masking.mdx+++ b/docs/content/changelog/04-22-26-composio-managed-credentials-masking.mdx@@ -73,7 +73,7 @@ If you were reading Composio-managed access or refresh tokens from these respons- **Composio-managed auth configs** — every credential field is redacted.- **Customer-owned auth configs** — public OAuth identifiers (`client_id`, `consumer_key`) still pass through so you can debug OAuth flows. Every other credential field is obfuscated.-If your code reads a secret — for example `client_secret` or `developer_token` — out of these responses, you will need to keep that value alongside the code that created the auth config (typically in your own secret manager at upload time). These fields were returned in plaintext under some paths on master and are now obfuscated.+If your code reads a secret — for example `client_secret` or `developer_token` — out of these responses, you will need to keep that value alongside the code that created the auth config (typically in your own secret manager at upload time). These fields were previously returned in plaintext on some code paths and are now obfuscated.### Why this change