Skip to content

chore: migrate to updated registry server API#474

Draft
peppescg wants to merge 1 commit intomainfrom
chore/migrate-to-new-registry-api
Draft

chore: migrate to updated registry server API#474
peppescg wants to merge 1 commit intomainfrom
chore/migrate-to-new-registry-api

Conversation

@peppescg
Copy link
Copy Markdown
Collaborator

Summary

  • Regenerated API client from latest swagger.json (toolhive-registry-server main)
  • Updated all call sites to match breaking path changes in the backend API
  • Updated MSW fixtures and test imports accordingly

API changes

Old endpoint New endpoint
GET /extension/v0/registries GET /v1/registries
GET /registry/v0.1/servers GET /registry/{registryName}/v0.1/servers
GET /registry/v0.1/servers/{serverName}/versions/{version} GET /registry/{registryName}/v0.1/servers/{serverName}/versions/{version}

Test plan

  • pnpm type-check passes
  • pnpm lint passes
  • pnpm test — 194/194 tests pass
  • Catalog page loads servers from local registry server

🤖 Generated with Claude Code

Regenerate client from latest swagger and update all call sites to
match the breaking API path changes in toolhive-registry-server:

- GET /extension/v0/registries → GET /v1/registries
- GET /registry/v0.1/servers → GET /registry/{registryName}/v0.1/servers
- GET /registry/v0.1/servers/{serverName}/versions/{version}
  → GET /registry/{registryName}/v0.1/servers/{serverName}/versions/{version}

Update MSW fixtures and test imports accordingly.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions github-actions bot added the size/XL Extra large PR: 1000+ lines changed label Mar 30, 2026
Copy link
Copy Markdown
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Large PR Detected

This PR exceeds 1000 lines of changes and requires justification before it can be reviewed.

How to unblock this PR:

Add a section to your PR description with the following format:

## Large PR Justification

[Explain why this PR must be large, such as:]

- Generated code that cannot be split
- Large refactoring that must be atomic
- Multiple related changes that would break if separated
- Migration or data transformation

Alternative:

Consider splitting this PR into smaller, focused changes (< 1000 lines each) for easier review and reduced risk.

See our Contributing Guidelines for more details on the pull request process.


This review will be automatically dismissed once you add the justification section.

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

Labels

size/XL Extra large PR: 1000+ lines changed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant