# Reported issues for SysKnife Pod holds 7 of 7 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user. Back to [SysKnife](/mcp/sysknife). ## Most discussed ### Post-release manual steps for v0.9.1 `v0.9.1` is published to npm, crates.io, GitHub Releases and the official MCP Registry. One directory listing still points at the previous version and cannot be updated from CI. ### Glama build spec Browser-only: Replace **Build steps** with the following, leave every other field alone (in particular keep the `mcp-proxy --` prefix in CMD arguments, which is how Glama exposes a stdio server), then click **Build & Release**: [Read the thread](https://github.com/lacs-project/sysknife/issues/288) · 2026-08-24 · closed · external user · 1 comment ### Post-release manual steps for v0.8.0 `v0.8.0` is published to npm, crates.io, GitHub Releases and the official MCP Registry. One directory listing still points at the previous version and cannot be updated from CI. ### Glama build spec Browser-only: Replace **Build steps** with the following, leave every other field alone (in particular keep the `mcp-proxy --` prefix in CMD arguments, which is how Glama exposes a stdio server), then click **Build & Release**: [Read the thread](https://github.com/lacs-project/sysknife/issues/213) · 2026-08-16 · closed · external user · 1 comment ### Post-release manual steps for v0.7.0 `v0.7.0` is published to npm, crates.io, GitHub Releases and the official MCP Registry. One directory listing still points at the previous version and cannot be updated from CI. ### Glama build spec Browser-only: Replace **Build steps** with the following, leave every other field alone (in particular keep the `mcp-proxy --` prefix in CMD arguments, which is how Glama exposes a stdio server), then click **Build & Release**: [Read the thread](https://github.com/lacs-project/sysknife/issues/183) · 2026-08-08 · closed · external user · 1 comment ### Post-release manual steps for v0.6.0 `v0.6.0` is published to npm, crates.io, GitHub Releases and the official MCP Registry. One directory listing still points at the previous version and cannot be updated from CI. ### Glama build spec Browser-only: Replace **Build steps** with the following, leave every other field alone (in particular keep the `mcp-proxy --` prefix in CMD arguments, which is how Glama exposes a stdio server), then click **Build & Release**: [Read the thread](https://github.com/lacs-project/sysknife/issues/167) · 2026-07-31 · closed · external user · 1 comment ### Post-release manual steps for v0.5.0 `v0.5.0` is published to npm, crates.io, GitHub Releases and the official MCP Registry. One directory listing still points at the previous version and cannot be updated from CI. ### Glama build spec Browser-only: Replace **Build steps** with the following, leave every other field alone (in particular keep the `mcp-proxy --` prefix in CMD arguments, which is how Glama exposes a stdio server), then click **Build & Release**: [Read the thread](https://github.com/lacs-project/sysknife/issues/157) · 2026-07-31 · closed · external user · 1 comment ### Post-release manual steps for v0.3.0 `v0.3.0` is published to npm, crates.io, and GitHub Releases. Two directory listings still point at the previous version, and neither can be updated from CI. ### 1. Official MCP Registry `server.json` already names `sysknife-cli@0.3.0`. The validator reads the **published** crate's rendered README for the `mcp-name:` marker, so this step only works now that crates.io has the version. ```sh mcp-publisher login github # device code, cannot run unattended mcp-publisher publish # from th [Read the thread](https://github.com/lacs-project/sysknife/issues/135) · 2026-07-29 · closed · external user · 1 comment ### Post-release manual steps for v0.2.16 `v0.2.16` is published to npm, crates.io, and GitHub Releases. Two directory listings still point at the previous version, and neither can be updated from CI. ### 1. Official MCP Registry `server.json` already names `sysknife-cli@0.2.16`. The validator reads the **published** crate's rendered README for the `mcp-name:` marker, so this step only works now that crates.io has the version. ```sh mcp-publisher login github # device code, cannot run unattended mcp-publisher publish # from [Read the thread](https://github.com/lacs-project/sysknife/issues/125) · 2026-07-28 · closed · external user · 1 comment ## Most recent The remaining reports are on [the project's issue tracker](https://github.com/lacs-project/sysknife/issues).