@devries-cameron20 / composio-1 / commits / 7c1ea1282
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.

docs(changelog): drop 'on master' git lingo from auth-config migration note

The prior commit renamed the file but missed staging the wording fix. Replaces "returned in plaintext under some paths on master" with "previously returned in plaintext on some code paths" — same meaning, no internal default-branch name leaking into a customer-facing doc. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Anshu Garg committed Apr 22, 2026 at 12:19 UTC 7c1ea128275c983f9014b41a1a176cd24de441c3
1 file changed +1 -1
docs/content/changelog/04-22-26-composio-managed-credentials-masking.mdx
+1 -1
@@ -73,7 +73,7 @@ If you were reading Composio-managed access or refresh tokens from these respons
73 - **Composio-managed auth configs** — every credential field is redacted.
74 - **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.
75
76 -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.
76 +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.
77
78 ### Why this change
79