Bump noyalib from 0.0.32 to 0.0.39

[dependabot]

Bumps noyalib from 0.0.32 to 0.0.39.

Release notes

Sourced from noyalib's releases.

noyalib v0.0.39

What's Changed

• test(spec-torture): five documents that separate the implementations (870cb75)
• fix(parallel,loader): document boundaries, cycles and YAML 1.1 integers (7c02351)

Checksums

9df43acfb5d16214a4f78e184707822141edfcd430a38a58ceb40067ba521290  ./noyalib-0.0.39.crate

noyalib v0.0.38

What's Changed

• chore(codespell): the ultra-complex fixture is verbatim input, not prose (fdc9e84)
• feat(parser,cst): the ultra-complex fixture, two diagnostics that name the mistake, formatter fixes (369c14a)
• ci(drift-net): read the entry's imports with a while loop (SC2013) (f369315)
• chore(release): date the v0.0.38 CHANGELOG heading (4d2f3a6)
• chore(version): the branch carries 0.0.38 from the start (ba9d824)

Checksums

6ff9fd27debdd6956b4378b45745cbf8a1dd7bec8e105abd3035b4a7a1d35968  ./noyalib-0.0.38.crate

noyalib v0.0.37

What's Changed

• chore(release): date the v0.0.37 CHANGELOG heading (a9bc6e1)
• chore(version): the branch carries 0.0.37 from the start (2ee0059)

Checksums

a34cd8430232bb95a20123f8436824f20a724facdcbd1e5d3e21b9c7e4e5fc82  ./noyalib-0.0.37.crate

noyalib v0.0.36

What's Changed

• chore(release): date the v0.0.36 CHANGELOG heading (baa7c29)
• fix(cst): a ... that closes nothing is not a document (b08d693)
• fix(parser): one tab rule and one block-scalar rule for every document in a stream (43d4034)
• deps(cargo): jsonschema 0.53.0 for real: the manifest requirement moves with the lock (8065472)
• deps(cargo): bump jsonschema to 0.53.0 (dependabot #405), vet exemptions refreshed (15dc8ef)
• fix(error): gate relocate on std, the stream parser is its only caller (c7c1e5e)
• fix(cst): locate stream parse errors in the stream, not the failing document (0138b27)
• chore(version): the branch carries 0.0.36 from the start (3626ad6)

Checksums

</tr></table> 

... (truncated)

Changelog

Sourced from noyalib's changelog.

[v0.0.39] - 2026-09-07

Fixed

• parallel::values counted one document too many for any stream that opened with a comment, a blank line or a directive: the splitter treated that prologue as a document of its own, so the parallel path disagreed with load_all. The prologue now stays with the document its --- opens. A property test holds the two paths to the same answer across every file of the official test suite.
• A self-referential anchor said the wrong thing. An alias pointing at an anchor whose value is still being built was reported as an unknown anchor defined "in an earlier document". It now says that the alias points at an anchor still being defined and that a self-referential node cannot be represented as a tree, which is the actual limit: YAML's representation graph may be cyclic, a Value is a tree.
• !!int on a YAML 1.1 spelling now says which one and what to write. !!int 0b101010 answers "YAML 1.2 has no binary literal, 0b was YAML 1.1; write 42", and !!int 100_000_000 names the digit separator and gives 100000000.

Added

• Twenty documents that each stress one corner of the specification (tests/fixtures/spec-torture/), with every expectation cross-checked against libyaml and go-yaml: complex keys with all three chomping indicators and an explicit indentation indicator; a merge lattice with !!binary, !!timestamp, hexadecimal and octal integers; !!set, !!omap and !!pairs together; graph recursion and anchor shadowing; a multi-line flow key that every implementation refuses; custom local tags with infinities and NaN; the null boundary shapes; %TAG shorthand resolution; zero-indent nested sequences; a sequence of mappings and a mapping holding a block scalar used as keys; four-byte emoji, a Japanese key and a zero-width space in a key; tag and anchor in either order; an anchored block-scalar key aliased as a value; plain-scalar folding; and empty documents around a real one. Five of them separate the implementations: a billion-laughs payload that the alias budget refuses in under a second, where libyaml exhausts memory and go-yaml does not finish inside a minute; the Norway problem, where NO, no, off, y and 190:20:30 all stay strings under YAML 1.2's core schema while libyaml still resolves them the 1.1 way; a block scalar opened inside a flow collection, which every implementation refuses; colons inside plain scalars; and a four-line plain scalar used as an explicit key.

[v0.0.38] - 2026-09-06

Added

... (truncated)

Commits

• 1d3c613 Merge pull request #414 from sebastienrousseau/feat/v0.0.39
• 870cb75 test(spec-torture): five documents that separate the implementations
• 7c02351 fix(parallel,loader): document boundaries, cycles and YAML 1.1 integers
• f581128 Merge pull request #413 from sebastienrousseau/feat/v0.0.38
• fdc9e84 chore(codespell): the ultra-complex fixture is verbatim input, not prose
• 369c14a feat(parser,cst): the ultra-complex fixture, two diagnostics that name the mi...
• f369315 ci(drift-net): read the entry's imports with a while loop (SC2013)
• 4d2f3a6 chore(release): date the v0.0.38 CHANGELOG heading
• ba9d824 chore(version): the branch carries 0.0.38 from the start
• 5f4bb01 Merge pull request #412 from sebastienrousseau/feat/v0.0.37
• 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: e4420acd-5361-4e8d-8c2f-6e60a0165733

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.}