fix(release): add missing server.json for MCP registry publish - #41
Closed
asachs01 wants to merge 1 commit into
Closed
fix(release): add missing server.json for MCP registry publish#41asachs01 wants to merge 1 commit into
asachs01 wants to merge 1 commit into
Conversation
Release run 31139355966 (2026-08-07) failed at the 'Publish to MCP Registry' step: jq: error: Could not open file server.json -- this repo never had one, unlike every other *-mcp repo. Every release will fail at this step until it exists. Modeled on action1-mcp's server.json (same reusable release workflow, same schema). Environment variables match src/auth/azureAuth.ts and src/client/afkbotClient.ts exactly (AZURE_TENANT_ID, AZURE_CLIENT_ID, AZURE_CLIENT_SECRET required; AFKBOT_API_URL, AFKBOT_APP_CLIENT_ID optional) -- transport is stdio-only, no MCP_TRANSPORT/AUTH_MODE vars (this repo doesn't support gateway header-injection mode). Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
Member
Author
|
Closing — superseded by Aaron's decision (2026-08-19, decision batch 3, item 5): afkbot-mcp stays private/internal, the deliberate 2026-04-29 revert of server.json stands. Option (b) instead: decouple the deploy job in release.yml from the mcp-registry sub-job's (expected) failure. See follow-up PR. |
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.
Problem
Release run 31139355966 (2026-08-07) fails at 'Publish to MCP Registry':
jq: error: Could not open file server.json. This repo never had aserver.json— every other *-mcp repo does, since the shared release workflow's 'Stamp version into server.json' step expects one committed with0.0.0placeholders. Reference: task_1786072998734.Fix
Added
server.json, modeled on action1-mcp's (same schema, same reusable release workflow). Environment variables verified directly against source (src/auth/azureAuth.ts,src/client/afkbotClient.ts) rather than guessed from the README:AZURE_TENANT_ID,AZURE_CLIENT_ID,AZURE_CLIENT_SECRET— requiredAFKBOT_API_URL,AFKBOT_APP_CLIENT_ID— optionalMCP_TRANSPORT/AUTH_MODE, unlike some siblings that support gateway header-injection)Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.