Bump noyalib from 0.0.44 to 0.0.45

[dependabot]

Bumps noyalib from 0.0.44 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

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
• See full diff 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: df1a7ea6-fba4-4faf-9531-c5f646ac576f

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 68f4b45fbdfcfdcc6fb6dfa8fc779279b121eb34

Assessed noyalib 0.0.44 → 0.0.45 against the comparison base, tagged upstream changes, and published source. No additional patch is needed: the fixes affect APIs bitcoinvert does not use, and its exact-decimal configuration parsing remains appropriate. All six configured checks passed, including 60 tests and the security audit. The input snapshot is unchanged; retain the Dependabot update as proposed.

Findings:

• Scope: this is a single-package repository. Only Cargo.toml and Cargo.lock differ from the comparison base; noyalib is the sole changed locked package. Its downloaded archive checksum matches Cargo.lock and the release checksum.
• Usage: src/defaults.rs calls from_str_with_config with no_schema(true), preserving legacy unquoted decimal lexemes for Amount without conversion through f64. The existing setting remains necessary and supported. Existing tests exercise exact numeric, quoted and scientific amounts, rejected invalid values, dependency-generated YAML round-tripping, and ordered JSON with exact decimal strings. Source: https://github.com/sebastienrousseau/noyalib/blob/v0.0.45/crates/noyalib/src/de/config.rs
• The release fixes leading-comment ownership, CST fragment containment and sibling-shape checks, borrowed-reader !!str handling, and parser-toggle propagation through Spanned. Bitcoinvert uses none of those APIs. No relevant API removal, changed default, or new replacement for its existing parsing approach was found. Sources: https://github.com/sebastienrousseau/noyalib/blob/v0.0.45/CHANGELOG.md and sebastienrousseau/noyalib@v0.0.44...v0.0.45
• Compatibility: default features remain disabled with std enabled. The optional ariadne 0.6 and garde 0.23 adapters are unused; upstream development dependency updates do not change this project's lockfile. The embedded no_std target clarification does not apply to this CLI. Noyalib's unchanged Rust minimum of 1.86.0 is below bitcoinvert's declared 1.95.0. Source: https://github.com/sebastienrousseau/noyalib/blob/v0.0.45/crates/noyalib/Cargo.toml
• No source changes or additional tests were justified by this version interval. Configuration writing through home-config remains unchanged; replacing that separate dependency path would exceed this upgrade's scope.
• Validation used Rust 1.98.1; Rust 1.95.0 and the separate nightly unused-dependency CI job were not rerun. Two direct source-download attempts were blocked by sandbox address restrictions, but tagged upstream evidence and Cargo's checksum-verified package source were subsequently available through unchanged routing. Delegation was unavailable because the agent service could not locate this session.

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