v0.3.4
v0.3.4
Documentation-only patch release. No runtime, source, detector, storage,
controller, projection, MCP-surface, or release-engineering change versus
v0.3.3. The npm package remains @geanatz/curion and the Trusted
Publishing / provenance path is unchanged.
What this release does
- Fixes npm README documentation links. The v0.3.3 README shipped
to the npm registry with relativedocs/*.mdlinks that 404 on
npmjs.org because thedocs/directory is not included in the npm
tarball — onlyREADME.md,LICENSE, and the package contents are.
v0.3.4 re-publishes the README with absolute
https://github.com/geanatz/curion/blob/main/docs/<page>.mdURLs
(with the same fragment anchors the relative links used), so the
"MCP client setup", "Configuration", "API reference", and
"Privacy & storage" links from the README resolve correctly when the
README is read from the npm registry. The docs/ pages themselves,
the install command, the MCP server identity, and the public API
surface are unchanged. - No stale references re-introduced. No
v0.2.0 is taggedframing,
nogpt-5.5model placeholder, no unscopednpm install curion
install line. The npm README and the GitHub README continue to match.
Install
npm install -g @geanatz/curionThe curion binary on PATH is the MCP stdio server entrypoint. Always
start it through an MCP client that manages the stdio transport.
Publishing
Published to npm with provenance attestation via Trusted Publishing
(OIDC) — no long-lived NPM_TOKEN secret is read or required. Verify
the attestation with npm audit signatures or the npm registry's
"Provenance" panel on the package page.
See CHANGELOG.md for the full v0.3.4 section.