feat!: promote connectors API from v1beta to v1

[leseb]

Summary

• Promote the Connectors API from experimental (v1beta) to stable (v1), moving MCP connector management endpoints to the stable API surface
• Endpoints are unchanged in behavior, only the route prefix moves from /v1beta/connectors to /v1/connectors
• OpenAPI specs regenerated: connectors endpoints move from experimental-llama-stack-spec.yaml to llama-stack-spec.yaml

BREAKING CHANGE: Connectors API endpoints moved from /v1beta/ to /v1/. Clients using /v1beta/connectors must update to /v1/connectors.

Test plan

• uv run pytest tests/unit/core/routers/test_connectors_router.py -x --tb=short (15/15 passing)
• uv run pre-commit run --all-files (all checks pass)
• OpenAPI spec validation (stable, experimental, deprecated, stainless all valid)

🤖 Generated with Claude Code

[github-actions]

✱ Stainless preview builds

This PR will update the llama-stack-client SDKs with the following commit message.

feat!: promote connectors API from v1beta to v1

Edit this comment to update it. It will appear in the SDK's changelogs.

✅ llama-stack-client-openapi studio · code · diff

Your SDK build had at least one "warning" diagnostic, but this did not represent a regression.
generate ⚠️

New diagnostics (4 note)

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/connectors`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/connectors/{connector_id}/tools/{tool_name}`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/connectors/{connector_id}/tools`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/connectors/{connector_id}`

✅ llama-stack-client-go studio · conflict

Your SDK build had at least one new note diagnostic, which is a regression from the base state.

New diagnostics (4 note)

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/connectors`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/connectors/{connector_id}/tools/{tool_name}`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/connectors/{connector_id}/tools`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/connectors/{connector_id}`

✅ llama-stack-client-python studio · conflict

Your SDK build had at least one new note diagnostic, which is a regression from the base state.

New diagnostics (4 note)

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/connectors`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/connectors/{connector_id}/tools/{tool_name}`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/connectors/{connector_id}/tools`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/connectors/{connector_id}`

✅ llama-stack-client-node studio · conflict

Your SDK build had at least one new note diagnostic, which is a regression from the base state.

New diagnostics (4 note)

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/connectors`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/connectors/{connector_id}/tools/{tool_name}`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/connectors/{connector_id}/tools`

💡 Endpoint/NotConfigured: Skipped endpoint because it's not in your Stainless config: `get /v1/connectors/{connector_id}`

---

This comment is auto-generated by GitHub Actions and is automatically kept up to date as you push.
If you push custom code to the preview branch, re-run this workflow to update the comment.
Last updated: 2026-04-10 13:11:01 UTC

[mergify]

This pull request has merge conflicts that must be resolved before it can be merged. @leseb please rebase it. https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork

[leseb]

@mattf @cdoern PTAL

[mattf]

this needs more bake time