Repository navigation
v0.2.1 — reproducible .mcpb builds
What's in it
0.2.1 is a release about the release: the .mcpb is now byte-reproducible, so the bundle published here can be rebuilt from this tag and come out identical — and CI fails if it doesn't.
The v0.2.0 tag predates these fixes, so its bundle cannot be rebuilt reproducibly. Reproducibility starts with this tag.
Reproducible .mcpb
- Bundles are written by a deterministic in-Node zip writer (
scripts/zip-writer.mjs) instead ofbsdtar/zip: entries in sorted order, one fixed timestamp, no extra fields and no host-derived attributes. - Text payloads are normalised to LF as they are archived, so a CRLF checkout and an LF checkout produce the same bytes.
- A CI job builds the bundle on Linux and Windows and fails the build if the two hashes differ.
Checks that keep the release honest
mcpb:smokeinstalls the bundle the way a host does and drives it with the official@modelcontextprotocol/clientSDK: the officialmcpbCLI validates the manifest,initializereports this version,tools/listandprompts/listare complete, andlist-testsis really called against a fixture project.- The
.mcpb.sha256sidecar now hashes LF-normalised lockfile content, so thepackage-lock.jsonhash it records matches the file committed in this repository rather than a Windows working-tree copy.
Reproducing this bundle
git clone https://github.com/trajectiq-ai/E2E && cd E2E/playwright-e2e-mcp
git checkout v0.2.1
npm ci && npm run mcpb
sha256sum playwright-e2e-mcp-0.2.1.mcpb
# 1e02c31e81e93614fbe839757e13d3d287a22571d7ea0a49075e28024b55985bVerifying this download
# from the folder you downloaded into:
sha256sum -c SHA256SUMS.txtThe .mcpb.sha256 sidecar also records the hash of the package-lock.json the bundle was built from, which ties the bundle back to this repository. Check it inside a checkout of this tag, with the downloaded bundle alongside it:
git checkout v0.2.1
sha256sum -c playwright-e2e-mcp-0.2.1.mcpb.sha256
# playwright-e2e-mcp-0.2.1.mcpb: OK
# package-lock.json: OKThe recorded lockfile hash is taken over LF-normalised content — the file as committed. On a Windows checkout with core.autocrlf=true your working copy is CRLF, so that one line will not match it; compare against git show v0.2.1:package-lock.json instead. (v0.2.0 recorded a Windows working-tree hash that nobody else could reproduce, which is what this release corrects.)
| asset | what it is |
|---|---|
playwright-e2e-mcp-0.2.1.mcpb |
Claude Desktop / MCP bundle — byte-reproducible |
playwright-e2e-mcp-0.2.1.mcpb.sha256 |
bundle hash, plus the hash of the lockfile it was built from |
playwright-e2e-mcp-0.2.1.tgz |
npm tarball |
SHA256SUMS.txt |
hashes of both artifacts above |
Changed
- Version moves to
0.2.1inpackage.json,package-lock.jsonandserver.json; README pins and the documented download URL move tov0.2.1. - README demo images regenerated so the endpoint card shows the released version.
A note on the hashes
-
The
.mcpbis byte-identical regardless of platform, Node version or line endings. It is the artifact to reproduce: the recipe above rebuilds it exactly. -
The
.tgzhere is the exact artifact published to npm by thePublish to npmworkflow on this tag, with provenance, so it can be checked against the registry too:sha512-THfK1YANDQpbI6bNjG81A/iwCWuQhrrPqCaNwcrH3rD8mr1ZDEHwc2caht+SKAQ0hl4nQ/UfFd62qOalqbAMKQ==npm preserves the packer's line endings for
README.md,package.jsonanddist/tools/probe-script.js, so a tarball you pack yourself can differ byte-for-byte from this one — a Windows pack differs in exactly those three files.