Pin the tested ExMCP fork without enabling MCP #1599
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/mcp-bandit-dependency"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Pin sean/ex_mcp commit 2bbb22baf398f05b7f1d20b03a6225f674ab3d86 from sean/ex_mcp#1. Cowboy is optional; the resolved dependency graph has no Cowboy/Cowlib/Ranch. ExMCP is packaged with load-only startup and runtime:false so its default in-memory services do not start. No endpoint is exposed.
Add exact-pin and banned-package checks to the normal contract suite. Check packaged applications in make release and both container release architectures. Record maintenance requirements and pending MCP work in docs/mcp-dependency.md.
Validation: red dependency contract before the pin; green after. Full make check passed, including 2258 existing ExUnit tests and PostgreSQL integration. make release, clean audit without exceptions, format check, and release dependency checks passed. Inspected the release boot script: Binjovi API starts, ExMCP does not.
This removes the dependency blocker. Ory sign-in, durable MCP sessions, tool projections, commands, and watches remain separate implementation work. Forgejo Actions is disabled on the fork; its weekly workflow is not yet active.
Pull request closed