Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jun 23, 2025

This PR contains the following updates:

Package Type Update Change
schemars (source) dependencies major 0.8.21 -> 1.0.0

Release Notes

GREsau/schemars (schemars)

v1.1.0

Compare Source

Added
  • Public functions that have no side-effects are now marked with #[must_use] so that they report a lint warning when the returned value is unused, as this likely indicates a mistake.
Fixed
  • Improve accuracy of schemas for flattened enums, in particular: unit variants of externally-tagged enums, and enums wrapped in Option<>. (#​464 / #​483)

v1.0.5

Compare Source

Fixed
  • Fix schema.pointer_mut() to resolve URI fragment identifiers like #/$defs/foo, matching current behaviour of schema.pointer() (#​478 / #​479)

v1.0.4

Compare Source

Fixed
  • Fix JsonSchema impl on atomic types being ignored on non-nightly compilers due to a buggy cfg check (#​453)
  • Fix compatibility with minimal dependency versions, e.g. old(-ish) versions of syn (#​450)
  • Fix derive for empty tuple variants (#​455)

v1.0.3

Compare Source

Fixed
  • Fix compile error when a doc comment is set on both a transparent (or newtype) struct and its field (#​446)
  • Fix json_schema!() macro compatibility when used from pre-2021 rust editions (#​447)

v1.0.2

Compare Source

Fixed
  • Fix schema properties being incorrectly reordered during serialization (#​444)

v1.0.1

Compare Source

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

v1.0.0

Compare Source

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 (#​436)
  • Optimise type param usage in SchemaGenerator::subschema_for, reducing LLVM line count and improving compile times (#​439)

v0.9.0

Compare Source

This version is identical to 1.0.0-alpha.18, but is available for those who are unable to unwilling to use a pre-release version.

Those upgrading from Schemars 0.8 may want to consult the migration guide, which also applies when migrating from 0.8 to 0.9.


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 this update 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 renovate bot force-pushed the renovate/schemars-1.x branch from 99e00a2 to 8771512 Compare August 10, 2025 13:39
@renovate renovate bot force-pushed the renovate/schemars-1.x branch from 8771512 to 7670e9e Compare September 25, 2025 17:03
@renovate renovate bot force-pushed the renovate/schemars-1.x branch from 7670e9e to 99b07a5 Compare November 3, 2025 00:30
@renovate renovate bot force-pushed the renovate/schemars-1.x branch from 99b07a5 to c7bbbdc Compare November 5, 2025 22:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant