martin/recurring-events
Watch
1
0
Fork
You've already forked recurring-events
 0
Code Issues 1 Pull requests 2 Projects Releases Packages Wiki Activity Actions

fix(deps): update rust crate jsonschema to 0.52 #39

Open
clank-bot wants to merge 1 commit from renovate/dependencies-(non-major) into master
pull from: renovate/dependencies-(non-major)
merge into: martin:master
Conversation 0 Commits 1 Files changed 2 +11 -12
clank-bot commented 2026-08-24 00:04:11 +00:00
Collaborator
Copy link

This PR contains the following updates:

Package Type Update Change
jsonschema dependencies minor 0.50 → 0.52

Release Notes

Stranger6667/jsonschema (jsonschema)

v0.52.0

Added
  • Evaluation::is_valid.
  • Location::is_empty.
  • Display for ErrorEntry.
  • ValidationOptions::offline and canonical::CanonicalizeOptions::offline, refusing to fetch references outside the registry.
  • idna Cargo feature, enabled by default, gating the idn-hostname and idn-email formats. #​1313
  • CLI: the --offline flag of jsonschema validate, jsonschema bundle and jsonschema dereference.
Changed
  • ValidationErrors' Display gained the instance path of each error.
Fixed
  • Canonicalization not idempotent where a patternProperties $ref matches a key properties names.
  • is_valid disagreeing with validate, iter_errors, and evaluate on a schema that reaches its own $ref twice, one of them under not.
  • format: email and format: idn-email rejecting an empty quoted string as the local part (it should be accepted).
  • format: email and format: idn-email rejecting an address literal whose IPv6: tag is not written in that exact case (the tag is case-insensitive).
  • format: email accepting a non-ASCII character in the local part (it should be rejected).
  • ValidationOptions::with_draft gating keywords on the vocabularies of the $schema it overrides, so the validator accepted every instance.
Performance
  • iter_errors collects into a single buffer instead of allocating and re-boxing an iterator at every schema node.

v0.51.0

Added
  • ValidationOptions::with_vocabulary and the vocabularies attribute on jsonschema::validator, declaring support for a vocabulary this crate does not implement.
  • The --vocabulary flag of jsonschema validate.
Changed
  • Vocabulary gained the FormatAssertion variant, which its Draft 2020-12 URI parses to instead of Vocabulary::Custom, and is marked non_exhaustive.
Fixed
  • The uniqueItems length ceiling not reading an items or contains schema written as a $ref.
  • The Draft 2020-12 Format-Assertion vocabulary read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • An unrecognized format accepted under a meta-schema requiring the Format-Assertion vocabulary (it should be rejected).
  • A meta-schema requiring a vocabulary this crate does not implement accepted (it should be rejected).
  • The Draft 2019-09 Format vocabulary declared true read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • The bundled https://json-schema.org/draft/2020-12/meta/format-assertion meta-schema not declaring its vocabulary, so a schema written against it annotated format instead of asserting it.
  • A meta-schema without $id keeping its $vocabulary unread, so a schema written against it got every Draft 2020-12 vocabulary.
  • A schema naming a bundled vocabulary meta-schema as its $schema rejected as an unknown meta-schema (it should build).
  • The regex format reading the Rust regex dialect (it should read the ECMA-262 dialect in Unicode mode).
  • The uri-template format rejecting an apostrophe in a literal (it should accept it, per RFC 6570 errata 6937).
  • The duration format accepting weeks combined with a time part, such as P1WT1H (it should reject it).
  • Stack overflow compiling unevaluatedProperties or unevaluatedItems beside a $ref that cycles back to the node, written as #, through its $id, or through a chain of definitions.
Performance
  • Building unevaluatedProperties or unevaluatedItems over a deep allOf or $ref chain costs its depth instead of its square.

Configuration

