chore(deps): update serde-saphyr requirement from =0.0.21 to =0.0.22

[dependabot]

Updates the requirements on serde-saphyr to permit the latest version.

Release notes

Sourced from serde-saphyr's releases.

0.0.22 - !include and properties

This release introduces support for !include. While not a standard YAML, multiple existing implementations show the need for this capability.

serde-saphyr now can resolve !include tags through a custom resolver configured via Options. The !include functionality is gated behind the include feature and must also be explicitly enabled by providing a resolver. For convenience, a safety-hardened filesystem-based resolver is available as an additional optional feature (include-fs).

This library also now supports properties, implemented in a Docker Compose-like style:

  database_password: ${DATABASE_PASSWORD}

Properties are implemented to prevent their values from being checked into the repository or from leaking via error snippets or other messages in logs. Tests were written to ensure that the value is never printed on error (please supply the security report if it is). Property values are provided via a custom-supplied HashMap, so up to the user how to store them safely, or maybe even generate them.

Other improvements

• Full support for JSON-style Unicode surrogate pairs in quoted strings. serde-saphyr now correctly decodes valid UTF-16 surrogate pair escapes such as \uD834\uDD1E into a single Unicode scalar, matching the equivalent YAML \U form. We also expanded the JSON compatibility test coverage with dedicated cases for objects, arrays, URLs, Unicode escapes, numbers, booleans, and null, and the full related test suite now passes.
• Indentation checking. Adding or removing a single space in YAML indentation may result in a document that is still syntactically correct but semantically wrong. To mitigate such issues, serde-saphyr can enforce indentation rules during deserialization via RequireIndent.
• Support options for to_string_multiple, #87. Thanks, Eirik A @​clux)
• Fixed merge key expansion that bypassed duplicate-key enforcement. Now, merge keys also require all keys to be unique. However, if you rely heavily on overriding key values during merge, you can set DuplicateKeyPolicy in Options to

Commits

• c6696cd Last small README improvement
• 09ebb6e Last small README improvement
• 043c702 Documenting with_include_resolver
• fa7a68b Merge remote-tracking branch 'origin/master'
• 80ca14e Snal formatting
• 892d52e Switching to saphyr-parser-bw crates.io version 0.0.610, setting release to 0...
• 0eaba66 Merge remote-tracking branch 'origin/master'
• a16aa36 Adding SOOS badge
• 0ac01e5 Saphyr parser bw update
• 932da62 Persistent tag directives can taint later documents
• 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, rust. Please create them before Dependabot can add them to a pull request.

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

[dependabot]

Superseded by #35.