Bump noyalib from 0.0.43 to 0.0.44

[dependabot]

Bumps noyalib from 0.0.43 to 0.0.44.

Release notes

Sourced from noyalib's releases.

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

Changelog

Sourced from noyalib's changelog.

[v0.0.44] - 2026-09-16

Fixed

• A formatting wrapper around a struct moved the struct's fields up a level. SpaceAfter, Commented, and a FlowSeq/FlowMap/LitStr/ FoldStr holding a shape other than the one it names all fall back to ordinary block output. The serializer's layout decision did not look through them: it treated every __noya_ wrapper as inline, so the key was written wrapped: and the block mapping that followed started at the parent's column.

  # was — `wrapped` is null and `k` is a sibling of `head`
  head: 0
  wrapped:
  k: 3
  tail: 9

  The result is valid YAML that means something else, so nothing failed loudly. SpaceAfter and Commented around a struct are ordinary usage, not a misuse of the wrapper. needs_block_layout now predicts, per tag, what the writer will actually emit.

• SpaceAfter emitted no blank line. It is documented as "emit a blank line after the value" and wrote a single newline, which start_line then absorbed when it opened the next entry — so between mapping entries and between sequence items, which is the whole point of the wrapper, it did nothing. Its only test serialized it at the document root, where a bare value produces the same bytes, so the test passed either way.

• A comment beside an entry with no value was invisible. An entry written k: with nothing after it is an implicit null: a real entry with a key token of its own, which write_span has resolved since #310/#311 so that set_value can fill it in. The comment API asked for the value's span instead, so a # todo sitting right beside the entry was not reported by comments_at, both setters refused it, and both removers reported success having done nothing. All four now work, at any depth and at end of input, keeping whatever gutter the author wrote. An empty sequence item is deliberately unchanged, because no implementation has a usable answer there (#425).

• A new key was inserted below a comment that belonged to the document, not to the entry above it (#418, a regression in v0.0.25).

  a:
    b:

... (truncated)

Commits

• 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
• 21d6a62 Merge pull request #427 from zoosky/fix/insert-anchor-skips-trailing-comments
• 96c7cdb Merge main into feat/comments-on-an-entry-with-no-value
• 1592456 Merge branch 'main' into fix/insert-anchor-skips-trailing-comments
• 375eb1f Merge pull request #424 from zoosky/fix/set-value-block-collection-to-scalar
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 67553ce4-2857-46d5-810c-d285891390b9

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[gcomte]

Dependency upgrade assessment — commit 72d53f6944afaa9ddb111420c1607f2599e38ea3

Reviewed noyalib 0.0.43 → 0.0.44 against the comparison base and version-specific upstream source. No additional edits are needed: the applicable parser fix works through bitcoinvert’s existing API, and all six requested checks passed. Keep the proposed upgrade as-is; the workspace is unchanged.

Findings:

• Scope: one Cargo package, no workspaces or transitive version changes. Only noyalib’s manifest version and lockfile version/checksum changed. Both downloaded crate checksums match their respective lockfiles.
• Applicable fix: tabs before comment-only lines now parse consistently after quoted scalars. A temporary CLI check confirmed exact amounts and ordered outputs for plain, quoted, and scientific-notation defaults. Source: https://github.com/sebastienrousseau/noyalib/blob/v0.0.44/src/parser/scanner.rs
• src/defaults.rs uses ParserConfig::no_schema(true) and from_str_with_config. These APIs remain supported and unchanged; schema-free parsing remains necessary to preserve legacy decimal lexemes without f64 conversion. Source: https://github.com/sebastienrousseau/noyalib/blob/v0.0.44/src/de/config.rs
• Formatting-wrapper fixes and CST comment, insertion, indentation, and CRLF fixes require no application changes: bitcoinvert uses neither formatting wrappers nor CST mutation APIs. Template creation remains handled by home-config’s serde_yaml serializer. Upstream test, documentation, and CI changes likewise need no adoption. Release notes: https://github.com/sebastienrousseau/noyalib/blob/v0.0.44/CHANGELOG.md
• Upstream jsonschema changes affect an optional feature that is disabled here; yaml-rust2 changes concern upstream development dependencies. noyalib’s Rust minimum remains 1.86, compatible with bitcoinvert’s declared 1.95. Source: https://github.com/sebastienrousseau/noyalib/blob/v0.0.44/Cargo.toml
• Validation used Rust 1.98.1 on Linux. Rust 1.95, other platforms, and the nightly unused-dependency check were not run locally. Subagent delegation was unavailable because the service failed to start an agent; the assessment was completed locally.

The session reported running checks. No independent validation was run for this result.