bottlerocket-update-operator icon indicating copy to clipboard operation
bottlerocket-update-operator copied to clipboard

Published 20 hours ago • verified publisher icon bottlerocket-os

build(deps): bump schemars from 0.8.22 to 1.0.2

Open dependabot[bot] opened this issue 4 months ago • 0 comments

Bumps schemars from 0.8.22 to 1.0.2.

Release notes

Sourced from schemars's releases.

v1.0.2

Fixed

v1.0.1

Fixed

  • Deriving JsonSchema with no_std broken due to std::borrow::ToOwned trait not being in scope (GREsau/schemars#441)

v1.0.0

This is a major release with many additions, fixes and changes since 0.8 (but not many since 0.9). While the basic usage (deriving JsonSchema and using schema_for!() or SchemaGenerator) is mostly unchanged, you may wish to consult the migration guide which covers some of the most significant changes.

Changes since 1.0.0-rc.2:

Added

  • #[schemars(bound = ...)] attributes are now used from fields as well as containers
  • The Schema::pointer(...) method now works when given a JSON pointer in URI Fragment representation with a leading # character. In particular, this means that you can now lookup a schema from a $ref value using that method.

Fixed

  • Schema names that contain special characters are now correctly encoded when used inside a $ref value (GREsau/schemars#436)
  • Optimise type param usage in SchemaGenerator::subschema_for, reducing LLVM line count and improving compile times (GREsau/schemars#439)

v1.0.0-rc.2

Added

  • Serde attributes that you want schemars to ignore can now be "unset" by including them in a schemars attribute with a ! prefix, e.g. #[schemars(!from)] (GREsau/schemars#433 / GREsau/schemars#434)

Removed

  • ⚠️ Deprecated items have been removed:
    • SchemaSettings::option_nullable and SchemaSettings::option_add_null_type fields
    • gen module

v1.0.0-rc.1

Added

Changed

  • Use oneOf when generating schema for serialized mixed-type sequences (GREsau/schemars#348) - the previous behaviour was to always use true schema (i.e. any value) for mixed-type sequences

v1.0.0-alpha.22

Added

... (truncated)

Changelog

Sourced from schemars's changelog.

[1.0.2] - 2025-06-26

Fixed

[1.0.1] - 2025-06-24

Fixed

  • Deriving JsonSchema with no_std broken due to std::borrow::ToOwned trait not being in scope (GREsau/schemars#441)

[1.0.0] - 2025-06-23

This is a major release with many additions, fixes and changes since 0.8 (but not many since 0.9). While the basic usage (deriving JsonSchema and using schema_for!() or SchemaGenerator) is mostly unchanged, you may wish to consult the migration guide which covers some of the most significant changes.

Changes since 1.0.0-rc.2:

Added

  • #[schemars(bound = ...)] attributes are now used from fields as well as containers
  • The Schema::pointer(...) method now works when given a JSON pointer in URI Fragment representation with a leading # character. In particular, this means that you can now lookup a schema from a $ref value using that method.

Fixed

  • Schema names that contain special characters are now correctly encoded when used inside a $ref value (GREsau/schemars#436)
  • Optimise type param usage in SchemaGenerator::subschema_for, reducing LLVM line count and improving compile times (GREsau/schemars#439)

[1.0.0-rc.2] - 2025-06-19

Added

  • Serde attributes that you want schemars to ignore can now be "unset" by including them in a schemars attribute with a ! prefix, e.g. #[schemars(!from)] (GREsau/schemars#433 / GREsau/schemars#434)

Removed

  • ⚠️ Deprecated items have been removed:
    • SchemaSettings::option_nullable and SchemaSettings::option_add_null_type fields
    • gen module

[1.0.0-rc.1] - 2025-06-16

Added

Changed

  • Use oneOf when generating schema for serialized mixed-type sequences (GREsau/schemars#348) - the previous behaviour was to always use true schema (i.e. any value) for mixed-type sequences

... (truncated)

Commits
  • 2697ecb v1.0.2
  • d3d96b6 Improve handling of keyword ordering in schema serialization (#445)
  • d8efe53 Delete broken symlinks
  • 0c38f5f v1.0.1
  • 092e971 Simplify docs.rs links
  • 98a707d Fix deriving with no_std (#442)
  • 0134a2e Remove v1 alpha notes
  • 1cc01f2 v1.0.0 🎉
  • ba9e3f3 Respect #[schemars(bound = ...)] attributes on fields as well as containers...
  • 1905e9a fix: (somewhat) avoid duplicate compilation of subschema_for
  • Additional commits viewable in compare view

Most Recent Ignore Conditions Applied to This Pull Request
Dependency Name Ignore Conditions
schemars [>= 0.9.a, < 0.10]

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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @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[bot] avatar Jun 27 '25 04:06 dependabot[bot]