build(deps): bump noyalib from 0.0.28 to 0.0.45

[dependabot]

Bumps noyalib from 0.0.28 to 0.0.45.

Release notes

Sourced from noyalib's releases.

noyalib v0.0.45

What's Changed

• fix(ci,docs): compile tests with default features, retire the dead xtask commands (#444) (bb63ec5)
• release(v0.0.45): five CST and reader fixes, found by differential testing (#443) (006c013)
• fix(de): carry the parser toggles through Spanned (2329e8b)

Checksums

10912f3af95a00e49a000323539768b9209a5948d76389fc2795c09f4fa6ed7d  ./noyalib-0.0.45.crate

noyalib v0.0.44

What's Changed

• fix(ci): set the coverage floors from the gate's own measurement (be8f0c8)
• fix(ci): gate the compat façade test behind its own feature (848b563)
• fix(v0.0.44): formatting wrappers no longer reparent a struct's fields (ed98016)
• deps(cargo)(deps): bump jsonschema from 0.53.0 to 0.56.0 (#432) (92876e9)
• deps(cargo)(deps): bump indexmap from 2.14.1 to 2.14.2 (#431) (bd441d4)
• deps(cargo)(deps): bump yaml-rust2 from 0.12.0 to 0.13.0 in the yaml-competitors group (#430) (ea53f50)
• fix(ci): unbreak the Kani and CodeQL gates together (#439) (7c6fbb7)
• ci(deps): bump github/codeql-action/analyze from 4.37.9 to 4.38.0 (#435) (c409e7f)
• ci(deps): bump taiki-e/install-action in the rust-toolchain group (#433) (050db8a)
• fix(cst): tab-before-comment consistency (#428) and keep-chomped inserts (#429) (bb79d96)
• perf(cst): bound the header scan to the bytes a header can occupy (4af3592)
• fix(cst): a kept block scalar's blank lines are content, not trivia (8a9a9bd)
• test(cst): cover set_path, the third way into the same anchor (872f2ad)
• fix(cst): an insert stops at the last line its anchor entry owns (d5c32ca)
• feat(cst): comments on an entry written with no value (588a338)
• fix(cst): a scalar written over a block collection keeps its indent (3d6c8b9)
• fix(cst): a replacement adopts the document's line break, like an insertion (0a3b8a4)

Checksums

f307578cc6389d7c00bc284401ee1bff6d47c66c39debd8fc4db5b02892bc7a4  ./noyalib-0.0.44.crate

noyalib v0.0.43

What's Changed

• chore(version): the branch carries 0.0.43 from the start (0d120de)

Checksums

55f03682003f288e23f94d8f6222de0dcf15c77329b5e42b2f37421243c1d373  ./noyalib-0.0.43.crate

noyalib v0.0.42

What's Changed

... (truncated)

Changelog

Sourced from noyalib's changelog.

[v0.0.45] - 2026-09-17

Added

• docs/errors.md — every error variant, the ErrorKind it reports, the stable code() a tool can match on, and what raises it. 32 variants, 11 kinds.

• docs/internals.md — the module map (68 modules) and the twelve longest functions, which are where the time goes and where a change is most likely to cost something.

  Both are generated from the source by scripts/generate-reference-docs.sh, because an inventory maintained by hand is wrong the first time someone adds an item and forgets the document. Generation alone would not be enough — someone can forget to run it — so tests/reference_docs_are_complete.rs reads the source and the documents and fails when they disagree, in both directions: a variant or module missing from a document, and a document naming something that no longer exists. Both documents are compiled by the same CI gate as the rest of docs/.

Changed

• Dependencies brought to their latest releases. ariadne 0.5 → 0.6 and garde 0.22 → 0.23 are major bumps for a 0.x crate; the adapters and their examples were checked to still render and validate identically, not merely to compile. serde-saphyr 1.2 → 1.3, memchr 2.8.2 → 2.8.3, smallvec 1.16.0 → 1.16.1, and the cargo-vet exemptions moved with them.

Fixed

• A leading comment anchored on the value, not the key (#442, thanks @​zoosky). A leading comment decorates the entry, so the line it sits above is the entry's first line — the key's. The comment API measured from the value instead, which is the same line only when the value is a scalar, a flow collection or an implicit null. For a block-valued key the value starts on the next line, so the upward walk began one line too low.

  comments_at("k").before reported [] for a comment sitting directly above k:, contradicting the field's own documented contract, and set_comment(.., Before, ..) spliced the new comment inside the block, where it documented the first child instead.

  Worse, it could claim a comment it did not own: for k:\n # about n\n n: 1\n the walk started inside the block, so # about n was reported as the leading comment of both k and k.n

... (truncated)

Commits

• bb63ec5 fix(ci,docs): compile tests with default features, retire the dead xtask comm...
• 006c013 release(v0.0.45): five CST and reader fixes, found by differential testing (#...
• cf20cbf Merge pull request #441 from sebastienrousseau/fix/spanned-parser-toggles
• 2329e8b fix(de): carry the parser toggles through Spanned
• a2e27e2 Merge pull request #440 from sebastienrousseau/release/v0.0.44
• be8f0c8 fix(ci): set the coverage floors from the gate's own measurement
• 848b563 fix(ci): gate the compat façade test behind its own feature
• ed98016 fix(v0.0.44): formatting wrappers no longer reparent a struct's fields
• 30911d9 Merge pull request #426 from zoosky/feat/comments-on-an-entry-with-no-value
• cc643ee Merge main into feat/comments-on-an-entry-with-no-value
• Additional commits viewable in compare view

[dependabot]

Superseded by #7.