[dependabot]

Bumps serde-saphyr from 2.0.0 to 2.1.1.

Release notes

Sourced from serde-saphyr's releases.

2.1.1 Optimization and maintenance release

Fixed

• Fixed 2.1.0 regression empty documents producing errors (#265). Empty document is a valid YAML document. Fix of this regression is the reason of making this release so early.

Performance improvements

• Significantly reduced allocations when deserializing (#262), thanks @​mat-gas

2.1.0 Minor feature extension, maintenance and performance release

Added

• Added opt-in Options::reject_tagged_field_names to catch misplaced tags on struct field names, with Error::TaggedStructFieldName diagnostics. Struct field names can only be strings; !!str is still accepted. As other tags can only be ignored, tag on a structure field name is almost for sure placed wrongly. This setting will be default in next major release.
• Added Options::leading_zero_numbers_as_strings and Options::underscored_numbers_as_strings to preserve numeric spellings such as 0755 and 1_000 as strings in untyped values, including untagged enums and flattened fields (#225). Both default to false; direct typed parsing, explicit numeric tags, and mapping-key comparison keep their existing behavior.
• Added Error::render_to to append diagnostics to any std::fmt::Write using RenderOptions, without collecting the complete output in an intermediate string (#221).
• Added DuplicateKeyPolicy::PassThrough to delegate repeated explicit mapping entries to Serde visitors, matching serde_yaml's handling for structs, standard maps, and custom multimap visitors (#226). The default remains Error; merge expansion retains its precedence rules. See the README migration note for the scope of this option.

Deprecated

• Deprecated SerializerOptions::empty_as_braces. Setting it to false emits YAML null for empty block collections without tags or anchors. These values do not round-trip into collection types. Omit the setting to keep the default true and emit [] or {}. Existing serialization behavior remains supported for compatibility.

Fixed

• Emit empty lines in literal and folded block scalars without indentation, avoiding trailing whitespace while preserving whitespace in the string content (#249).
• Expose the original std::io::Error from deserialization failures through std::error::Error::source(). The outer message is IO error, so error chains include the underlying cause only once. Standalone Miette, Figment, and Figment2 diagnostics retain the cause in their messages. Custom Miette formatters retain control over the complete message through MessageFormatter::format_standalone_message.
• Avoid duplicate messages from Error::WithSnippet when following std::error::Error::source() by forwarding the wrapped error's source. Use without_snippet() to inspect the wrapped error. Alias errors retain their complete source chain, including snippet wrappers, for compatibility.

... (truncated)

Changelog

Sourced from serde-saphyr's changelog.

2.1.1

Fixed

• Fixed 2.1.0 regression empty documents producing errors (#265). Empty document is a valid YAML document.

Performance improvements

• Significantly reduced allocations when deserializing (#262)

2.1.0

–

Added

• Added PropertySyntax::DockerComposeWithNulls: Compose interpolation where a value that is solely a reference to an unset property, or whose expansion is null/~, becomes YAML null. Explicitly empty properties and empty defaults stay empty strings, and DockerCompose itself is unchanged.
• Added opt-in Options::reject_tagged_field_names to catch misplaced tags on struct field names, with Error::TaggedStructFieldName diagnostics. Struct field names can only be strings, !!str is still accepted. As other tags can only be ignored, tag on a structure field name is almost for sure placed wrongly. This setting will be default in next major release.
• Added Options::leading_zero_numbers_as_strings and Options::underscored_numbers_as_strings to preserve numeric spellings such as 0755 and 1_000 as strings in untyped values, including untagged enums and flattened fields (#225). Both default to false; direct typed parsing, explicit numeric tags, and mapping-key comparison keep their existing behavior.
• Added Error::render_to to append diagnostics to any std::fmt::Write using RenderOptions, without collecting the complete output in an intermediate string (#221).
• Added DuplicateKeyPolicy::PassThrough to delegate repeated explicit mapping entries to Serde visitors, matching serde_yaml's handling for structs, standard maps, and custom multimap visitors (#226). The default remains Error; merge expansion retains its precedence rules. See the README migration note for the scope of this option.

Deprecated

• Deprecated SerializerOptions::empty_as_braces. Setting it to false emits YAML null for empty block collections without tags or anchors. These values do not round-trip into collection types. Omit the setting to keep the default true and emit [] or {}. Existing serialization behavior remains supported for compatibility.

Fixed

• Preserve application-tagged null-like documents in multi-document APIs, including the garde and validator integrations. A document such as !Maybe null now reaches enum dispatch instead of being skipped. This also affects default options: an Option<String> target receives a None item for !Foo null, while a String target reports NullIntoString. Untagged null documents and explicit !!null are still skipped.
• Resolve tagged enum payloads according to their target type under no_schema:

... (truncated)

Commits

• 07bfc26 Fix formatting
• a988642 Advance release version number
• ef4862b Restore empty YAML stream deserialization into collections (#265)
• 3501fa9 Reduce allocations when deserializing (#262)
• 38f4202 Removed unneeded here file
• 57f72d5 The failed parser now releases its cached error before conversion, preserving...
• 346afe2 Tag lookup optimization, this way confirmed to work faster.
• aa5d474 Number of tests goes over 4000
• 1cadc9c Prepare to 2.1.0 release
• 1d509d2 Add DockerComposeWithNulls with consistent null handling (#261)
• 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: dependencies. Please create it before Dependabot can add it to a pull request.

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