refactor(manifests): remove MCP resource field - #191
Merged
Conversation
Contributor
Preview deployment
Commit: |
Contributor
Preview deployment cleaned upThe preview deployment for PR #191 has been removed. |
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.
What changed
resourceUrls.mcpfrom all product manifests, the product schema, and TypeScript types.Impact
Product manifests now expose a smaller, consistent resource URL shape. MCP support can still be documented as product capability text without maintaining a dedicated global URL field.
Validation
pnpm test:ci(154 passed, 4 skipped)pnpm type-checkpnpm validate:i18npnpm validate:i18n-usagepnpm validate:i18n-duplicatespnpm data-health:check