[breaking] chore: update rust dependencies (7 updates) #422

Merged

Wuast94 merged 1 commit from updatarr/rust-dependencies-17605dfeaf into main 2026-10-15 01:42:57 +02:00

Conversation 0 Commits 1 Files changed 2 +44 -44

Wuast94 commented 2026-10-13 11:59:15 +02:00

Owner

• Copy link
• Copy Markdown

Updates rust dependencies.
Breaking change detected. Review the release notes before merging.

Automerge: Disabled because breaking change release notes were detected

Updates

Dependency	From	To	Type	Locations
serde-saphyr	1.3.0	2.0.0	major	Cargo.toml L38
sha2	0.11.0	0.11.1	patch	Cargo.toml L34
tokio	1.53.2	1.53.3	patch	Cargo.toml L21, L61
uv-pep440	0.0.92	0.0.93	patch	Cargo.toml L41
uv-pep508	0.0.92	0.0.93	patch	Cargo.toml L42
wuast-common	1.5.0	1.5.1	patch	Cargo.toml L17
wuast-ui	1.4.0	1.4.1	patch	Cargo.toml L18

Release notes: serde-saphyr

2.0.0 2.0.0 Performance and compliance release

Breaking changes

• There is a new capture_comments feature that is default on and can be disabled, winning about 10 % percent of performance. This feature was the main reason to advance the first version digit, because formally this is a breaking change.
• Preserving inner error in alias errors in the newly added field in AliasError. The old field (text representation) is still present, but deprecated. Another formally breaking change, even if unlikely to be a problem.
• from_multiple, from_multiple_with_options, from_slice_multiple, and from_slice_multiple_with_options now accept T: Deserialize<'de> instead of T: DeserializeOwned, allowing values to borrow from the input. Direct calls require no changes. Function pointers or callbacks may need adjustments.
• granit_parser 2.0.0 has some corner formally breaking changes, but mostly in very obscure parts (see its changelog for details).

All other changes are backward compatible:

• For projects aiming for very strict YAML compliance rather than drop-in compatibility with mainstream libraries, it is not possible to disable all compromises with strict_indentation flag in Options.
• Value serialization target can now receive Inf and NaN if so configured. Even if most common serde_json::Value cannot take them (produces null instead), many other abstract value receivers can.
• Made huge_documents and serde_derived_types enable deserialize, fixing isolated feature
  builds with --no-default-features, including autopkgtests of Debian team (as observed).
