chore(deps): update rust crate serde-saphyr to v1 #2235

Open

renovate wants to merge 1 commit from renovate/serde-saphyr-1.x into main

renovate commented

2026-09-12 16:10:32 +00:00

Collaborator

This PR contains the following updates:

Package	Type	Update	Change
serde-saphyr	workspace.dependencies	major	`0.0.29` → `1.0.0`

Release Notes

bourumir-wyngs/serde-saphyr (serde-saphyr)

`v1.2.0`

Compare Source

Changed

Folded property-interpolation depth and work limits into Budget; property resource-limit
failures are now reported through Error::Budget and BudgetBreach.
Added the opt-in Options::reject_unsupported_tags strict mode. It rejects explicitly tagged
scalar, sequence, and mapping nodes when their tag is unknown to serde-saphyr; the default remains
permissive for compatibility with custom tagged enums. YAML 1.1 !!merge and !!value are
accepted in this mode only as the exact scalar mapping keys << and =, respectively, while
robotics-only !degrees and !radians require both the robotics crate feature and
angle_conversions, and !include requires both the include crate feature and a configured
resolver.
Enforced the scalar, sequence, or mapping node kinds required by recognized tags even when
reject_unsupported_tags is disabled.
Hardened serializer indentation handling: indent_step is now limited to 1..=64, all
serializer entry points validate it, and indentation arithmetic returns an error instead of
overflowing. We do not consider this breaking because values outside this range does not look sane.
Validated custom anchor-generator names before emission. Names must be 1–256 bytes and cannot
contain whitespace, control characters, or YAML flow punctuation; unsupported names now return
a serialization error.

Fixes

Avoided unnecessary quotes around string keys and values containing an inline #, such as
a#b, while retaining quotes for leading or whitespace-separated hashes. Borrowed from
commit 1119a54
under the terms of the Apache/MIT licenses. When property interpolation is configured,
newly plain values such as ${NAME}#fragment can interpolate; use quote_all to preserve
literal values.
Recognized explicit YAML 1.1 !!merge keys, including verbatim tags and %TAG-expanded
handles, everywhere implicit << merge keys are supported.
Recognized the YAML 1.1 !!value tag while intentionally treating it as a no-op annotation.
Accepted valid zero-indented root folded block scalars, including #-prefixed content lines.
Fixed externally tagged typetag trait-object deserialization by consuming the closing mapping
event when a Serde map visitor returns after its final key/value pair, preventing a false
"multiple YAML documents" error.
Rejected non-UTF-8 canonical include and root-file paths before resolver policy checks and source
identity handling, preventing lossy path collisions and policy bypasses on Unix.
Reported alias-use locations as primary for unsupported-tag and budget failures during replay,
while retaining the anchor-definition locations as secondary context.

Testing

Reviewed yaml test suite, made sure all 350 active IDs and all 402 active cases are represented and documented
we use YAML Test Suite v2022-01-17.
property test with 1,024 generated cases to check the round trip.
added tests for typetag.

`v1.1.0`

Compare Source

Added

