fix(ui): Update API endpoints from /admin/v0 to /v0 after backend refactor#208
Merged
timflannagan merged 1 commit intoagentregistry-dev:mainfrom Feb 23, 2026
Merged
Conversation
…actor After PR agentregistry-dev#185 (commit fb54b9f), which removed /admin/v0 endpoints from the backend, the UI was not updated and continues trying to call the now-deleted endpoints. This causes all admin UI pages to fail with 404 errors. This commit updates ui/lib/admin-api.ts to use /v0/* endpoints instead of /admin/v0/*, matching the current backend API structure. Changes: - Replace all /admin/v0 references with /v0 in ui/lib/admin-api.ts - Update comment to reflect correct API path Testing: - Verified UI can successfully fetch servers, agents, skills, and deployments - Confirmed all admin UI pages load without 404 errors - Tested against local registry server Fixes the admin UI broken since PR agentregistry-dev#185.
peterj
approved these changes
Feb 23, 2026
Collaborator
|
Looks like the workflows are stuck. Going to try closing/re-opening to see if that unsticks CI. |
timflannagan
approved these changes
Feb 23, 2026
christian-posta
pushed a commit
to christian-posta/agentregistry
that referenced
this pull request
Mar 9, 2026
…actor (agentregistry-dev#208) # Description After PR agentregistry-dev#185 (commit fb54b9f), which removed `/admin/v0` endpoints from the backend, the UI was not updated and continues trying to call the now-deleted endpoints. This causes all admin UI pages to fail with 404 errors. **What changed:** - Updated `ui/lib/admin-api.ts` to use `/v0/*` endpoints instead of `/admin/v0/*`, matching the current backend API structure - Changed all 26 occurrences of `/admin/v0` to `/v0` - Updated comment to reflect correct API path **Testing:** - ✅ Verified UI can successfully fetch servers, agents, skills, and deployments - ✅ Confirmed all admin UI pages load without 404 errors - ✅ Tested against local registry server Fixes the admin UI broken since PR agentregistry-dev#185. # Change Type /kind fix # Changelog ```release-note fix(ui): Update API client to use /v0 endpoints after backend refactor removed /admin/v0 routes ``` # Additional Notes This is a critical bug fix - the admin UI has been completely non-functional since the backend refactor in PR agentregistry-dev#185. All API calls were returning 404 errors because the UI was calling endpoints that no longer exist.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
After PR #185 (commit fb54b9f), which removed
/admin/v0endpoints from the backend, the UI was not updated and continues trying to call the now-deleted endpoints. This causes all admin UI pages to fail with 404 errors.What changed:
ui/lib/admin-api.tsto use/v0/*endpoints instead of/admin/v0/*, matching the current backend API structure/admin/v0to/v0Testing:
Fixes the admin UI broken since PR #185.
Change Type
/kind fix
Changelog
Additional Notes
This is a critical bug fix - the admin UI has been completely non-functional since the backend refactor in PR #185. All API calls were returning 404 errors because the UI was calling endpoints that no longer exist.