[dependabot]

Bumps serde-saphyr from 0.0.27 to 1.3.0.

Release notes

Sourced from serde-saphyr's releases.

1.3.0 Maintenance and performance release

• Integer mapping keys now compare by their parsed numeric value for duplicate detection and merge resolution, including inside composite keys (0xB and 11 compare equal). Deserializing to strings preserves the original spelling; FirstWins and LastWins retain the selected key's spelling and associated value.
• Composite keys containing null-like strings now preserve both the key and its associated value; for example, {{"null": 1}: 2} now round-trips correctly.
• Null mapping keys now remain distinct from null-like string keys during duplicate detection and merge resolution, including inside composite keys.
• Null detection now respects string tags and scalar styles, preserving null-like strings such as !!str null, including when deserializing to Option<String>.
• Explicit numeric tags (!!int and !!float) now deserialize correctly through deserialize_any, including quoted and block scalars.
• Floating-point deserialization now rejects incompatible core tags; for example, from_str::<f64>("!!str 1.5") now returns an error.
• Serialization now escapes U+FFFE and U+FFFF as \uFFFE and \uFFFF.
• Serialization now preserves newline-only strings in literal block scalars, including LitStr and LitString, by using keep chomping and retaining every empty line.
• Updated the granit-parser revision to preserve document boundaries after zero-indented root literal and folded block scalars, including empty strings.
• Preserve string scalars across YAML 1.1 readers (PR #90, thanks @​NiklasRosenstein)
• The version increased to 1.3 because it uses granit-parser 1.3, and that is because granit-parser added two methods to Input for performance improvements. As serde-saphyr re-exports it, the version number must be increased to 1.3 as well, even if no new features are added to this crate itself.

1.2.0 It's all about !!tags this time

This release focuses on enhanced tag support.

• Implemented tag capturing (#183). Applications can use custom tags to express units, priorities, accessibility, or other application-specific semantics for a node. This is supported by new Tagged<T> wrapper that is similar to Commented<T>.
• Unsupported tags can now be rejected rather than ignored (new option reject_unsupported_tags, #180). This aligns the behavior with ruamel.yaml that rejects tags for which it has no constructor (serde-saphyr does not construct this way) that caused discussion on prek.
• Clearly wrongly placed tags like !!int [1] or !!map [1] are now an error.
• Documentation was revised to make sure all examples compile (are not fragments).

1.1.0 Maintenance release

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)

... (truncated)

Changelog

Sourced from serde-saphyr's changelog.

1.3.0 Maintenance and performance release

Fixed

• Integer mapping keys now compare by their parsed numeric value for duplicate detection and merge resolution, including inside composite keys (0xB and 11 compare equal). Deserializing to strings preserves the original spelling; FirstWins and LastWins retain the selected key's spelling and associated value.
• Composite keys containing null-like strings now preserve both the key and its associated value; for example, {{"null": 1}: 2} now round-trips correctly.
• Null mapping keys now remain distinct from null-like string keys during duplicate detection and merge resolution, including inside composite keys.
• Null detection now respects string tags and scalar styles, preserving null-like strings such as !!str null, including when deserializing to Option<String>.
• Explicit numeric tags (!!int and !!float) now deserialize correctly through deserialize_any, including quoted and block scalars.
• Floating-point deserialization now rejects incompatible core tags; for example, from_str::<f64>("!!str 1.5") now returns an error.
• Serialization now escapes U+FFFE and U+FFFF as \uFFFE and \uFFFF.
• Serialization now preserves newline-only strings in literal block scalars, including LitStr and LitString, by using keep chomping and retaining every empty line.
• Updated the granit-parser revision to preserve document boundaries after zero-indented root literal and folded block scalars, including empty strings.
• Preserve string scalars across YAML 1.1 readers (PR #90, thanks @​NiklasRosenstein)
• The version increased to 1.3 because it uses granit-parser 1.3, and that is because granit-parser added two methods to Input for performance improvements. As serde-saphyr re-exports it, the version number must be increased to 1.3 as well, even if no new features are added to this crate itself.

1.2.0 Maintenance release

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.

... (truncated)

Commits

• 93e634c Switching to 1.3.0
• b94505a Miri fix
• aa4adad We will need to go 1.3
• 7a1646e Update CHANGELOG.md
• b17fc43 Extend the quoting check to signed lowercase 0o forms
• 8aae8fe Preserve string scalars across YAML 1.1 readers (#190)
• de014b0 Bump rstest from 0.26.1 to 0.27.0 (#191)
• bbd93a8 Switch to released granit parser.
• 49ecf1b Next release start automatically on tag push
• 6bcee83 Fix pirate formatter test
• 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]

Superseded by #46.