Update Rust crate schemars to v1 #214
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/schemars-1.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
0.8.22
->1.0.4
Release Notes
GREsau/schemars (schemars)
v1.0.4
Compare Source
Fixed
JsonSchema
impl on atomic types being ignored on non-nightly compilers due to a buggycfg
check (https://github.com/GREsau/schemars/issues/453)syn
(https://github.com/GREsau/schemars/issues/450)v1.0.3
Compare Source
Fixed
transparent
(or newtype) struct and its field (https://github.com/GREsau/schemars/issues/446)json_schema!()
macro compatibility when used from pre-2021 rust editions (https://github.com/GREsau/schemars/pull/447)v1.0.2
Compare Source
Fixed
v1.0.1
Compare Source
Fixed
JsonSchema
withno_std
broken due tostd::borrow::ToOwned
trait not being in scope (https://github.com/GREsau/schemars/issues/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 usingschema_for!()
orSchemaGenerator
) 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 containersSchema::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
$ref
value (https://github.com/GREsau/schemars/pull/436)SchemaGenerator::subschema_for
, reducing LLVM line count and improving compile times (https://github.com/GREsau/schemars/pull/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: Enabled.
♻ 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.
This PR has been generated by Renovate Bot.
⚠️ 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:
The artifact failure details are included below:
File name: Cargo.lock
50d59558fd
to0c7f1b64ed
0c7f1b64ed
to9661821dbf
9661821dbf
tof81fe3f546
f81fe3f546
todb90f2264d
db90f2264d
to27cac2c0d9
27cac2c0d9
toab094fd6d6
ab094fd6d6
to5425691206
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.