serde_with v3.8.1

Fixed

• Do not emit schemars(deserialize_with = "...") annotations, as schemars does not support them (#735)
  Thanks to @sivizius for reporting the issue.

serde_with v3.8.0

Added

• Implement (De)Serialization for Pinned Smart Pointers by @Astralchroma (#733)
• Implement JsonSchemaAs for PickFirst by @swlynch99 (#721)

Changed

• Bump base64 dependency to v0.22 (#724)
• Update dev dependencies

Fixed

• serde_conv regressed and triggered clippy::ptr_arg and add test to prevent future problems. (#731)

serde_with v3.7.0

Added

• Implement JsonSchemaAs for EnumMap by @swlynch99 (#697)
• Implement JsonSchemaAs for IfIsHumanReadable by @swlynch99 (#717)
• Implement JsonSchemaAs for KeyValueMap by @swlynch99 (#713)
• Implement JsonSchemaAs for OneOrMany by @swlynch99 (#719)

Fixed

• Detect conflicting schema_with attributes on fields with schemars annotations by @swlynch99 (#715)
  This extends the existing avoidance mechanism to a new variant fixing #712.

serde_with v3.6.1

Changed

• Eliminate dependency on serde's "derive" feature by @dtolnay (#694)
  This allows parallel compilation of serde and serde_derive which can speed up the wallclock time.
  It requires that downstream crates do not use the "derive" feature either.

serde_with v3.6.0

Added

• Add IfIsHumanReadable for conditional implementation by @irriden (#690)
  Used to specify different transformations for text-based and binary formats.
• Add more JsonSchemaAs impls for all Duration* and Timestamp* adaptors by @swlynch99 (#685)

Changed

• Bump MSRV to 1.65, since that is required for the regex dependency.

serde_with v3.5.1

Fixed

• The serde_as macro now better detects existing schemars attributes on fields and incorporates them by @swlynch99 (#682)
  This avoids errors on existing #[schemars(with = ...)] annotations.

serde_with v3.5.0

Added

• Support for schemars integration added by @swlynch99 (#666)
  The support uses a new Schema top-level item which implements JsonSchema
  The serde_as macro can now detect schemars usage and emits matching annotations for all fields with serde_as attribute.
  Many types of this crate come already with support for the schemars, but support is not complete and will be extended over time.

serde_with v3.4.0

• Lower minimum required serde version to 1.0.152 (#653)
  Thanks to @banool for submitting the PR.

  This allows people that have a problem with 1.0.153 to still use serde_with.

• Add support for core::ops::Bound (#655)
  Thanks to @qsantos for submitting the PR.

serde_with v3.3.0

Added

• Support the hashbrown type HashMap and HashSet (#636, #637)
  Thanks to @OliverNChalk for raising the issue and submitting a PR.

  This extends the existing support for HashMaps and HashSets to the hashbrown crate v0.14.
  The same conversions as for the std and indexmap types are available, like general support for #[serde_as] and converting it to/from sequences or maps.

Changed

• Generalize some trait bounds for DeserializeAs implementations

  While working on #637 it came to light that some of the macros for generating DeserializeAs implementations were not as generic as they could.
  This means they didn't work with custom hasher types, but only the default hashers.
  This has now been fixed and custom hashers should work better, as long as they implement BuildHasher + Default.

• (internal) Change how features are documented (#639)

  This change moves the feature documentation into Cargo.toml in a format that can be read by lib.rs.
  It will improve the generated features documentation there.
  The page with all features remains in the guide but is now generated from the Cargo.toml information.

serde_with v3.2.0

Added

• Add optional support for indexmap v2 (#621)
  Support for v1 is already available using the indexmap_1 feature.
  This adds identical support for v2 of indexmap using the indexmap_2 feature.

Changed

• Bump MSRV to 1.64, since that is required for the indexmap v2 dependency.

Fixed

• Prevent panics when deserializing i64::MIN using TimestampSeconds<i64> (#632, #633)
  Thanks to @hollmmax for reporting and fixing the issue.