Skip to content

ci: stop publishing to Smithery, which shuts down on October 31 - #116

Merged
travist merged 1 commit into
mainfrom
remove-smithery
Oct 30, 2026
Merged

travist merged 1 commit into
mainfrom
remove-smithery

Conversation

@travist

@travist travist commented Oct 30, 2026

Copy link
Copy Markdown
Member

Smithery shuts down its connection services on October 31, 2026 (https://smithery.ai/future): its API, CLI, accounts and hosted server URLs stop working, and only a public directory remains. Publishing updates is already refused, so the release workflow's Smithery step failed the @formio/ai 1.1.0 release (run 41093812513) with 403 {"error":"Updating servers has been removed. Contact support@smithery.ai."} and skipped the Docker Hub decision after it. Every release would fail the same way.

Changes

  • .github/workflows/release.yml: removes the "Publish the bundle to Smithery" step and its SMITHERY_API_KEY, and Smithery from the comments that list the downstream publishes.
  • scripts/build-mcpb.ts: builds one bundle, dist/formio-mcp.mcpb. The .smithery.mcpb variant existed only to pass Smithery's manifest validation.
  • smithery.yaml: removed.
  • OpenSpec change remove-smithery-publish: Smithery is no longer one of the channels claude-plugin-release publishes on every release.

The Smithery badges in the READMEs stay: the listing remains in Smithery's public directory, frozen at its last version. packages/mcp-server/README.md ships in the npm package, so pnpm check:releases would require an @formio/mcp release to change it; it can go with the next one.

No published package changes, so there is no changeset.

Tests

  • New release-channels.test.ts: the workflow has no Smithery step and reads no Smithery credential.
  • mcpb-build.test.ts 1.12: the build produces formio-mcp.mcpb and no Smithery variant (replaces the test that checked the variant).
  • Both failed before the change and pass after. packages/mcp-server: 1939 passing. packages/skill-tests: 1669 passing. pnpm check:releases --base=origin/main: passes.

After merging, the SMITHERY_API_KEY repository secret can be deleted.

🤖 Generated with Claude Code

Smithery shuts down its connection services on October 31, 2026
(https://smithery.ai/future), and its API already refuses updates: the
release workflow's Smithery step failed the @formio/ai 1.1.0 release with
`403 Updating servers has been removed` and skipped the Docker Hub decision
after it. Every release would fail the same way.

The workflow no longer publishes there or reads SMITHERY_API_KEY, and the
bundle build makes one archive, dist/formio-mcp.mcpb, without the
.smithery.mcpb variant that existed only for Smithery's manifest validation.
smithery.yaml is removed. The README badges stay: the listing remains in
Smithery's public directory, and the server README ships in the npm package,
so it changes with the next @formio/mcp release.

OpenSpec change remove-smithery-publish: Smithery is no longer one of the
channels claude-plugin-release publishes on every release.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@travist
travist merged commit d62d076 into main Oct 30, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant