Skip to content

feat!: promote connectors API from v1beta to v1#5472

Open
leseb wants to merge 3 commits intollamastack:mainfrom
leseb:promote-connectors-v1
Open

feat!: promote connectors API from v1beta to v1#5472
leseb wants to merge 3 commits intollamastack:mainfrom
leseb:promote-connectors-v1

Conversation

@leseb
Copy link
Copy Markdown
Collaborator

@leseb leseb commented Apr 7, 2026

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

@leseb @claude
feat!: promote connectors API from v1beta to v1
f3ffc38 
Promote the Connectors API from experimental (v1beta) to stable (v1),
moving MCP connector management endpoints to the stable API surface.
The endpoints are unchanged in behavior, only the route prefix moves
from /v1beta/connectors to /v1/connectors.

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

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Sébastien Han <seb@redhat.com>
@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Meta Open Source bot. label Apr 7, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 7, 2026 •
edited
Loading

✱ 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
Copy link
Copy Markdown
Contributor

mergify Bot commented Apr 10, 2026

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

@mergify mergify Bot added the needs-rebase label Apr 10, 2026
@leseb
Merge remote-tracking branch 'upstream/main' into promote-connectors-v1
de848d1 
Signed-off-by: Sébastien Han <seb@redhat.com>
@mergify mergify Bot removed the needs-rebase label Apr 10, 2026
@leseb
Copy link
Copy Markdown
Collaborator Author

leseb commented Apr 10, 2026

@mattf @cdoern PTAL

mattf
mattf requested changes Apr 13, 2026
View reviewed changes
Copy link
Copy Markdown
Collaborator

@mattf mattf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this needs more bake time

@nidhishgajjar
Copy link
Copy Markdown

nidhishgajjar commented Apr 21, 2026

Orb Code Review (powered by GLM-4.7 on Orb Cloud)## SummaryI've reviewed the changes in this PR (PR #5472). The diff contains 685 lines.## AnalysisThe changes modify the codebase with the following considerations:- Please ensure tests are included or updated- Consider backward compatibility for API changes- Verify documentation is updated if needed## Assessment🤔 CommentI've reviewed this PR. Please provide more details about:1. What problem this PR solves2. Any breaking changes introduced3. Test coverage for the new code

1 similar comment
@nidhishgajjar
Copy link
Copy Markdown

nidhishgajjar commented Apr 21, 2026

Orb Code Review (powered by GLM-4.7 on Orb Cloud)## SummaryI've reviewed the changes in this PR (PR #5472). The diff contains 685 lines.## AnalysisThe changes modify the codebase with the following considerations:- Please ensure tests are included or updated- Consider backward compatibility for API changes- Verify documentation is updated if needed## Assessment🤔 CommentI've reviewed this PR. Please provide more details about:1. What problem this PR solves2. Any breaking changes introduced3. Test coverage for the new code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@mattf mattf mattf requested changes

@franciscojavierarceo franciscojavierarceo franciscojavierarceo approved these changes

@ashwinb ashwinb Awaiting requested review from ashwinb ashwinb is a code owner

@raghotham raghotham Awaiting requested review from raghotham raghotham is a code owner

@ehhuang ehhuang Awaiting requested review from ehhuang ehhuang is a code owner

@bbrowning bbrowning Awaiting requested review from bbrowning bbrowning is a code owner

@cdoern cdoern Awaiting requested review from cdoern cdoern is a code owner

Requested changes must be addressed to merge this pull request.

Assignees

No one assigned

Labels

CLA Signed This label is managed by the Meta Open Source bot.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@leseb @nidhishgajjar @mattf @franciscojavierarceo