Repository navigation
After 0.4.0: the app's icon in server.json - #65
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
Follow-up to the v0.4.0 release (#64).
server.jsongetsicons: the 400×400 PNG atassets/logo-400.pngon main, so the MCP Registry and directories that read it show the app's icon. Checked withmcp-publisher validate(schema 2025-12-11) andpackages/cli/test/server-json.test.js.date(2026-11-03) already matches the release, published on 2026-11-03, so it's unchanged;releasedflips by itself now that the release exists.Note: the icon only reaches the registry with the next
mcp-publisher publish. The registry doesn't allow republishing the same version, so it either goes out with the first publish of 0.2.0 (if this merges first) or with the next CLI version.