chore(deps): update rust crate serde-saphyr to 0.0.26 #1765

Merged

ginger merged 1 commit from renovate/serde-saphyr-0.x into main

2026-05-14 13:22:37 +00:00

renovate commented

2026-05-14 05:03:20 +00:00

Collaborator

This PR contains the following updates:

Package	Type	Update	Change
serde-saphyr	workspace.dependencies	patch	`0.0.25` → `0.0.26`

Release Notes

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

`v0.0.26`

Compare Source

UTF-16LE, UTF-16BE, UTF-8 with BOM and UTF-8 without BOM are all supported for the Reader - based methods (stabilized)
Relaxed from_slice to support borrowed deserialization, aligning its behavior with from_str and from_slice_with_options
Reduce size of Location data structure in huge_documents mode, using 48 bits only for offsets. This silences Clippy warnings, due these some teams needed to box serde-saphyr Error. The maximal size of documents in huge_documents mode is now 256 Tb that is unlikely a problem (default limit is 4 Gb).
saphyr-parser-bw, whose primary consumer is serde-saphyr, has been renamed to granit-parser, adjusting serde-saphyr dependencies. The granit-parser crate has undergone a security audit followed by additional hardening.

Merge key handling is now configurable via MergeKeyPolicy. There may be communities that

Indeed have such a strange keys like << as ordinary, and these are even not quoted, maybe in generated YAML. Handling of this case is supported via AsOrdinary variant.
Took very strict internal policy disallow merge keys in configurations that is their choice, and want to alert about their presence to automate the code review. Handling them as ordinary may result valid YAML with unexpected result, and would not report the error location properly, so there is an Error variant for this case.
Have legacy code with merge keys, or see nothing wrong with them (default: Merge)

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.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [serde-saphyr](https://github.com/bourumir-wyngs/serde-saphyr) | workspace.dependencies | patch | `0.0.25` → `0.0.26` | --- ### Release Notes <details> <summary>bourumir-wyngs/serde-saphyr (serde-saphyr)</summary> ### [`v0.0.26`](https://github.com/bourumir-wyngs/serde-saphyr/releases/tag/0.0.26) [Compare Source](https://github.com/bourumir-wyngs/serde-saphyr/compare/0.0.25...0.0.26) - UTF-16LE, UTF-16BE, UTF-8 with BOM and UTF-8 without BOM are all supported for the Reader - based methods (stabilized) - Relaxed from\_slice to support borrowed deserialization, aligning its behavior with from\_str and from\_slice\_with\_options - Reduce size of Location data structure in `huge_documents` mode, using 48 bits only for offsets. This silences Clippy warnings, due these some teams needed to box serde-saphyr Error. The maximal size of documents in huge\_documents mode is now 256 Tb that is unlikely a problem (default limit is 4 Gb). - saphyr-parser-bw, whose primary consumer is serde-saphyr, has been renamed to granit-parser, adjusting serde-saphyr dependencies. The granit-parser crate has undergone a security audit followed by additional hardening. Merge key handling is now configurable via MergeKeyPolicy. There may be communities that - Indeed have such a strange keys like `<<` as ordinary, and these are even not quoted, maybe in generated YAML. Handling of this case is supported via `AsOrdinary` variant. - Took very strict internal policy disallow merge keys in configurations that is their choice, and want to alert about their presence to automate the code review. Handling them as ordinary may result valid YAML with unexpected result, and would not report the error location properly, so there is an `Error` variant for this case. - Have legacy code with merge keys, or see nothing wrong with them (default: `Merge`) </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](https://github.com/renovatebot/renovate).

renovate added the

Dependencies

Dependencies/Renovate

labels

2026-05-14 05:03:20 +00:00

renovate added 1 commit

2026-05-14 05:03:20 +00:00

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

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

Details

Checks / Prek / Check changed files (pull_request) Successful in 6s

Details