build(deps): bump serde-saphyr from 0.0.11 to 1.1.0

[dependabot]

Bumps serde-saphyr from 0.0.11 to 1.1.0.

Release notes

Sourced from serde-saphyr's releases.

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)

1.0.1 maintenance release

• 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.

1.0.0 - first real release

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.

1.0.0-rc.1 release preview

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.

Some breaking changes were made at this point because this is the last good time to streamline the API. Please raise any issues you find with the API changes, or if you would like to propose something. The goal of the release preview is exactly not to go 2.x.x next week after release.

• Options, SerializerOptions, Budget, and AliasLimits are now #[non_exhaustive]. Construct them with options!, ser_options!, budget!, and alias_limits!.
• Removed the deprecated to_writer and to_writer_with_options APIs. Use to_fmt_writer* for fmt::Write or to_io_writer* for io::Write.
• API compatibility check no guards compatibility with 1.0.0

Also

• Fix core tag enforcement. In the previous version, !!str 42 is accepted as i32(42), and !!int true is accepted as bool(true). Core tag handling is now hardened, and such constructs no longer pass.
• Fix: budget callbacks were sometimes not delivered on immediate breaches

0.0.29 Hardening release

• Summarizing results of automated fuzzing and static analysis, robustness against malformed (bad intent) YAML input was further hardened.
• Docker-compose, whose syntax serde-saphyr emulates, supports property nesting, so implemented nesting support for serde-saphyr as well. In the previous release, "${SET:-${B}}" with SET=value resolves to "value}".
• Fixed incorrect acceptance on Rust's float grammar (inf/Infinity/nan). YAML 1.2 only recognizes the .inf/.nan forms.
• Fixed caret misaligned in secondary snippet windows when line numbers exceed one digit
• FoldStr wrapping now cares not to start a continuation line with a tab
• Error reporting has been improved, showing location in some cases where previous versions were unable.
• Remove base64 create from deserializer dependencies (faster build)
• New version of (also hardened) granit-parser 0.0.7.

... (truncated)

Changelog

Sourced from serde-saphyr's changelog.

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).

Commits

• ad5c614 Granit parser fix
• 6a78135 Formatting fix
• e05e51f Bw/sr (#179)
• 146b4ae Integrate new granit-parser ability to suppress comments (#174)
• a8450ae Fix YAML tag metadata specifically for mappings. Fix #177 (#178)
• f11f2cc Switch into granit-parse git version
• ec5ba12 Merge remote-tracking branch 'origin/master'
• 6e32b1e Fix #172 : add granit-parser resource limits to Budget
• 65c5ad6 Explicit test for issue #170
• a3dee91 Explicit test for issue #170
• 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)