📅 Schedule: (UTC)

  • 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 has been generated by Mend Renovate.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [jsonschema](https://github.com/Stranger6667/jsonschema) | dependencies | minor | `0.50` → `0.52` | --- ### Release Notes <details> <summary>Stranger6667/jsonschema (jsonschema)</summary> ### [`v0.52.0`](https://github.com/Stranger6667/jsonschema/blob/HEAD/CHANGELOG.md#0520---2026-08-26) ##### Added - `Evaluation::is_valid`. - `Location::is_empty`. - `Display` for `ErrorEntry`. - `ValidationOptions::offline` and `canonical::CanonicalizeOptions::offline`, refusing to fetch references outside the registry. - `idna` Cargo feature, enabled by default, gating the `idn-hostname` and `idn-email` formats. [#&#8203;1313](https://github.com/Stranger6667/jsonschema/issues/1313) - **CLI**: the `--offline` flag of `jsonschema validate`, `jsonschema bundle` and `jsonschema dereference`. ##### Changed - `ValidationErrors`' `Display` gained the instance path of each error. ##### Fixed - Canonicalization not idempotent where a `patternProperties` `$ref` matches a key `properties` names. - `is_valid` disagreeing with `validate`, `iter_errors`, and `evaluate` on a schema that reaches its own `$ref` twice, one of them under `not`. - `format: email` and `format: idn-email` rejecting an empty quoted string as the local part (it should be accepted). - `format: email` and `format: idn-email` rejecting an address literal whose `IPv6:` tag is not written in that exact case (the tag is case-insensitive). - `format: email` accepting a non-ASCII character in the local part (it should be rejected). - `ValidationOptions::with_draft` gating keywords on the vocabularies of the `$schema` it overrides, so the validator accepted every instance. ##### Performance - `iter_errors` collects into a single buffer instead of allocating and re-boxing an iterator at every schema node. ### [`v0.51.0`](https://github.com/Stranger6667/jsonschema/blob/HEAD/CHANGELOG.md#0510---2026-08-23) ##### Added - `ValidationOptions::with_vocabulary` and the `vocabularies` attribute on `jsonschema::validator`, declaring support for a vocabulary this crate does not implement. - The `--vocabulary` flag of `jsonschema validate`. ##### Changed - `Vocabulary` gained the `FormatAssertion` variant, which its Draft 2020-12 URI parses to instead of `Vocabulary::Custom`, and is marked `non_exhaustive`. ##### Fixed - The `uniqueItems` length ceiling not reading an `items` or `contains` schema written as a `$ref`. - The Draft 2020-12 Format-Assertion vocabulary read as an annotation, so a meta-schema requiring it accepted values its `format` rejects. - An unrecognized `format` accepted under a meta-schema requiring the Format-Assertion vocabulary (it should be rejected). - A meta-schema requiring a vocabulary this crate does not implement accepted (it should be rejected). - The Draft 2019-09 Format vocabulary declared `true` read as an annotation, so a meta-schema requiring it accepted values its `format` rejects. - The bundled `https://json-schema.org/draft/2020-12/meta/format-assertion` meta-schema not declaring its vocabulary, so a schema written against it annotated `format` instead of asserting it. - A meta-schema without `$id` keeping its `$vocabulary` unread, so a schema written against it got every Draft 2020-12 vocabulary. - A schema naming a bundled vocabulary meta-schema as its `$schema` rejected as an unknown meta-schema (it should build). - The `regex` format reading the Rust regex dialect (it should read the ECMA-262 dialect in Unicode mode). - The `uri-template` format rejecting an apostrophe in a literal (it should accept it, per RFC 6570 errata 6937). - The `duration` format accepting weeks combined with a time part, such as `P1WT1H` (it should reject it). - Stack overflow compiling `unevaluatedProperties` or `unevaluatedItems` beside a `$ref` that cycles back to the node, written as `#`, through its `$id`, or through a chain of definitions. ##### Performance - Building `unevaluatedProperties` or `unevaluatedItems` over a deep `allOf` or `$ref` chain costs its depth instead of its square. </details> --- ### Configuration 📅 **Schedule**: (UTC) - 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xNTAuMSIsInVwZGF0ZWRJblZlciI6IjQzLjE1MC4xIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbImRlcGVuZGVuY2llcyJdfQ==-->
fix(deps): update rust crate jsonschema to 0.51
All checks were successful
ci/woodpecker/pr/pr-review Pipeline was successful
Details
ci/woodpecker/pr/global-rust-generate-verify Pipeline was successful
Details
407c8a8cf7
clank-bot force-pushed renovate/dependencies-(non-major) from 407c8a8cf7
All checks were successful
ci/woodpecker/pr/pr-review Pipeline was successful
Details
ci/woodpecker/pr/global-rust-generate-verify Pipeline was successful
Details
to 505a93e331
All checks were successful
ci/woodpecker/pr/pr-review Pipeline was successful
Details
ci/woodpecker/pr/global-rust-generate-verify Pipeline was successful
Details
2026-08-27 00:02:50 +00:00 Compare
clank-bot changed title from fix(deps): update rust crate jsonschema to 0.51 to fix(deps): update rust crate jsonschema to 0.52 2026-08-27 00:02:51 +00:00
All checks were successful
ci/woodpecker/pr/pr-review Pipeline was successful
Details
ci/woodpecker/pr/global-rust-generate-verify Pipeline was successful
Details
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/dependencies-(non-major):renovate/dependencies-(non-major)
git switch renovate/dependencies-(non-major)

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch master
git merge --no-ff renovate/dependencies-(non-major)
git switch renovate/dependencies-(non-major)
git rebase master
git switch master
git merge --ff-only renovate/dependencies-(non-major)
git switch renovate/dependencies-(non-major)
git rebase master
git switch master
git merge --no-ff renovate/dependencies-(non-major)
git switch master
git merge --squash renovate/dependencies-(non-major)
git switch master
git merge --ff-only renovate/dependencies-(non-major)
git switch master
git merge renovate/dependencies-(non-major)
git push origin master
Sign in to join this conversation.
Reviewers
No reviewers
martin
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
martin/recurring-events!39
No description provided.