build(deps): bump noyalib from 0.0.18 to 0.0.23

[dependabot]

Bumps noyalib from 0.0.18 to 0.0.23.

Release notes

Sourced from noyalib's releases.

noyalib v0.0.23

What's Changed

• fix(docs): repair two doc defects in the reorder change (0984039)
• fix(cst): reorder moves the entry, not the value bytes (#269) (d397330)
• feat(cst): remove flow members and sole entries — closes #221 (b208c50)
• ci(miri): run the full Miri sweep weekly instead of nightly (6ecd133)
• ci: compare like with like in the duration monitor — filter by event (1573f2c)
• ci(miri): install the cross toolchain before the native sweep, not after (7fe277a)
• ci(miri): use an if-statement for the sysroot assertion (3ef3b88)
• ci(miri): install the mips64 libc headers too, and widen the job budget (1646d08)
• ci: send a User-Agent to crates.io, and stop mislabelling 403 as a network fault (2a9c46f)
• ci: fix the two failing scheduled monitors (f6a5074)

Checksums

f960f72c3b4e3e1e89fa89c5ef62ec3cb44f4509e3e1871b8d24336b978c2cc7  noyalib-0.0.23.crate

noyalib v0.0.22

What's Changed

• docs(changelog): cut the v0.0.22 release section (5122e42)
• chore(release): bump to v0.0.22 (7601ced)
• fix(cst): splices adopt the document's line break instead of assuming \n (0e647db)

Checksums

213c922c1762f1e25cdd85773b2a7968b96e5b88058265733a847e2be3b589ce  noyalib-0.0.22.crate

noyalib v0.0.21

Changes since v0.0.19 (2026-08-11).

Note on versioning. 0.0.20 was merged to main but never tagged, so it never reached crates.io. Its bare-metal no_std work ships here. The published sequence is 0.0.19 → 0.0.21.

---

Three silent-corruption fixes

Each of these returned Ok while damaging the document. None were reported — they were found by probing the behaviour the roadmap claimed, and in one case by a property test written in the same branch.

remove deleted more than it was asked to

| input | call | before |

... (truncated)

Changelog

Sourced from noyalib's changelog.

[v0.0.23] - 2026-08-16

Added

• Document::remove now covers flow members and sole entries (#221, sub-ask 4 — completes the issue). Both classes previously refused. The refusals were correct at the time: v0.0.21 turned them from silent data loss into errors, because a flow member shares its line with its siblings and its parent, so "delete the line" deleted the parent — and for a one-entry document, the document.

  • Flow members. a: {x: 1, y: 2} → remove("a.x") → a: {y: 2}; a: [1, 2, 3] → remove("a[1]") → a: [1, 3]. The member's own span is spliced along with exactly one separator: the comma after it, or — for the last member — the comma before it, so neither {, y: 2} nor {x: 1, } can result. A separator parked on another line is deliberately not matched; a multi-line flow collection refuses rather than splicing bytes it cannot account for.

  • Sole entries. Removing the last entry of a collection now writes that collection out explicitly — a:\n x: 1 becomes a:\n {}, a sole sequence item leaves [], and a single-key document becomes {}. Deleting the bytes alone would leave a dangling a:, which re-parses as null: a type change, not a removal.

  The document's trailing newline survives the rewrite. A collection's span can run to the end of its last line, so overwriting that range wholesale would take the final newline with it — harmless to a parser, but this is a lossless CST, where a vanished trailing newline is a whole-file diff and a failing end-of-file check.

  remove_subtree was not added. The issue offered it as an alternative to extending remove, and extending remove is the path that was taken, so a second entry point would be a synonym rather than a capability.

Changed

• swap_items / move_item exchange whole entries, not value bytes (#269). An item now moves with the lines it owns — its head-comment run included — which is the same range remove deletes (owned_entry_range). Previously only the two value spans moved, so every comment stayed with the slot: swapping - one # first and - two # second produced - two # first, and a # about one header stayed above index 0 while the item it described moved away. At Ok, and invisible to the typed oracle, which compares values and cannot see a comment.

  This is a behaviour change, not a bug fix: the old semantics were deliberate and tested (swap_preserves_inline_comment_position, "the

... (truncated)

Commits

• ed8d74f Merge pull request #271 from sebastienrousseau/feat/v0.0.23
• 0984039 fix(docs): repair two doc defects in the reorder change
• d397330 fix(cst): reorder moves the entry, not the value bytes (#269)
• 47ee84f Merge pull request #268 from sebastienrousseau/feat/v0.0.23
• b208c50 feat(cst): remove flow members and sole entries — closes #221
• fd8ef2e Merge pull request #267 from sebastienrousseau/ci/miri-weekly
• 6ecd133 ci(miri): run the full Miri sweep weekly instead of nightly
• eaae6f7 Merge pull request #266 from sebastienrousseau/fix/duration-monitor-event-filter
• 1573f2c ci: compare like with like in the duration monitor — filter by event
• 9bf7832 Merge pull request #265 from sebastienrousseau/ci/miri-install-toolchain-first
• 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)

[dependabot]

Labels

The following labels could not be found: rust. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[dependabot]

Looks like noyalib is up-to-date now, so this is no longer needed.