0.7.3

/plugin now sends cache-control: no-cache, so a release reaches hosts
that already installed. The URL is constant and the response carried only
last-modified and an etag, so npm's request cache (~/.npm/_cacache) held
the tarball fresh under heuristic freshness and answered reinstalls without
asking the service. 0.7.2 shipped the opencode fix and stayed invisible:
deleting opencode's package directory reinstalled 0.7.1 from the client cache,
with the endpoint itself serving 0.7.2 the whole time. no-cache means
revalidate, not "do not store" — the etag still answers 304, so an unchanged
bundle costs one conditional request.
Anyone still on a cached 0.7.1/0.7.2 needs one manual clear, since the old
cached response is what decides whether the new one is fetched:
npm cache clean --force, then delete the host's package directory
(opencode: ~/.cache/opencode/packages/https:/<host>/ach-memory/plugin) and
restart it. From 0.7.3 on, a restart is enough.

No service change beyond the header; the release is the plugin.

Navigation Menu