fix(release): align server.json with package.json (0.18.2) + drift guard - #95
Merged
Merged
Conversation
server.json sat at 0.17.2 since the 0.17.2 release, so release.yml's MCP-Registry guard (server.json.version == package.json.version) FAILED on 0.17.3, 0.18.0, and 0.18.1 — npm and the GitHub .mcpb shipped each time, but the registry listing silently went stale. Align both server.json version fields (top-level + packages[0].version) to track package.json, and add test/audit/server-json-version.test.ts so any future drift fails at PR time instead of only at release. Patch-bump to 0.18.2 so a release fires and the registry finally re-syncs. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
runtimeArguments + the env-var hint still pinned @leadbay/mcp@0.17, so a registry-sourced `npx` install would pull the 0.17.x line (without the quota fix). Bump both to @0.18, and extend the audit to assert every @leadbay/mcp@<major.minor> pin tracks package.json's version line — so the install pin can't silently lag the way the version field did. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
milstan
added a commit
that referenced
this pull request
Jun 9, 2026
…s hosts (WF#16-18) Server-built deterministic next_steps on leadbay_pull_leads (the "Triage board" artifact offer pinned at options[0], null on empty batch), the dual host-widget schema (ask_user_input_v0 + AskUserQuestion) documented and made widget-mandatory-when-available, and WF#16-18 contracts. Rebased onto current main (origin PR #70, squashed): version-bump collision resolved at 0.19.0 (main reached 0.18.2); bumped packages/mcp/server.json version fields + the @leadbay/mcp npx pins to 0.19 to satisfy the new server-json-version drift guard (#95); merged the 0.18.1 / 0.18.2 CHANGELOG entries; regenerated tool descriptions / prompts / skills from the merged templates (textual auto-merge of tool-descriptions.generated.ts was stale, picked up #89's quota description changes on regen). Co-authored-by: milstan <milstan@gmail.com> Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
milstan
added a commit
that referenced
this pull request
Jun 9, 2026
…s hosts (WF#13–15) (#70) * fix(widgets): reliable next-step / artifact / scheduling offers across hosts (WF#16-18) Server-built deterministic next_steps on leadbay_pull_leads (the "Triage board" artifact offer pinned at options[0], null on empty batch), the dual host-widget schema (ask_user_input_v0 + AskUserQuestion) documented and made widget-mandatory-when-available, and WF#16-18 contracts. Rebased onto current main (origin PR #70, squashed): version-bump collision resolved at 0.19.0 (main reached 0.18.2); bumped packages/mcp/server.json version fields + the @leadbay/mcp npx pins to 0.19 to satisfy the new server-json-version drift guard (#95); merged the 0.18.1 / 0.18.2 CHANGELOG entries; regenerated tool descriptions / prompts / skills from the merged templates (textual auto-merge of tool-descriptions.generated.ts was stale, picked up #89's quota description changes on regen). Co-authored-by: milstan <milstan@gmail.com> Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * chore(eval): move dashboard generator into eval helpers --------- Co-authored-by: milstan <milstan@gmail.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
milstan
added a commit
that referenced
this pull request
Jun 10, 2026
Resolve conflicts after main advanced to 0.19.0 (#93 contacts, #95 server-json): - WORKFLOWS.md: keep main's contact rows (15-23) + append new scan_portfolio_signals row (24); renumber. - research_lead_by_id description: trim 50 chars of redundant prose to absorb main's new add_contact anti-trigger (auto-emitted into WHEN TO USE), restoring the 17000-char budget (now 16973). - Regenerate tool-descriptions.generated.ts. Version stays 0.19.1 (main 0.19.0 + patch). Co-Authored-By: Claude Opus 4.8 (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.
Problem
packages/mcp/server.json(the MCP-Registry manifest) was stuck at 0.17.2 since the 0.17.2 release.release.yml's registry step verifiesserver.json.version == package.json.version, so it has failed on every release since: 0.17.3, 0.18.0, and 0.18.1. npm + the GitHub.mcpbshipped each time (those are the channels installs/auto-update actually use), but the MCP-Registry listing silently went stale — caught only at release time, after the fact.Surfaced while delivering #89 (0.18.1): npm published, GitHub release +
.mcpbpublished, registry step failed onDrift: package.json=0.18.1 server.json=0.17.2.Change
server.jsonversion fields — top-levelversionandpackages[0].version— topackage.json(0.18.2).packages/mcp/test/audit/server-json-version.test.tsasserts the alignment (version match on both fields +server.json.name == package.json.mcpName+ npmidentifier == package.json.name). Drift now fails at PR time, not silently at release.package.json→0.18.2so a release fires and the registry finally re-syncs (the fix is inert without a new release; npm won't let 0.18.1 republish).Heads-up (not changed here — flagging for a call)
server.jsonpackages[0].runtimeArgumentsstill pin@leadbay/mcp@0.17(and theLEADBAY_TOKENenv hint references@0.17). Once this publishes, a user installing via the MCP Registry would still getnpx @leadbay/mcp@0.17— i.e. the 0.17.x line, without the quota fix. Left untouched because the major.minor pin looks deliberate; say the word and I'll bump those to@0.18(or unpin) in a follow-up.Verification
pnpm -r build+pnpm -r typecheck— greenpnpm -r test— green (core 344 / promptforge 16 / mcp 374, incl. the 4 new audit assertions)🤖 Generated with Claude Code