• Fix borrow support for untagged enum (PR #195, thanks @Guiguiprim ).
• Added SerializerOptions::no_lang_directive (default false) to suppress the %YAML 1.2 directive independently of yaml_12's quoting (requirement obvious from Nushell code work work arrounds).
• Property interpolation can now be configured to be fully Docker Compose compliant if preferred (we are not fans of undefined property defaulting to empty but may be opinion-based).
• It is possible to deserialize multiple documents into collection other than vector: serde_saphyr::from_str_multiple supports any collection implementing Default + Extend<T>, such as Vec<T>, VecDeque<T>, BTreeSet<T>, or custom storage like SmallVec<T>.

Other fixes

• Keep span offsets relative to the caller's input after a BOM (#212)
• Compare mapping keys regardless of entry order (#211)
• Report a collection where &str is expected, not end of input (#210)
• Replace non-printable characters in Commented comments (#209)
• Implement dedicated YAML trim (#206). Default Rust trim() considers special Unicode whitespace chars that YAML calls to be ignored.
• Improve multi-snippet error rendering (#208). Do not rely on error texts for functionallity.
• Fix serializer indentation after - and ? so output reads back- #207
• Report a parser error after an implicit document end in single-document entry points- #220
  #220, thanks @pcshrosbree

Source

Release

Compare source

Release notes: sha2

No release notes available.
Source comparison unavailable: source refs for this transition are not known.

Release notes: tokio

No release notes available.
Source comparison unavailable: source refs for this transition are not known.

Release notes: uv-pep440

No release notes available.
Source comparison unavailable: source refs for this transition are not known.

Release notes: uv-pep508

No release notes available.
Source comparison unavailable: source refs for this transition are not known.

Release notes: wuast-common

No release notes available.

Release notes: wuast-ui

No release notes available.

Updates <code>rust dependencies</code>. **Breaking change detected.** Review the release notes before merging. Automerge: Disabled because breaking change release notes were detected ### Updates | Dependency | From | To | Type | Locations | | --- | --- | --- | --- | --- | | <code>serde-saphyr</code> | <code>1.3.0</code> | <code>2.0.0</code> | major | <code>Cargo.toml</code> L38 | | <code>sha2</code> | <code>0.11.0</code> | <code>0.11.1</code> | patch | <code>Cargo.toml</code> L34 | | <code>tokio</code> | <code>1.53.2</code> | <code>1.53.3</code> | patch | <code>Cargo.toml</code> L21, L61 | | <code>uv-pep440</code> | <code>0.0.92</code> | <code>0.0.93</code> | patch | <code>Cargo.toml</code> L41 | | <code>uv-pep508</code> | <code>0.0.92</code> | <code>0.0.93</code> | patch | <code>Cargo.toml</code> L42 | | <code>wuast-common</code> | <code>1.5.0</code> | <code>1.5.1</code> | patch | <code>Cargo.toml</code> L17 | | <code>wuast-ui</code> | <code>1.4.0</code> | <code>1.4.1</code> | patch | <code>Cargo.toml</code> L18 | <details> <summary>Release notes: <code>serde-saphyr</code></summary> #### <code>2.0.0</code> <code>2.0.0 Performance and compliance release</code> Breaking changes - There is a new capture_comments feature that is default on and can be disabled, winning about 10 % percent of performance. This feature was the main reason to advance the first version digit, because formally this is a breaking change. - Preserving inner error in alias errors in the newly added field in `AliasError`. The old field (text representation) is still present, but deprecated. Another formally breaking change, even if unlikely to be a problem. - from_multiple, from_multiple_with_options, from_slice_multiple, and from_slice_multiple_with_options now accept T: Deserialize<'de> instead of T: DeserializeOwned, allowing values to borrow from the input. Direct calls require no changes. Function pointers or callbacks may need adjustments. - granit_parser 2.0.0 has some corner formally breaking changes, but mostly in very obscure parts (see its changelog for details). All other changes are backward compatible: - For projects aiming for very strict YAML compliance rather than drop-in compatibility with mainstream libraries, it is not possible to disable all compromises with `strict_indentation` flag in Options. - Value serialization target can now receive `Inf` and `NaN` if so configured. Even if most common serde_json::Value cannot take them (produces `null` instead), many other abstract value receivers can. - Made `huge_documents` and `serde_derived_types` enable `deserialize`, fixing isolated feature builds with `--no-default-features`, including autopkgtests of Debian team (as [observed](https://dfsg-new-queue.debian.org/reviews/rust-serde-saphyr)). - Fix borrow support for untagged enum (PR #195, thanks @Guiguiprim ). - Added `SerializerOptions::no_lang_directive` (default `false`) to suppress the `%YAML 1.2` directive independently of `yaml_12`'s quoting (requirement obvious from [Nushell code work work arrounds](https://github.com/nushell/nushell/blob/d7cb4e589ea53bd1a0bb29dd78d63b76fcb59862/crates/nu-heavy-utils/src/yaml/serialize.rs#L158-L200)). - Property interpolation can now be configured to be fully Docker Compose compliant if preferred (we are not fans of undefined property defaulting to empty but may be opinion-based). - It is possible to deserialize multiple documents into collection other than vector: [`serde_saphyr::from_str_multiple`](https://docs.rs/serde-saphyr/latest/serde_saphyr/fn.from_str_multiple.html) supports any collection implementing `Default + Extend<T>`, such as `Vec<T>`, `VecDeque<T>`, `BTreeSet<T>`, or custom storage like [`SmallVec<T>`](https://docs.rs/smallvec/latest/smallvec/struct.SmallVec.html). Other fixes - Keep span offsets relative to the caller's input after a BOM (#212) - Compare mapping keys regardless of entry order (#211) - Report a collection where &str is expected, not end of input (#210) - Replace non-printable characters in Commented comments (#209) - Implement dedicated YAML trim (#206). Default Rust trim() considers special Unicode whitespace chars that YAML calls to be ignored. - Improve multi-snippet error rendering (#208). Do not rely on error texts for functionallity. - Fix serializer indentation after - and ? so output reads back- #207 - Report a parser error after an implicit document end in single-document entry points- #220 #220, thanks @pcshrosbree <a href="https://github.com/bourumir-wyngs/serde-saphyr">Source</a> <a href="https://github.com/bourumir-wyngs/serde-saphyr/releases/tag/2.0.0">Release</a> <a href="https://github.com/bourumir-wyngs/serde-saphyr/compare/1.3.0...master">Compare source</a> </details> <details> <summary>Release notes: <code>sha2</code></summary> No release notes available. Source comparison unavailable: source refs for this transition are not known. </details> <details> <summary>Release notes: <code>tokio</code></summary> No release notes available. Source comparison unavailable: source refs for this transition are not known. </details> <details> <summary>Release notes: <code>uv-pep440</code></summary> No release notes available. Source comparison unavailable: source refs for this transition are not known. </details> <details> <summary>Release notes: <code>uv-pep508</code></summary> No release notes available. Source comparison unavailable: source refs for this transition are not known. </details> <details> <summary>Release notes: <code>wuast-common</code></summary> No release notes available. </details> <details> <summary>Release notes: <code>wuast-ui</code></summary> No release notes available. </details>

Wuast94 added 1 commit 2026-10-13 11:59:15 +02:00

chore: update rust dependencies (0.11.0 → 0.11.1) 505933f4d9

Wuast94 scheduled this pull request to auto merge when all checks succeed 2026-10-13 11:59:17 +02:00

Wuast94 changed title from chore: update rust dependencies (0.11.0 → 0.11.1) to [breaking] chore: update rust dependencies (3 updates) 2026-10-14 12:00:16 +02:00

Wuast94 force-pushed updatarr/rust-dependencies-17605dfeaf from 505933f4d9 to 373204910a 2026-10-14 12:00:18 +02:00 Compare

Wuast94 changed title from [breaking] chore: update rust dependencies (3 updates) to [breaking] chore: update rust dependencies (5 updates) 2026-10-14 13:56:33 +02:00

Wuast94 force-pushed updatarr/rust-dependencies-17605dfeaf from 373204910a to a92e093d02 2026-10-14 13:56:34 +02:00 Compare

Wuast94 changed title from [breaking] chore: update rust dependencies (5 updates) to [breaking] chore: update rust dependencies (7 updates) 2026-10-15 01:29:43 +02:00

Wuast94 force-pushed updatarr/rust-dependencies-17605dfeaf from a92e093d02 to 200f817899 2026-10-15 01:29:45 +02:00 Compare

Wuast94 merged commit c0e3727e08 into main 2026-10-15 01:42:57 +02:00

Wuast94 referenced this pull request from a commit 2026-10-15 01:42:58 +02:00

Merge pull request '[breaking] chore: update rust dependencies (7 updates)' (#422) from updatarr/rust-dependencies-17605dfeaf into main

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

Wuast94/updatarr!422

No description provided.