All notable changes to lima are documented in this file.
The format follows Keep a Changelog. This crate's version number tracks its own release history and is independent of the Lima specification version — Lima Core 1.0 and Lima References 1.0 are both frozen regardless of what this file shows.
First independent whole-repo review of Lima, then a second review of the
consolidated result. Nine rounds of Core 1.0 errata (1.0.1–1.0.9) and
a cross-implementation rework of References 2.0 error positions, all
fixing behaviour the specifications already required. The crate version
advances to 0.4.0 to align with the TypeScript package and Go module.
The Lima Core 1.0 and References 2.0 specification texts gain only
non-normative clarifications (§5, §5.2, §6.1.3, error-api); no rule
changed.
The shared conformance corpus grows to 211 Core and 136 References 2.0
cases (from 149 / 119). The frozen 1.0.0 baseline of 149 Core cases is
byte-identical; every added case carries a since revision marker.
- An unquoted key must now match the Core §5.1 grammar
(
[A-Za-z0-9_][A-Za-z0-9_:-]*) in every mapping context — top level, nested, and flow. Keys such asa.b,($x),${x}, or a key with a leading non-ASCII space are no longer recognised; the line or item is skipped in both modes. (errata 1.0.5) parse_corecomputes a value's source column only on the positioned path, restoring its hot path.
|literal block scalars: recognised under a nested key, not only at the top level; the scalar ends at the first line indented to the key's column or less; indentation trimming removes exactly the smallest common indent. (errata 1.0.1)- Quoted-string lexing is escape-aware in every value position:
"a\""and'a\''are unterminated in flow and block contexts;"a: b": vparses as a single key; an unquoted key with interior whitespace makes its line or item unrecognised in nested and flow mappings. (errata 1.0.2) - A comment line between a bare key and its nested block no longer drops the block. (errata 1.0.3)
- A block-sequence item's first bare key now aligns following sibling keys at the key's own column, not the dash column. (errata 1.0.6)
- U+2028 / U+2029 are ordinary quoted-key characters (Core §15.6 excludes only U+000A); Rust already accepted them, TypeScript now does too. (errata 1.0.9)
\#is collapsed to#only in unquoted values (Core §6.1.4). Inside"..."it is now an unknown escape (non-strict keeps the backslash, strict throwsINVALID_ESCAPE); inside'...'a literal backslash. (errata 1.0.9)- The whitespace between a value and a trailing
#comment is stripped with the project whitespace set (is_trim_whitespace), not Rust'sstr::trim_end(char::is_whitespace) — so a U+FEFF before a comment is now trimmed and a U+0085 is now kept as content, matching TypeScript and Go. (errata 1.0.9) - References 2.0 error positions:
lineandcolumnare the physical position in the original source text, counted in Unicode code points and identical across the TypeScript, Rust, and Go implementations. Leading-tab expansion and\#escapes no longer shift a later token's reported column — including inside a flow[...]/{...}. A block-sequence continuation-key value's raw anchor now uses the project whitespace boundary, not Rust's, matching the other implementations. - References 2.0 diagnostic ordering: an unresolved-reference or structural error is attributed to the earliest participating source token, including across flow-collection elements on one line and across a second pure-reference copy.
parse_corecarries a ~10–20% regression from the §5.1 per-key validation and the physical-position token scan, accepted as the cost of spec conformance. Realistic frontmatter still parses several times faster thanyaml-rust2.
- Full Lima References 2.0 support: dotted document and partial paths, transitive three-edge resolution, cycle handling, structural copies, canonical interpolation, ordered diagnostics, and final resource checks.
- Primary
parse(input, ParseOptions)entry point andParseMode. - Options-based Core parsing with duplicate-key warning callbacks.
- Structured reference diagnostic fields and References 2.0 benchmarks.
parse_referencesis now a deprecated alias forparseand has References 2.0 semantics. References 1.0 tokens are literal text.parse_coreacceptsCoreOptions;boolremains supported through a compatibility conversion.- Warning collection and duplicate-key lookup are bypassed entirely when no callback is supplied, preserving the Core hot path.
- The crate version advances to 0.3.0 to align with the TypeScript 0.3.x release line.
- The conformance test pins and executes all 369 shared cases: 149 Core, 101 References 1.0, and 119 References 2.0.
Initial release. (0.1.0 was reserved on crates.io as a placeholder with no working implementation; this is the first version with real content.)
parse_core(input, strict)— Lima Core 1.0 only, no reference resolution.parse_references(input, options)— Core plus the References 1.0 extension (($key)document references,(%key)external partials).- Zero runtime dependencies.
- Verified against the shared, implementation-independent conformance
corpus (250 cases as of this release; count pinned by
tests/corpus.rs) — seedocs/guide.mdanddocs/corpus-design/.