Repository navigation
v0.13.0
No runtime changes.
Changed
release.shwaits for npm to serve the version before publishing to the
MCP Registry.npm publishreturns when the registry accepts the tarball,
but the version is not yet readable from npm's CDN-backed read path, and the
MCP Registry validates by reading it -- so the registry step could fail with
version 'x.y.z' was not found (status: 404)and need a re-run. The wait
polls the exact URL the registry's validator fetches withcurl(not
npm view, whose metadata cache can outlast the condition), warns rather
than fails on timeout somcp-publisherstill reports its own error, and
can be skipped withSKIP_NPM_WAIT=1or retuned withNPM_WAIT_TIMEOUT_S
(#45).- README: the X follow badge moved from the top of the page to the bottom, so
the description leads on npm and GitHub (#46).
Documentation
- The README's per-tool gating list covers every tool.
pg_io_stats,
pg_seq_scan_tablesandpg_index_advisorwere in neither authority class;
all three are annotated read-only and join Auto-allow.pg_explainmoves to
Always prompt, where itsdestructiveHint: trueannotation already put it:
the old "without ANALYZE-of-write" condition depended on a call argument that
no per-tool toggle can see. Thepg_queryentry now says writes also need
ALLOW_WRITES=1, the duplicatepg_list_rolesentry is gone, and the
ALLOW_WRITESconfiguration row namespg_kill, which it also gates (#34). - The
EXPLAIN ANALYZErollback is described precisely: the written rows do
not persist, but a sequence the statement advanced stays advanced.