Added granit-parser resource limits to Budget (#172):
- max_buffered_comment_events (default: 32)
- simple_key_max_lookahead (default: 1,024 characters)
- flow_nesting_limit (default: 255)
The limits are applied to parsers created for strings, readers, standalone budget checks, and
included YAML sources. When the serde_derived_types feature is enabled, deserializing an older
Budget representation that omits these fields uses the documented defaults.

Fixes

Fixed enums tags for struct variants (#177).
Improved error message wording (#178).

`v1.0.1`: maintenance release

Compare Source

Fix #170 regression on local type tags
By fixing granit-parser (use its release 1.0.1), explicitly fix #169 (large scalar deserialization performance regression)

This release is fully API compatible with 1.0.0 and must be a drop-in replacement.

`v1.0.0`: - first real release

Compare Source

From this release onward, we are adopting the 1.x.x semantic versioning (SemVer) scheme. This means that API changes will be clearly reflected in the version number: the major version indicates breaking changes, the minor version indicates backward-compatible additions, and the patch version indicates backward-compatible fixes. The current compatibility status is indicated by the accompanying badge.

This release adds some #[track_caller] and #[must_use] annotations where looks reasonable. There are not many other changes that is exactly the point: the crate seems serving community well enough.

Configuration

📅 Schedule: (UTC)

Branch creation
- At any time (no schedule defined)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [serde-saphyr](https://github.com/bourumir-wyngs/serde-saphyr) | workspace.dependencies | major | `0.0.29` → `1.0.0` | --- ### Release Notes <details> <summary>bourumir-wyngs/serde-saphyr (serde-saphyr)</summary> ### [`v1.2.0`](https://github.com/bourumir-wyngs/serde-saphyr/blob/HEAD/CHANGELOG.md#120-Maintenance-release) [Compare Source](https://github.com/bourumir-wyngs/serde-saphyr/compare/1.1.0...1.2.0) ##### Changed - Folded property-interpolation depth and work limits into `Budget`; property resource-limit failures are now reported through `Error::Budget` and `BudgetBreach`. - Added the opt-in `Options::reject_unsupported_tags` strict mode. It rejects explicitly tagged scalar, sequence, and mapping nodes when their tag is unknown to serde-saphyr; the default remains permissive for compatibility with custom tagged enums. YAML 1.1 `!!merge` and `!!value` are accepted in this mode only as the exact scalar mapping keys `<<` and `=`, respectively, while robotics-only `!degrees` and `!radians` require both the `robotics` crate feature and `angle_conversions`, and `!include` requires both the `include` crate feature and a configured resolver. - Enforced the scalar, sequence, or mapping node kinds required by recognized tags even when `reject_unsupported_tags` is disabled. - Hardened serializer indentation handling: `indent_step` is now limited to `1..=64`, all serializer entry points validate it, and indentation arithmetic returns an error instead of overflowing. We do not consider this breaking because values outside this range does not look sane. - Validated custom anchor-generator names before emission. Names must be 1–256 bytes and cannot contain whitespace, control characters, or YAML flow punctuation; unsupported names now return a serialization error. ##### Fixes - Avoided unnecessary quotes around string keys and values containing an inline `#`, such as `a#b`, while retaining quotes for leading or whitespace-separated hashes. Borrowed from [commit 1119a54](https://github.com/bourumir-wyngs/serde-saphyr/commit/1119a54cc184d2151d53089f6be1b311b0f57e5a) under the terms of the Apache/MIT licenses. When property interpolation is configured, newly plain values such as `${NAME}#fragment` can interpolate; use `quote_all` to preserve literal values. - Recognized explicit YAML 1.1 `!!merge` keys, including verbatim tags and `%TAG`-expanded handles, everywhere implicit `<<` merge keys are supported. - Recognized the YAML 1.1 `!!value` tag while intentionally treating it as a no-op annotation. - Accepted valid zero-indented root folded block scalars, including `#`-prefixed content lines. - Fixed externally tagged `typetag` trait-object deserialization by consuming the closing mapping event when a Serde map visitor returns after its final key/value pair, preventing a false "multiple YAML documents" error. - Rejected non-UTF-8 canonical include and root-file paths before resolver policy checks and source identity handling, preventing lossy path collisions and policy bypasses on Unix. - Reported alias-use locations as primary for unsupported-tag and budget failures during replay, while retaining the anchor-definition locations as secondary context. ##### Testing - Reviewed yaml test suite, made sure all 350 active IDs and all 402 active cases are represented and documented we use [YAML Test Suite v2022-01-17](https://github.com/yaml/yaml-test-suite/releases/tag/v2022-01-17). - property test with 1,024 generated cases to check the round trip. - added tests for [typetag](https://crates.io/crates/typetag). ### [`v1.1.0`](https://github.com/bourumir-wyngs/serde-saphyr/blob/HEAD/CHANGELOG.md#110-Maintenance-release) [Compare Source](https://github.com/bourumir-wyngs/serde-saphyr/compare/1.0.1...1.1.0) ##### Added - Added granit-parser resource limits to `Budget` ([#172](https://github.com/bourumir-wyngs/serde-saphyr/issues/172)): - `max_buffered_comment_events` (default: 32) - `simple_key_max_lookahead` (default: 1,024 characters) - `flow_nesting_limit` (default: 255) The limits are applied to parsers created for strings, readers, standalone budget checks, and included YAML sources. When the `serde_derived_types` feature is enabled, deserializing an older `Budget` representation that omits these fields uses the documented defaults. ##### Fixes - Fixed enums tags for struct variants ([#177](https://github.com/bourumir-wyngs/serde-saphyr/issues/177)). - Improved error message wording ([#178](https://github.com/bourumir-wyngs/serde-saphyr/issues/178)). ### [`v1.0.1`](https://github.com/bourumir-wyngs/serde-saphyr/releases/tag/1.0.1): maintenance release [Compare Source](https://github.com/bourumir-wyngs/serde-saphyr/compare/1.0.0...1.0.1) - Fix [#170](https://github.com/bourumir-wyngs/serde-saphyr/issues/170) regression on local type tags - By fixing granit-parser (use its release 1.0.1), explicitly fix [#169](https://github.com/bourumir-wyngs/serde-saphyr/issues/169) (large scalar deserialization performance regression) This release is fully API compatible with 1.0.0 and must be a drop-in replacement. ### [`v1.0.0`](https://github.com/bourumir-wyngs/serde-saphyr/releases/tag/1.0.0): - first real release [Compare Source](https://github.com/bourumir-wyngs/serde-saphyr/compare/0.0.29...1.0.0) From this release onward, we are adopting the 1.x.x semantic versioning (SemVer) scheme. This means that API changes will be clearly reflected in the version number: the major version indicates breaking changes, the minor version indicates backward-compatible additions, and the patch version indicates backward-compatible fixes. The current compatibility status is indicated by the accompanying badge. This release adds some #\[track\_caller] and #\[must\_use] annotations where looks reasonable. There are not many other changes that is exactly the point: the crate seems serving community well enough. </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).

renovate added the

Dependencies

Dependencies/Renovate

labels

2026-09-12 16:10:32 +00:00

renovate added 1 commit

2026-09-12 16:10:33 +00:00

chore(deps): update rust crate serde-saphyr to v1

Auto Labeler / Apply labels based on changed files (pull_request_target) Successful in 13s

Details

Documentation / Build and Deploy Documentation (pull_request) Successful in 1m29s

Details