Home Original page

Bump schemars from 0.8.21 to 0.8.22 by dependabot[bot] · Pull Request #355 · KittyCAD/machine-api

Bumps schemars from 0.8.21 to 0.8.22.

Release notes

Sourced from schemars's releases.

v0.8.22

Fixed:

Changelog

Sourced from schemars's changelog.

[0.8.22] - 2025-02-25

Fixed:

[1.0.0-alpha.17] - 2024-12-02

Changed

  • For newtype variants of internally-tagged enums, prefer referencing the inner type's schema via $ref instead of always inlining the schema (GREsau/schemars#355) (this change was included in the release notes for 1.0.0-alpha.16, but was accidentally excluded from the published crate)

[1.0.0-alpha.16] - 2024-11-25

Removed (⚠️ breaking changes ⚠️)

  • the enumset1/enumset optional dependency has been removed, as its JsonSchema impl did not actually match the default serialization format of EnumSet (GREsau/schemars#339)

Changed (⚠️ breaking changes ⚠️)

  • MSRV is now 1.70
  • The example attribute value is now an arbitrary expression, rather than a string literal identifying a function to call. To avoid silent behaviour changes, the expression must not be a string literal where the value can be parsed as a function path - e.g. #[schemars(example = "foo")] is now a compile error, but #[schemars(example = foo())] is allowed (as is #[schemars(example = &"foo")] if you want the the literal string value "foo" to be the example).

Fixed

  • The "deserialize" schema for bytes::Bytes/BytesMut now allows strings, matching the actual deserialize behaviour of the types.
  • The schema for either::Either now matches the actual serialize/deserialize behaviour of that type.

[1.0.0-alpha.15] - 2024-09-05

Added

  • SchemaSettings now has a contract field which determines whether the generated schemas describe how types are serialized or deserialized. By default, this is set to Deserialize, as this more closely matches the behaviour of previous versions - you can change this to Serialize to instead generate schemas describing the type's serialization behaviour (GREsau/schemars#48 / GREsau/schemars#335)

Changed

  • Schemas generated for enums with no variants will now generate false (or equivalently {"not":{}}), instead of {"enum":[]}. This is so generated schemas no longer violate the JSON Schema spec's recommendation that a schema's enum array "SHOULD have at least one element".

[1.0.0-alpha.14] - 2024-08-29

Added

[1.0.0-alpha.13] - 2024-08-27

Fixed

  • Fix compile errors when using #[validate(regex(path = *expr))] attribute

... (truncated)

Commits

Dependabot compatibility score

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)