v0.12.1

Every install path works again, and Helm charts join the graph.

v0.12.1 fixes v0.12.0's package installs and the other install paths we found broken while checking every channel. It also links Helm charts to what they deploy, and stops the graph from inventing a registry for container images.

Upgrading? The first index of each existing project after the upgrade is a full rebuild, once (image identities changed; see below).

Fixed: installs

• npm, PyPI and Go installs. npm i, pnpm add, pip install and the Go wrapper could not install v0.12.0 on any platform. Each wrapper refused an archive member above 256 MiB, and every v0.12.0 binary is 331-335 MB. The size limits are gone from all three wrappers. The archive is still verified against the release's checksums.txt before it is unpacked, its contents must be exactly the expected files, and the binary must answer --version. Thank you, @hydroplexus, for the precise report (#2657).
• Homebrew. The formula was still at 0.10.3, and on Linux it installed the dynamically linked build, which needs glibc 2.38 (Ubuntu 22.04, Debian 12 and RHEL 9 do not have it). It now installs the current release, and on Linux the static -portable build that runs on any distribution.
• go install. A pinned go install .../pkg/go/cmd/codebase-memory-mcp@vX.Y.Z never worked, and @latest installed a stale version. Releases now carry pkg/go/vX.Y.Z tags, and the wrapper installs the release matching its own version.
• npm next. The next dist-tag no longer points to an old release candidate; a stable release moves it.
• Docs. winget and Chocolatey were listed as install channels but are not published; they are removed until they are. Windows arm64 builds ship and are now listed.

Install-path smoke tests. Every pull request and every release now installs the npm, PyPI and Go wrappers, the way a user's package manager does, against the real release archives, and runs the binary each one installed. A release is published only after these installs pass, so an installer that cannot install what we ship can no longer reach you.

Helm charts in the graph

A Helm chart used to be an isolated node. Now it links to what it deploys (#2663):

• Chart → objects (DEPLOYS, via: chart): every Kubernetes object rendered from the chart's templates/ (a subchart's objects belong to the subchart).
• values file → Chart (CONFIGURES): values.yaml and values-<x>.yaml beside Chart.yaml.
• Chart → images (DEPLOYS, ref: image): every image its objects name literally (a templated image names none).

HelmRelease → Chart → Deployment → Image is now one traversable path. On 20 infrastructure repositories, charts with no outgoing edge dropped from 238 of 260 to 109, and 2,511 chart-to-object links appeared; every other edge stayed identical.

Images keep the registry the code names

An image without a registry host used to be stored under an invented docker.io/library/... (#2654). Docker Hub is only Docker's default: Podman and CRI-O resolve short names through a search list, mirrors rewrite them, and a local build tag may exist on no registry at all. An image now keeps its name as written, with registry: unknown when no host is stated; a stated host is kept (Docker Hub's spellings become docker.io). FROM nginx and image: docker.io/library/nginx are now two Image nodes. This changes image identities, which is why each project is rebuilt once after the upgrade.

Upgrade notes

• The first index of each existing project after the upgrade is a full rebuild, once.
• Image nodes without a stated registry now carry registry: unknown and the name as written, instead of docker.io/library/....

Security Verification

Every binary published below was scanned by VirusTotal before smoke and soak testing, and the verdict for the exact shipped bytes is linked per product (decisive engines: 61–69).
Every shipped binary was clean.

Selection is tuple-local and defaults to stripped. The selected executable SHA-256 was verified again after packaging; archive containers were not redundantly submitted to VirusTotal. Their hashes remain available in checksums.txt.

Durable evidence: candidate provenance, candidate VirusTotal results, selection decisions.