Devotd Github
NewModel Context Protocol

praket7/hotload-mcp 0.3.2 — version bump for retrying the npm release

The gateway hotload-mcp, which hot-reloads child MCP servers, bumped its version to 0.3.2 and retried the npm release.

Repositorypraket7/hotload-mcp ↗

The gateway hotload-mcp, which hot-reloads child MCP servers, bumped its version to 0.3.2 and retried the npm release.

GitHub description: A stable MCP gateway for hot-reloading child MCP servers in Codex

stars
★ 2
Forks
0
Language
TypeScript
License
NOASSERTION
Read original source ↗View on GitHub ↗

praket7/hotload-mcp is a gateway that runs MCP (Model Context Protocol) servers as child processes and, when the configuration changes, reloads only the individual servers instead of restarting the gateway as a whole. The commit 7d37a07 of October 16, 2026 raised the version from 0.3.1 to 0.3.2, and it touched only two files, package.json and package-lock.json, with 3 insertions and 3 deletions. The commit message 'chore: retry npm release as 0.3.2' shows that the purpose of this change was to retry the npm release.

The use case of this project is the MCP server development loop. The core feature of this repository is being able to swap out only the child servers when you change server code, without having to take the gateway down and bring it back up. The dependencies are @modelcontextprotocol/client and @modelcontextprotocol/server, each pinned at ^2.0.0. This patch contains no code that changes server behavior; only the version strings in the manifest and the lockfile were aligned to 0.3.2.

However, since the commit message explicitly says 'retry', it reads as though the preceding npm release attempt did not complete as-is. Even so, this commit record contains no information on whether the release succeeded, no release log, no functional differences between 0.3.1 and 0.3.2, and no indicators such as license or star count. So this change is closer to a packaging-type commit that only bumps the version without any functional fix. Whether 0.3.2 actually landed on npm can only be known by checking the registry state separately.