Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jun 30, 2025

This PR contains the following updates:

Package Type Update Change
schemars (source) dependencies major 0.8.211.0.0

Release Notes

GREsau/schemars (schemars)

v1.2.0

Compare Source

Added
Changed
  • Schemas generated for HashMap/BTreeMap with enum keys are now more specific (#​452)

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 is behind base branch, 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
Copy link
Contributor Author

renovate bot commented Jun 30, 2025

⚠️ 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: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package [email protected] --precise 1.2.0
    Updating crates.io index
error: failed to select a version for the requirement `schemars = "^0.8"`
candidate versions found which didn't match: 1.2.0
location searched: crates.io index
required by package `k8s-openapi v0.25.0`
    ... which satisfies dependency `k8s-openapi = "^0.25.0"` of package `magnum-cluster-api v0.34.2 (/tmp/renovate/repos/github/vexxhost/magnum-cluster-api)`

@renovate renovate bot force-pushed the renovate/schemars-1.x branch 10 times, most recently from a262604 to a963380 Compare August 26, 2025 01:05
@renovate renovate bot force-pushed the renovate/schemars-1.x branch 16 times, most recently from 3366610 to a7cd433 Compare September 2, 2025 19:23
@mnaser
Copy link
Member

mnaser commented Sep 2, 2025

this is blocked by kube-rs pending the release of kube-rs/kube@92aca33

@renovate renovate bot force-pushed the renovate/schemars-1.x branch 2 times, most recently from f194c15 to af4ef3f Compare September 2, 2025 19:51
@renovate renovate bot force-pushed the renovate/schemars-1.x branch 4 times, most recently from 7b37bc4 to 30ed6a8 Compare September 20, 2025 15:57
@renovate renovate bot force-pushed the renovate/schemars-1.x branch 3 times, most recently from 7959ffa to 50896c9 Compare October 6, 2025 15:45
@renovate renovate bot force-pushed the renovate/schemars-1.x branch 8 times, most recently from 2b8317b to b0dc023 Compare October 17, 2025 03:39
@renovate renovate bot force-pushed the renovate/schemars-1.x branch from b0dc023 to a1036e9 Compare October 22, 2025 16:19
@renovate renovate bot force-pushed the renovate/schemars-1.x branch 12 times, most recently from 0a1b1ba to 99373bc Compare November 18, 2025 00:47
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/schemars-1.x branch from 99373bc to 2da3697 Compare December 12, 2025 01:21
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.

2 participants