Repository navigation
Conversation
|
A quick update: Symfony AI 1.0.0-BETA1 has now been released, including We've migrated our shared AI bundles and consuming apps to beta 1. API Platform's MCP integration remains a blocker: we've temporarily disabled it in affected apps, and kept one app on the older MCP bundle where we still need that integration. My expectation is that entering beta should mean fewer breaking changes as Symfony AI approaches 1.0, though that's an expectation, not a backward-compatibility guarantee—particularly for the separately versioned MCP SDK, which is still at 0.9. This PR keeps support for both SDK 0.8 and 0.9; the targeted registry tests already pass against both versions. Would you be open to moving this compatibility fix forward now that beta 1 is available? |
|
@soyuka, a nudge on this one. Symfony AI 1.0.0-BETA1 is out, and |
MCP SDK 0.9 adds
RegistryInterface::publishesListChanges(), so loadingSecureRegistrycurrently fails with a missing abstract method when using Symfony MCP bundle 0.15. Forward the capability to the decorated registry, retain SDK 0.8 compatibility, and allow both SDK versions in Composer.src/Mcp/Tests/Capability/Registry/SecureRegistryTest.phpreproduces the fatal error before the fix and checks both true and false forwarding without triggering lazy loading. The capability tests pass with SDK 0.9.0 (17 tests, 38 assertions) and 0.8.1 (17 tests, 38 assertions); existing PHPUnit mock notices remain. Targeted PHPStan, PHP CS Fixer, and Composer validation pass.