tier-check spec-tracking does not detect SDK releases published shortly before the spec release

Open
#459 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
70/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
cli, release, testing-qa

Research direction

Start in src/tier-check/checks/spec-tracking.ts and run tier-check --repo modelcontextprotocol/python-sdk to observe the current gap. Update the check so the SDK release published shortly before the latest spec release is detected, then verify that the example release no longer produces a growing gap or a Tier 1 failure.

Written by the indexing model from the issue text.

Description

tier-check's spec-tracking check (src/tier-check/checks/spec-tracking.ts) looks for the first SDK release published at or after the latest spec release. An SDK release published shortly before the spec release is tagged is not detected as the release for that spec, so the SDK reads as "no release yet" and the check turns fail (a Tier 1 blocker) 30 days after the spec release unless the SDK happens to publish again.

Example: the 2026-07-28 spec release was published at 16:47Z; python-sdk v2.0.0 went out at 13:41Z the same day (three hours earlier), so tier-check --repo modelcontextprotocol/python-sdk currently reports a growing "Nd gap" and will report fail from 2026-08-28. go-sdk v1.7.0 (13:09Z) and typescript-sdk's 2.0.0 packages (published the evening before) are in the same position; csharp-sdk v2.0.0 (21:27Z, after the tag) is detected fine.

Dominant language
TypeScript
Stars
127
Forks
101
Avg merge
4d 7h
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from modelcontextprotocol/conformance

All issues in modelcontextprotocol/conformance

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.