Release notes
Per-release narrative notes, newest first. One file per tag, named
exactly for the tag it documents — v0.0.17.md is v0.0.17 — so a
version is enough to find its notes without consulting this index.
These complement CHANGELOG.md rather than
duplicating it. The changelog is the complete, structured record of every
release under Keep a Changelog;
these files carry the narrative for the releases that had one — why a
change was made, what it broke, what to do about it.
Notes exist for v0.0.1 – v0.0.17. From v0.0.18 to v0.0.53 the changelog entries carry that narrative themselves, so there are no separate files; see the changelog for those releases.
From v0.0.54 onward every release has a file again, in a fixed shape:
it opens with the ## Highlights ⭐️ bullets the GitHub release page is
composed from at release time (the rest of the page, What’s Changed,
Checksums and the Full Changelog link, is generated). The release workflow
refuses a tag whose Highlights file is missing, and
scripts/verify-release-versions.sh checks for it before that.
| Version | Date | Notes |
|---|---|---|
v0.0.55 | unreleased | Security hardening from the v0.0.54 family audit. |
v0.0.54 | 2026-10-07 | Reader entry points bounded at max_document_length before buffering. |
v0.0.17 | 2026-07-25 | Lockstep-only release; no code change in the core crate. |
v0.0.16 | 2026-07-24 | Build fix, MSRV raise, and dependency refresh — main had been left unbuildable under cargo check --all-targets. |
v0.0.15 | 2026-07-12 | Completes loader parity and hardens coverage. |
v0.0.14 | 2026-07-09 | The loader-parity cut; closes a fast-path silent-collapse bug. |
v0.0.13 | 2026-07-05 | Splits noyalib-mcp, noyalib-lsp and noya-cli into their own repositories. |
v0.0.12 | 2026-07-03 | The workspace-split pilot; noyalib-wasm leaves the monorepo first. |
v0.0.11 | 2026-07-01 | CI-integrity housekeeping. |
v0.0.10 | 2026-06-30 | Scanner correctness for UTF-8 BOM-prefixed multi-node documents. |
v0.0.9 | unreleased | Supply-chain refresh batching eight Dependabot updates. Never tagged. |
v0.0.8 | 2026-06-17 | The FlowStyle fix. |
v0.0.7 | 2026-06-02 | Supply-chain hardening. |
v0.0.6 | 2026-05-30 | Ecosystem integration — the four remaining v0.0.6 milestone issues. |
v0.0.5 | 2026-05-11 | Polish and stabilisation: edition 2024 and MSRV 1.85. |
v0.0.4 | 2026-05-11 | Opens the v0.0.4 cycle with the !include directive. |
v0.0.3 | 2026-05-11 | Surgical patch widening the rustc-hash dependency range. |
v0.0.2 | 2026-05-10 | Zero-copy borrowed deserialisation and lazy parsing. |
v0.0.1 | 2026-05-10 | First publishable release — a pure-Rust YAML 1.2 implementation with full serde integration. |
Conventions
- Filename equals tag.
docs/release-notes/<tag>.md. The mapping is one-to-one with git tags and GitHub releases, so a link can be constructed from a version alone. - Notes are immutable. A published file records what was true at that release. Corrections belong in a later release’s notes or in the changelog, not in edits to history.
- The changelog is the index of record. Every release appears there; only some have a narrative file here.
v0.0.9was never tagged. Its notes are kept for continuity of the record; the published sequence goesv0.0.8→v0.0.10.