@devries-cameron20 / composio Mirror · read-only / commits / 27972ef2d
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.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 22, 18:15 UTC

chore: update dates in the changelog

Composio committed Nov 13, 2025 at 18:06 UTC 27972ef2d37c67e80b5c1f15355050e95ebb84e4
1 file changed +3 -3
fern/pages/src/changelog/11-13-25.md
+3 -3
@@ -4,7 +4,7 @@ We're strengthening the security of Model Context Protocol (MCP) URLs by making
4
5 ## What's Changing?
6
7 -Starting today, **all new Composio projects** must include the `x-api-key` header when making requests to MCP URLs. This header authenticates your application and ensures secure communication with the Composio platform.
7 +Starting **December 15th, 2025**, **all new Composio projects** must include the `x-api-key` header when making requests to MCP URLs. This header authenticates your application and ensures secure communication with the Composio platform.
8
9 ## Why This Matters
10
@@ -14,9 +14,9 @@ This change provides:
14
15 ## Impact on Existing Projects
16
17 -**For existing projects**: We value backward compatibility and understand the need for a smooth transition. Your existing MCP URLs will continue to work without the `x-api-key` header until **March 31st, 2026**.
17 +**For existing projects**: We value backward compatibility and understand the need for a smooth transition. Your existing MCP URLs will continue to work without the `x-api-key` header until **April 15th, 2026**.
18
19 -**Important**: After March 31st, 2026, all MCP URL requests without the `x-api-key` header will be rejected. Please ensure you update your applications before this date to avoid service disruption.
19 +**Important**: After April 15th, 2026, all MCP URL requests without the `x-api-key` header will be rejected. Please ensure you update your applications before this date to avoid service disruption.
20
21 **Note**: If you're already passing the `x-api-key` header in your MCP requests, no action is required—you're all set!
22