Pin conformance harness to main@b18aa918 (merge of #371) via pkg.pr.new
A second commit landed on modelcontextprotocol/conformance#371, which caused pkg.pr.new to rebuild the @371 tarball; the new bytes no longer matched CONFORMANCE_PKG_SHA256, so the fetch-and-verify step started failing on every conformance run. #371 has since merged to conformance main as b18aa918.
Motivation and Context
Re-pin to the per-commit pkg.pr.new build of b18aa918 (the merge commit on conformance main) and bump CONFORMANCE_PKG_SHA256 to match. No published @modelcontextprotocol/conformance release includes #371 yet — 0.2.0-alpha.7 was cut the day before the merge — so the pkg.pr.new + SHA256-verify machinery stays for now. Once the next release ships, we'll repin to the registry version and drop the fetch-and-verify steps (per the comment in the workflow).
How Has This Been Tested?
Downloaded https://pkg.pr.new/@modelcontextprotocol/conformance@b18aa918 and verified its SHA256 is e9f6bc25085b4692e988cbdbd024a4203d54a52a6aaa065376cf8ecaa09bb680. The conformance workflow on this branch will confirm.
Breaking Changes
None — CI config only.
Types of changes
- Bug fix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)
- Breaking change (fix or feature that would cause existing functionality to change)
- Documentation update
Checklist
- I have read the MCP Documentation
- My code follows the repository's style guidelines
- New and existing tests pass locally
- I have added appropriate error handling
- I have added or updated documentation as needed
Additional context
The first commit on this branch pinned to the PR-branch commit ed314a73; the second retargets to the merge commit on main (same tarball bytes, but durable against PR-branch deletion).