Skip to content

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jul 12, 2025

Note

Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to mend[bot].

This notice will be removed on 2025-10-07.


This PR contains the following updates:

Package Type Update Change
schemars (source) dependencies major 0.8 -> 1.0

Release Notes

GREsau/schemars (schemars)

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.

Copy link

changeset-bot bot commented Jul 12, 2025

⚠️ No Changeset found

Latest commit: fab217c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot force-pushed the renovate/schemars-1.x branch from e4c66f4 to fab217c Compare September 26, 2025 23:25
Copy link
Author

renovate bot commented Sep 26, 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: apps/cli/Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path apps/cli/Cargo.toml --package schemars@0.8.22 --precise 1.0.4
error: failed to acquire package cache lock

Caused by:
  failed to open: /home/ubuntu/.cargo/.package-cache

Caused by:
  failed to create directory `/home/ubuntu/.cargo`

Caused by:
  File exists (os error 17)

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.

0 participants