Skip to content

Bump serde-saphyr from 1.1.0 to 2.2.0 - #1

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/serde-saphyr-2.1.1
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/serde-saphyr-2.1.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 9, 2026 •

Copy link
Copy Markdown

Bumps serde-saphyr from 1.1.0 to 2.2.0.

Release notes

Sourced from serde-saphyr's releases.

2.2.0 Compatiblity release

This release includes non-breaking changes accumulated while preparing for 3.0.0, which will include breaking changes to tag handling, number formats with underscores, and other corner cases.

Added

  • Added opt-in Options::null_as_string (default: false) to preserve plain null, Null, NULL, ~, and empty scalars as text for string targets in both mapping keys and values, including String, &str, and Cow<str> (#267). Explicit !!null tags remain rejected for strings; Option<T>, untyped null inference, mapping-key comparison, and no_schema quoting requirements keep their existing behavior.
  • Added Options::bom_inside_document_as_content (default false) to preserve a BOM at the start of a token inside a document as plain scalar content, including in included YAML. A BOM in a document prefix is still skipped.

Fixed

  • Preserve uppercase radix prefixes (0X, 0O, 0B, including signed forms) as strings during implicit type inference, including untagged enums and flattened fields (#266). Direct typed integer parsing, explicit !!int tags, and mapping-key comparison retain their existing behavior.
  • Infer plain signed not-a-number spellings (+.nan, -.NaN, -.NAN) as strings during implicit type inference, since the YAML 1.2 Core schema allows a sign on .inf only (#271; #272, #273). This applies under every NonFiniteFloatPolicy, including untagged enums and flattened fields. Also accept these spellings without quotes when no_schema: true for string values and mapping keys, including String, &str, and Cow<str>. Direct untagged float targets continue to accept them as NaN. Explicit !!float scalars now preserve the supplied NaN sign when deserialized as floats.

Changed

  • Updated to granit-parser 2.2.0. Under-indented quoted scalar continuations in block context and tabs before quoted continuations are now accepted by default; strict_indentation: true continues to reject them.

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.

... (truncated)

Changelog

Sourced from serde-saphyr's changelog.

2.2.0

Added

  • Added opt-in Options::null_as_string (default: false) to preserve plain null, Null, NULL, ~, and empty scalars as text for string targets in both mapping keys and values, including String, &str, and Cow<str> (#267). Explicit !!null tags remain rejected for strings; Option<T>, untyped null inference, mapping-key comparison, and no_schema quoting requirements keep their existing behavior.
  • Added Options::bom_inside_document_as_content (default false) to preserve a BOM at the start of a token inside a document as plain scalar content, including in included YAML. A BOM in a document prefix is still skipped.

Fixed

  • Preserve uppercase radix prefixes (0X, 0O, 0B, including signed forms) as strings during implicit type inference, including untagged enums and flattened fields (#266). Direct typed integer parsing, explicit !!int tags, and mapping-key comparison retain their existing behavior.
  • Infer plain signed not-a-number spellings (+.nan, -.NaN, -.NAN) as strings during implicit type inference, since the YAML 1.2 Core schema allows a sign on .inf only (#271; #272, #273). This applies under every NonFiniteFloatPolicy, including untagged enums and flattened fields. Also accept these spellings without quotes when no_schema: true for string values and mapping keys, including String, &str, and Cow<str>. Direct untagged float targets continue to accept them as NaN. Explicit !!float scalars now preserve the supplied NaN sign when deserialized as floats.

Changed

  • Updated to granit-parser 2.2.0. Under-indented quoted scalar continuations in block context and tabs before quoted continuations are now accepted by default; strict_indentation: true continues to reject them.

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

... (truncated)

Commits
  • c0b737a Formatting fix
  • 3d83fe9 Set version number
  • 4766a49 Migrate to granit-parser 2.2.0 and prepare for 2.2.0 release
  • f0fee62 Migrate to granit-parser 2.2.0 and prepare for 2.2.0 release
  • 4d7b62c Bump smallvec from 1.16.4 to 1.16.5 (#277)
  • 2ed4284 Bump annotate-snippets from 0.12.17 to 0.12.18 (#276)
  • 3f57600 Accept signed NaN strings and preserve explicit float signs (#273)
  • c680e06 Infer signed .nan spellings as strings during implicit inference (#272)
  • a96e179 Add opt-in null-as-string deserialization for keys and values (#269)
  • 32da30e Preserve uppercase radix prefixes during implicit inference (#268)
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Nov 9, 2026
Bumps [serde-saphyr](https://github.com/bourumir-wyngs/serde-saphyr) from 1.1.0 to 2.2.0.
- [Release notes](https://github.com/bourumir-wyngs/serde-saphyr/releases)
- [Changelog](https://github.com/bourumir-wyngs/serde-saphyr/blob/master/CHANGELOG.md)
- [Commits](bourumir-wyngs/serde-saphyr@1.1.0...2.2.0)

---
updated-dependencies:
- dependency-name: serde-saphyr
  dependency-version: 2.1.1
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title Bump serde-saphyr from 1.1.0 to 2.1.1 Bump serde-saphyr from 1.1.0 to 2.2.0 Nov 21, 2026
@dependabot
dependabot Bot force-pushed the dependabot/cargo/serde-saphyr-2.1.1 branch from d494ace to b081c5d Compare November 21, 2026 19:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants