Attach the Claude Desktop bundle to published releases

[lloydwatkin]

🤖 The bundle was only ever a CI build artifact, so installing it meant digging through the Actions tab for a green run on the right commit. The release workflow now packs it and uploads activeadmin-mcp-X.Y.Z.mcpb as an asset on the release that produced it.

The release tag now versions the bundle too

The workflow writes the tag into mcpb/manifest.json and mcpb/package.json before packing, and commits those bumps back alongside version.rb.

The manual bump the README asked for had already been missed: the bundle sits at 0.0.3 against a 0.0.4 gem. Claude Desktop reads the manifest version to detect upgrades, so a stale one means colleagues are never offered the update. The gem and the bundle can no longer drift apart.

I left the two JSON files at 0.0.3 in this branch rather than hand-fixing them — the next release overwrites both from the tag, so bumping them now would just be undone.

Ordering

The proxy tests and the pack run before gem push, so a broken bundle stops the release rather than trailing an irreversible publish. The upload uses --clobber, so re-running the workflow on a release replaces the asset instead of failing.

Node 24

CI and the release workflow both move from Node 22 (Jod, now maintenance) to Node 24 (Krypton, current LTS). The bundle's own >=18.0.0 floor is unchanged — that governs the machines colleagues install on, not the machine that packs the file.

Verification

• npm test in mcpb/ on a real node:24 container (v24.21.0): 13 pass, 0 fail.
• npx @anthropic-ai/mcpb pack . ../activeadmin-mcp-1.2.3.mcpb on Node 24: writes the file at the explicit versioned path (2,933 bytes, 3 files).
• The sed rewrites run against copies of the real manifest.json and package.json under GNU sed in ubuntu:24.04 — the leading quote in the pattern keeps them off manifest_version.
• Workflow YAML parses; step order confirmed.

Not verified: the workflow end to end. gh release upload can't be rehearsed without cutting a release, so that step is the riskiest line here. If it fails the gem is already published and the job needs re-running — which --clobber makes safe.

🤖 Generated with Claude Code