Update Rust crate ron to 0.12.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
ron	dependencies	minor	0.6.2 -> 0.12.0

---

Release Notes

ron-rs/ron (ron)

v0.12.0

Compare Source

API Changes

• Breaking: Removed the ron::error::Error::Base64Error variant. (#​566)
• Added into_inner() method to ron::ser::Serializer to retrieve the inner writer. (#​588)
• Removed the base64 dependency. (#​566)

Format Changes

• Format-Breaking: Remote base64-encoded byte strings deserialisation, replaced by Rusty byte strings in v0.9.0 (#​566)

Bug Fixes

• Fixed untagged enum deserialisation for serde >= 1.0.220 with better serde content detection (#​582)

v0.11.0

Compare Source

API Changes

• Breaking: SpannedError now stores the full error span in span: Span { start: Position, end: Position }`, to facilitate, e.g., language server highlighting of syntax errors.
• Breaking: Added no_std support via a new std feature (enabled by default). With default features disabled, you must enable the std feature to access de::from_reader, and the std::io operations on Options, such as from_reader, from_reader_seed, to_io_writer, and to_io_writer_pretty (#​567)
• Breaking: Fixed (again) ron::value::Number to ensure it is non-exhaustive, to avoid breaking matches when feature unification enables more of its variants than expected (#​568)

Examples

• Add a new example file_read_write_vec.rs for reading and writing Vec<T> to/from files. (#​573)

v0.10.1

API Changes

• Add ron::Options::to_io_writer and ron::Options::to_io_writer_pretty to allow writing into an io::Writer (#​561)
• Breaking: ron::value::Number is now non-exhaustive, to avoid breaking matches when feature unification enables more of its variants than expected (#​564)

v0.9.0

Compare Source

API Changes

• Breaking: Removed the ron::error::Error::Base64Error variant. (#​566)
• Added into_inner() method to ron::ser::Serializer to retrieve the inner writer. (#​588)
• Removed the base64 dependency. (#​566)

Format Changes

• Format-Breaking: Remote base64-encoded byte strings deserialisation, replaced by Rusty byte strings in v0.9.0 (#​566)

Bug Fixes

• Fixed untagged enum deserialisation for serde >= 1.0.220 with better serde content detection (#​582)

v0.8.1

Compare Source

• Fix issues #​277 and #​405 with Value::Map IntoIter and extraneous item check for Value::Seq (#​406)
• Fix issue #​401 with correct raw struct name identifier parsing (#​402)
• Fix issue #​410 trailing comma parsing in tuples and Some (#​412)
• Error instead of panic when deserializing non-identifiers as field names (#​415)
• [Non-API] Breaking: Fix issue #​307 stack overflow with explicit recursion limits in serialising and deserialising (#​420)
• Fix issue #​423 deserialising an identifier into a borrowed str (#​424)
• Bump MSRV to 1.57.0 and bump dependency: base64 to 0.20 (#​431)
• Bump dependency base64 to 0.21 (#​433)
• Depend on serde_derive directly to potentially enable more compilation parallelism (#​441)
• [Non-API] Breaking: Bump bitflags dependency to 2.0, changes serde impls of Extensions (#​443)
• Add Map::retain method (#​460)
• Bump MSRV to 1.64.0 and bump dependency: indexmap to 2.0 (#​459)

v0.8.0

Compare Source

• Bump dependencies: bitflags to 1.3, indexmap to 1.9 (#​399)
• Add integer128 feature that guards i128 and u128 (#​304, #​351)
• Fix issue #​265 with better missing comma error (#​353)
• Fix issue #​301 with better error messages (#​354)
• Fix issue #​337 by removing decimal_floats PrettyConfig option and unconditional decimals in floats (#​363)
• Fix issue #​203 with full de error positioning (#​356)
• Expand the ron::Error enum to distinguish serde errors like NoSuchEnumVariant and MissingStructField with error positioning (#​394)
• Bump MSRV to 1.56.0 (#​396)

v0.7.1

Compare Source

• Add struct_names option to PrettyConfig (#​329)
• Fix newtype variant unwrapping around enum, seq and map (#​331)
• Implement unwrap_newtypes extension during serialization (#​333)
• Implement unwrap_variant_newtypes extension during serialization (#​336)
• Add compact_arrays (#​299) and separator options to PrettyConfig (#​349)
• Fix issue #​338 value map roundtrip (#​341)
• Fix issue #​289 enumerate_arrays comments (#​344)
• Report struct name in expected struct error (#​342)
• Add Options builder to configure the RON serde roundtrip (#​343)
• Fix issue #​367 with eager implicit some (#​368)
• Fix issue #​359 with DeserializeSeed support (#​360)
• Fix issue #​370 with FromStr-equivalent float EBNF and Error::FloatUnderscore (#​371)
• Fix issue #​374 extraneous .0 for small floats (#​372)
• Deprecate Serializer::new (#​382)

v0.7.0

Compare Source

• Add unwrap_variant_newtypes extension (#​319)
• Change MSRV to 1.36

v0.6.6

• Fix serialization of raw identifiers (#​323)

v0.6.5

• support serde renames that start with a digit

v0.6.3

• bump base64 dependency to 0.13

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: sanity-bin/Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path sanity-bin/Cargo.toml --package [email protected] --precise 0.8.1
error: package ID specification `[email protected]` did not match any packages
Did you mean one of these?

  [email protected]
  [email protected]

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: sanity-bin/Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path sanity-bin/Cargo.toml --package [email protected] --precise 0.12.0
error: package ID specification `[email protected]` did not match any packages
help: there are similar package ID specifications:

  [email protected]
  [email protected]