fix(publish): drop OCI package entry from server.json#1587
Merged
yury-s merged 1 commit intomicrosoft:mainfrom May 1, 2026
Merged
fix(publish): drop OCI package entry from server.json#1587yury-s merged 1 commit intomicrosoft:mainfrom
yury-s merged 1 commit intomicrosoft:mainfrom
Conversation
The MCP Registry's runtime validator rejects 'registryBaseUrl' for OCI packages and requires the canonical reference (registry/repo:tag) to live in 'identifier' instead. Keeping it in sync across releases would need extra workflow plumbing, and the OCI listing isn't needed to unblock the original ask in microsoft#1477 (registryOnly clients install via npm). Docker users still pull directly from playwright.azurecr.io.
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.
Summary
The first dispatch run after #1586 (failed run) hit:
The schema permits
registryBaseUrl, but the registry's runtime validator rejects it for OCI. The npm entry validated cleanly.Fix
Drop the OCI package entry from
server.json. The npm listing alone resolves #1477 (VS Code + Copilot inregistryOnlymode installs via npx). Docker users still pull directly fromplaywright.azurecr.io— that channel doesn't need the registry to be discoverable.Why not reformat the OCI identifier
The canonical-reference form (
registry/repo:tag) bakes the version into the string, which means each release has to bump bothversionand the tag insideidentifier. The version-validation step in CI would also need OCI-specific logic. Manageable but extra plumbing for a channel we don't need to list. Can be added back in a focused PR if it's ever needed.Verifying
After merge, manually fire the
Publishworkflow againstmainfrom the Actions tab to publish v0.0.72 retroactively.