Repository navigation
ci: stop publishing to Smithery, which shuts down on October 31 - #116
Merged
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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/ai1.1.0 release (run 41093812513) with403 {"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 itsSMITHERY_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.mcpbvariant existed only to pass Smithery's manifest validation.smithery.yaml: removed.remove-smithery-publish: Smithery is no longer one of the channelsclaude-plugin-releasepublishes 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.mdships in the npm package, sopnpm check:releaseswould require an@formio/mcprelease to change it; it can go with the next one.No published package changes, so there is no changeset.
Tests
release-channels.test.ts: the workflow has no Smithery step and reads no Smithery credential.mcpb-build.test.ts1.12: the build producesformio-mcp.mcpband no Smithery variant (replaces the test that checked the variant).packages/mcp-server: 1939 passing.packages/skill-tests: 1669 passing.pnpm check:releases --base=origin/main: passes.After merging, the
SMITHERY_API_KEYrepository secret can be deleted.🤖 Generated with Claude Code