Repository navigation
v1.0.9
[1.0.9] — 2026-10-01
Distribution — official MCP Registry, Claude Code plugin marketplace, Homebrew tap, Smithery
- Official MCP Registry publishing is automated — the repo now carries a registry
server.json(io.github.nodesify/astria, stdio transport over the npm package) andrelease.ymlpublishes it viamcp-publisherwith GitHub OIDC after the npm publishes succeed; theverifyjob fails fast whenserver.json's version drifts from the package version. npm packages must declare the matchingmcpNamefor registry validation — added topackages/astria-cli/package.json. The first listing goes live on the next tagged release. - The repository is a Claude Code plugin marketplace —
/plugin marketplace add Nodesify/astriathen/plugin install astria@nodesifyinstalls, in one plugin: the MCP server (the tracked.mcp.json), the graph-first skill (skills/astria/), two slash commands (/astriagraph queries,/astria-riskPR-ready risk report), and anastria-architectsubagent — wired through.claude-plugin/marketplace.json+.claude-plugin/plugin.json. - Homebrew tap —
brew install nodesify/tap/astriainstalls the published npm package; the formula ships in the newNodesify/homebrew-taprepo, with per-release update instructions inpackaging/homebrew/README.md. - Smithery registry config —
smithery.yaml(stdio start command over the published npm package, optionalprojectPath) so smithery.ai lists the server once the repo is connected there. - Discovery metadata — GitHub topics gained
claude-codeandagent-skillsalongside the existingmcp-server/model-context-protocolset.
What's Changed
- Release 1.0.7 — judged semantics, drill-down viewer, scoped retrieval by @erictong0602 in #90
Full Changelog: v1.0.8...v1.0.9