Repository navigation
chore(deps): update cargo minor/patch updates - #1874
Merged
Merged
Conversation
Contributor
Author
|
Contributor
Merge Protections🟢 All 6 merge protections satisfied — ready to merge. Show 6 satisfied protections🟢 🤖 Continuous Integration
🟢 👀 Review Requirements
🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 Reviews
🟢 📕 PR description
🟢 🚦 Auto-queueWhen all merge protections are satisfied, this pull request will be queued automatically. |
Contributor
Merge Queue Status
This pull request spent 11 minutes 52 seconds in the queue, including 7 minutes 47 seconds running CI. Required conditions to merge
|
This was referenced Oct 5, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.56→0.580.58.5(+3)2.0.20→2.0.21Release Notes
Stranger6667/jsonschema (jsonschema)
v0.58.1Fixed
Pyo3validators when anEnummember'svalueoverride emptied a list or dict holding the instance being read.Performance
urianduri-referenceformats check the syntax directly instead of parsing each value into a URI.Enummembers read their stored value directly instead of calling thevalueproperty inPyo3validators.v0.58.0Added
backend = Pyo3on#[jsonschema::validator], generating a validator that reads Python objects in place.backend = Magnuson#[jsonschema::validator], generating a validator that reads Ruby objects in place.jsonschema::meta::pyo3, the bundled meta-schema validators for a schema held as a Python object.jsonschema::meta::magnus, the bundled meta-schema validators for a schema held as a Ruby object.methods = { ... }on#[jsonschema::validator], selecting which ofis_valid,validate, anditer_errorsare generated.json::Jsonb, validating a Postgresjsonbvalue in place, behind thejsonbfeature.Performance
oneOfandanyOfwhose branches each require a property fixed to a distinct string validate only the branch matching the instance's value.validatechecksrequiredin the same pass over an object asproperties, instead of looking up each required name.Fixed
oneOfover$refbranches beside a sibling none of them admits, which canonicalized to anallOfinstead offalse.multipleOfincorrectly accepted1e-400and other magnitudes below the smallestf64subnormal witharbitrary-precision(they are not zero).f64withoutarbitrary-precision.v0.57.0Added
PreparedDocument::unsatisfiable, naming the keywords that leave each unsatisfiable subschema empty and where they are.Changed
PreparedDocument::unsatisfiable_pointersis replaced byPreparedDocument::unsatisfiable.Fixed
PreparedDocument::unsatisfiable_pointerspassed over a subschema that admits no value only once its references resolve, such as anallOfover two$refs.Performance
dtolnay/thiserror (thiserror)
v2.0.21Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.