Repository navigation
chore(schemas): drop registryUrl and registryBranch from vendored schemas - #10
Merged
Merged
Conversation
…emas The CLI removed both overrides; it reads the registry only through the ATK API. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Mirrors the CLI (EmergentSoftware/agentic-toolkit-cli#284): the CLI no longer has registry location overrides and reads the registry only through the ATK API. Nothing in the web app reads either field.
Edited by hand:
pnpm sync-schemasexpects a sibling checkout namedagentic-toolkit, and a full sync would also pull in unrelated schema changes.Test plan
pnpm typecheck,pnpm lint,pnpm test(349 pass)🤖 Generated with Claude Code