Skip to content

v0.13.0

Choose a tag to compare

@jeffyaw jeffyaw released this 14 Sep 03:57
· 51 commits to main since this release
v0.13.0
bb10827

No runtime changes.

Changed

  • release.sh waits for npm to serve the version before publishing to the
    MCP Registry.
    npm publish returns 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 with curl (not
    npm view, whose metadata cache can outlast the condition), warns rather
    than fails on timeout so mcp-publisher still reports its own error, and
    can be skipped with SKIP_NPM_WAIT=1 or retuned with NPM_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_tables and pg_index_advisor were in neither authority class;
    all three are annotated read-only and join Auto-allow. pg_explain moves to
    Always prompt, where its destructiveHint: true annotation already put it:
    the old "without ANALYZE-of-write" condition depended on a call argument that
    no per-tool toggle can see. The pg_query entry now says writes also need
    ALLOW_WRITES=1, the duplicate pg_list_roles entry is gone, and the
    ALLOW_WRITES configuration row names pg_kill, which it also gates (#34).
  • The EXPLAIN ANALYZE rollback is described precisely: the written rows do
    not persist, but a sequence the statement advanced stays advanced.