Skip to content

Commit b6f1f96

Browse files
committed
Repin to conformance main@b18aa918 (merge of #371)
conformance#371 has merged. Switch the pkg.pr.new pin from the PR-branch commit (ed314a73) to the merge commit on main (b18aa918) — same tarball bytes (SHA256 unchanged), but durable against PR-branch deletion. No published @modelcontextprotocol/conformance release includes #371 yet (latest is 0.2.0-alpha.7, cut before the merge), so the pkg.pr.new + SHA256 verify machinery stays for now.
1 parent 8d58fe2 commit b6f1f96

1 file changed

Lines changed: 9 additions & 8 deletions

File tree

.github/workflows/conformance.yml

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -19,15 +19,16 @@ env:
1919
# Bump deliberately and reconcile both
2020
# .github/actions/conformance/expected-failures*.yml files in the same change.
2121
#
22-
# Temporarily pinned to the pkg.pr.new preview build of conformance#371, which
23-
# fixes the http-custom-headers fixture's spec-forbidden `number`-typed
24-
# x-mcp-header annotations. Pinned by commit SHA (not PR number) so a new push
25-
# to #371 cannot silently change the tarball; CONFORMANCE_PKG_SHA256 then pins
26-
# the bytes and the fetch-and-verify step below downloads, checks the digest,
27-
# and repoints CONFORMANCE_PKG at the verified local copy. Repin to the
28-
# published release that includes #371 once it ships, then drop
22+
# Temporarily pinned to the pkg.pr.new build of conformance main@b18aa918
23+
# (the merge of #371, which fixes the http-custom-headers fixture's
24+
# spec-forbidden `number`-typed x-mcp-header annotations) — no published
25+
# release includes it yet. Pinned by commit SHA so the tarball cannot move
26+
# under us; CONFORMANCE_PKG_SHA256 pins the bytes and the fetch-and-verify
27+
# step below downloads, checks the digest, and repoints CONFORMANCE_PKG at the
28+
# verified local copy. Repin to the next published @modelcontextprotocol/
29+
# conformance release (>0.2.0-alpha.7) once it ships, then drop
2930
# CONFORMANCE_PKG_SHA256 and the fetch-and-verify steps.
30-
CONFORMANCE_PKG: "https://pkg.pr.new/@modelcontextprotocol/conformance@ed314a73"
31+
CONFORMANCE_PKG: "https://pkg.pr.new/@modelcontextprotocol/conformance@b18aa918"
3132
CONFORMANCE_PKG_SHA256: "e9f6bc25085b4692e988cbdbd024a4203d54a52a6aaa065376cf8ecaa09bb680"
3233

3334
jobs:

0 commit comments

Comments
 (0)