Release v0.7.0 — aspark-graph on PyPI · a-lottes/aSPARK-graph

aspark-graph 0.7.0 — now on PyPI

Install aspark-graph in one command, straight from PyPI. You no longer have to clone the repository and run a sync to use the tool. pip install aspark-graph puts the aspark-graph command on your PATH, and uvx aspark-graph serve launches the MCP server with no checkout at all — which is exactly how an agent is meant to start it. Both the command-line queries and the MCP server run from the published package.
The README now explains the determinism promise — and its limits. It says plainly why the language grammars are pinned to exact versions and that the lockfile is part of the deal, so a graph you build rebuilds byte-for-byte on an unchanged repository. It is equally plain about the boundary: that promise holds for a fixed set of grammars, and upgrading a grammar can change what gets extracted — so a grammar upgrade is always a deliberate, changelog-noted, version-bumped event, never a silent shift under your feet.

The install instructions describe the working published path — and only that. The README leads with the one-command PyPI install; the "add as an MCP server" instructions use uvx aspark-graph serve instead of pointing at a local checkout. The from-source route (clone → sync → build) is kept for contributors under a Development heading. The old "not yet published to a package index" note is gone, and nothing in the README or CLAUDE.md still claims the tool is install-from-source only.
The package page renders cleanly on PyPI. The logo and the in-README links (to the security policy and the integration guide) now use absolute addresses, so the project page on pypi.org shows the same images and working links you see on GitHub rather than broken thumbnails and dead links.

N/A user-facing — this release changes no tool behaviour. Every query, argument, output shape and exit code is identical to 0.6.0; this cycle is distribution and documentation only. (A packaging-hygiene issue — untracked local files reachable in the built sdist — was found and fixed during this release's own preparation, before anything was published; see .spark/pypi-publish/plan.md's Deviations section.)