Skip to content

Make MCP coverage reports cover the whole evergreen PR - #228

Closed
rgarcia wants to merge 1 commit into
mainfrom
hypeship/mcp-updater-cumulative-baseline
Closed

rgarcia wants to merge 1 commit into
mainfrom
hypeship/mcp-updater-cumulative-baseline

Conversation

@rgarcia

@rgarcia rgarcia commented Oct 30, 2026

Copy link
Copy Markdown
Contributor

Summary

Fixes for the MCP coverage updater, found while reviewing the docs updater (#225).

  • The PR description only covered the latest release. The baseline SDK version was read from the evergreen branch, so each run diffed only since the previous bot commit, and gh pr edit --body-file replaced the description with that run's increment. For example, kernel-mcp-server#262 holds bumps from 0.133.0 through 0.139.0, but its description only covers 0.139.0. The baseline now comes from origin/main's package.json, so each run audits every release since main and its report describes the whole PR. The prompt says so, and tells the agent that earlier runs may already have covered part of the diff. The stale-run check still uses the branch's pinned version.
  • Hand-written SDK helpers were missing from the diff. src/client.ts and src/lib (browser routing, browser fetch, audit log download, config registry wait) are user-facing but weren't in the SDK diff. They are now.
  • The spec can be ahead of the SDK. The spec is fetched from the API's main branch at release time, so it can describe operations the released SDK doesn't have. The prompt now says the SDK defines what exists, and the spec is only used for the meaning of things the SDK has.

Testing

  • actionlint with shellcheck passes, apart from the existing info-level SC2016.
  • Checked locally that git show origin/main:package.json | jq reads kernel-mcp-server main's pinned SDK version (0.132.0).
  • The updated workflow hasn't run in Actions yet. The next run audits 0.132.0 through the current release, so it takes longer than an incremental run.

@rgarcia
rgarcia requested a review from hiroTamada October 30, 2026 14:57
@rgarcia

rgarcia commented Oct 30, 2026

Copy link
Copy Markdown
Contributor Author

Closing: custom code goes through the staging SDK repo. Will reopen there.

@rgarcia rgarcia closed this Oct 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant