chore(deps): take yamled 0.0.8

[any-victor]

Takes yamled 0.0.8 and releases ctl-core 0.6.24.

yamled 0.0.8 (victor-software-house/yamled#37) writes one-line text (TextStyle::Line) in the document's quotes instead of keeping a quoted node's old quotes, as yamled's spec requires. A consumer that edits through yamled resolves the version ctl-core pins, so it needs this release to get the fix.

ctl-core uses yamled only to place positions (Document::parse, locate_nearest); 0.0.8 changes only the writer, so ctl-core's behaviour is unchanged. Cargo.lock moves yamled alone.

[kodus-hostinger]

Review

Incremental · 0 open

@kody review after new commits. @kody full re-reads the whole PR.

Summary

Changes in this pass

Dependency bump (Cargo.toml)

• yamled moves from 0.0.7 to 0.0.8.
• The rest of the declaration is unchanged: it is still optional = true with default-features = false. The bump only matters for builds that enable the feature that pulls in yamled, and it adds no new yamled features.
• In Cargo, "0.0.8" is a caret requirement. For a 0.0.x version it resolves to >=0.0.8, <0.0.9, which pins this patch release exactly. Downstream crates that depend on ctl-core and edit YAML through yamled therefore cannot get the 0.0.8 quoting fix until this ctl-core release is published.

Release note (.changeset/yamled-0-0-8.md)

• Adds a patch-level changeset for ctl-core, which produces the 0.6.24 release.
• The note says the new yamled writes one-line text in the document's quotes instead of keeping a quoted node's old quotes. It also says ctl-core's own behavior does not change, because ctl-core only reads positions from yamled and does not write through it.

Review notes

• Wording in the changeset: the first sentence says ctl-core "edits YAML with yamled 0.0.8". The second sentence says ctl-core does not write through yamled. Reworded as "ctl-core depends on yamled 0.0.8…", the note would no longer suggest a behavior change in ctl-core.
• Cargo.lock not in this diff: the description says Cargo.lock moves only yamled, but no lockfile change appears in these patches. Check that the lockfile update is committed, or that the repository does not track one.

Files

File	Status	+	−
.changeset/yamled-0-0-8.md	added	+5	−0
Cargo.toml	modified	+1	−1

Open

No open findings.

History

When	Pass	Open
17 Oct 21:04 UTC	Incremental	0

_{Inspect this review}