deps(deps): bump jsonschema from 0.47.0 to 0.56.0

[dependabot]

Bumps jsonschema from 0.47.0 to 0.56.0.

Release notes

Sourced from jsonschema's releases.

[Python] Release 0.56.0

Added

• canonical.RawReason, what stopped a run from modeling a document, and RawView.reason and RawView.pointer, carrying it beside the subschema the run stopped on.

Changed

• Canonicalization of a oneOf whose branches share a region too wide to expand, which spent the document's whole intersection allowance on that choice and kept the document Raw.

Performance

• Preparing or building a schema that names no base URI parses the default one once for the process instead of once per schema.
• Canonicalization reads the facets no checker covers once per node instead of once per containment query.

[Ruby] Release 0.56.0

Added

• JSONSchema::Canonical::RawReason, what stopped a run from modeling a document, and RawView#reason and RawView#pointer, carrying it beside the subschema the run stopped on.

Changed

• Canonicalization of a oneOf whose branches share a region too wide to expand, which spent the document's whole intersection allowance on that choice and kept the document Raw.

Performance

• Preparing or building a schema that names no base URI parses the default one once for the process instead of once per schema.
• Canonicalization reads the facets no checker covers once per node instead of once per containment query.

[Rust] Release 0.56.0

Added

• canonical::RawReason, what stopped a run from modeling a document, and canonical::RawView, carrying it beside the document and a pointer to the subschema the run stopped on.
• ValidationOptions::is_known_format, whether a format of that name is checked under a draft.

Changed

• BREAKING: canonical::CanonicalView::Raw carries a canonical::RawView in place of the document alone.
• Canonicalization of a oneOf whose branches share a region too wide to expand, which spent the document's whole intersection allowance on that choice and kept the document Raw.

Performance

• Preparing or building a schema that names no base URI parses the default one once for the process instead of once per schema.
• Canonicalizing several subschemas of one prepared document compiles each pattern once for the document instead of once per call.
• Canonicalization reads the facets no checker covers once per node instead of once per containment query.

[Python] Release 0.55.1

Changed

• Canonicalization of an anyOf over an allOf through a $ref to a union, which left that union nested inside the outer one.
• Canonicalization of an anyOf whose branch narrowing runs out of intersections, which left true as a branch inside the union.

... (truncated)

Changelog

Sourced from jsonschema's changelog.

[0.56.0] - 2026-09-10

Added

• canonical::RawReason, what stopped a run from modeling a document, and canonical::RawView, carrying it beside the document and a pointer to the subschema the run stopped on.
• ValidationOptions::is_known_format, whether a format of that name is checked under a draft.

Changed

• BREAKING: canonical::CanonicalView::Raw carries a canonical::RawView in place of the document alone.
• Canonicalization of a oneOf whose branches share a region too wide to expand, which spent the document's whole intersection allowance on that choice and kept the document Raw.

Performance

• Preparing or building a schema that names no base URI parses the default one once for the process instead of once per schema.
• Canonicalizing several subschemas of one prepared document compiles each pattern once for the document instead of once per call.
• Canonicalization reads the facets no checker covers once per node instead of once per containment query.

[0.55.1] - 2026-09-08

Changed

• Canonicalization of an anyOf over an allOf through a $ref to a union, which left that union nested inside the outer one.
• Canonicalization of an anyOf whose branch narrowing runs out of intersections, which left true as a branch inside the union.

[0.55.0] - 2026-09-06

Changed

• BREAKING: canonical::ObjectViolationView gained the PatternValueFails variant, which negation records for a patternProperties entry.
• Canonicalization of not over patternProperties, which kept the entry under not instead of recording the demand a key breaks.
• Canonicalization of unevaluated* beside a conditional reaching no key or index the node already evaluates, which spent a case on it.
• Canonicalization of a conditional split outgrowing its per-node case budget, which kept documents like the Open API 3.2 meta-schema Raw.
• Canonicalization of an anyOf over objects sharing a properties key under patternProperties, which settled only on a second pass.
• Canonicalization of not over an allOf folded through a reference, which settled only on a second pass.
• Canonicalization of a multipleOf divisor past f64 precision, which was not taken to divide itself.
• Canonicalization of an anyOf over a value beside a window pinned to it, which settled only on a second pass.
• Canonicalization of minProperties: 1 beside a not that already demands a key, which settled only on a second pass.

Fixed

• absolute_keyword_location naming the sibling keyword whose validator carries the check: maxLength beside minLength, minItems, maxItems or type beside items, and a two-name required beside properties. #1579
• schemaLocation in evaluate output naming minLength for a maxLength failure. #1579

[0.54.0] - 2026-09-06

Added

• backend = SerdeJson on #[jsonschema::validator], generating a validator that reads serde_json::Value.
• PreparedDocument::unsatisfiable_pointers, listing every subschema no value satisfies.

... (truncated)

Commits

• c5ce51d chore(ruby): Release 0.56.0
• 1e244c9 chore(rust): Release 0.56.0
• 507d66a build: Switch to weekly dependabot
• 7762942 build: Increase timeout for s390x test job
• 7d4b40d test: Update hegeltest to 0.41
• b2622e5 build(deps): bump taiki-e/install-action from 2.87.3 to 2.87.8
• c983788 build(deps): update wasm-bindgen requirement from =0.2.127 to =0.2.128
• 6e7e8f6 build(deps): bump crates/jsonschema/tests/suite
• 3f2c0a0 perf: Preparing or building a schema that names no base URI parses the defaul...
• 2b4f25b perf: More benchmarks
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: rust. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: c012d320-797a-4095-b6b4-73347f7ef9a8

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

🔍 The Case of Pull Request #800

Schema Sets

• ecommerce
• reference

Schema Set ecommerce

Plain-English Readout

• Holmes (evidence investigation): The Holmes report is unavailable because the workflow finished without a readable holmes-report.json artifact.
• Watson (independent verification): The Watson report is unavailable because the workflow finished without a readable watson-report.json artifact.
• Moriarty (trend forecast): The Moriarty forecast is unavailable because the workflow finished without a readable moriarty-report.json artifact.

Suggested next actions

1. Regenerate the HOLMES artifacts and make sure holmes-report.json is uploaded before trusting this PR summary.
2. Regenerate the WATSON artifacts and make sure watson-report.json is uploaded before trusting this PR summary.
3. Regenerate the MORIARTY artifacts and make sure moriarty-report.json is uploaded before trusting this PR summary.

🕵️ SHA-lock HOLMES full report for ecommerce (click to expand)

Report unavailable for holmes: readable holmes-report.md artifact not found.

🩺 Dr. WATSON full report for ecommerce (click to expand)

Report unavailable for watson: readable watson-report.md artifact not found.

🔮 Professor MORIARTY full report for ecommerce (click to expand)

Report unavailable for moriarty: readable moriarty-report.md artifact not found.

---

Schema Set reference

Plain-English Readout

• Holmes (evidence investigation): The Holmes report is unavailable because the workflow finished without a readable holmes-report.json artifact.
• Watson (independent verification): The Watson report is unavailable because the workflow finished without a readable watson-report.json artifact.
• Moriarty (trend forecast): The Moriarty forecast is unavailable because the workflow finished without a readable moriarty-report.json artifact.

Suggested next actions

1. Regenerate the HOLMES artifacts and make sure holmes-report.json is uploaded before trusting this PR summary.
2. Regenerate the WATSON artifacts and make sure watson-report.json is uploaded before trusting this PR summary.
3. Regenerate the MORIARTY artifacts and make sure moriarty-report.json is uploaded before trusting this PR summary.

🕵️ SHA-lock HOLMES full report for reference (click to expand)

Report unavailable for holmes: readable holmes-report.md artifact not found.

🩺 Dr. WATSON full report for reference (click to expand)

Report unavailable for watson: readable watson-report.md artifact not found.

🔮 Professor MORIARTY full report for reference (click to expand)

Report unavailable for moriarty: readable moriarty-report.md artifact not found.

---

📚 Glossary (what the Holmes terms mean)

• HOLMES: Wesley’s main evidence investigation. It decides whether the cited proof is strong enough to justify shipping this commit.
• WATSON: An independent verification pass. It checks Holmes’s citations and score math instead of trusting them blindly.
• MORIARTY: A readiness forecast over time. It is advisory trend analysis, not the release gate itself.
• Schema coverage score (SCS): How much of the schema has direct supporting evidence across generated artifacts and cited proof.
• Test confidence index (TCI): How much test evidence exists for constraints, policies, relationships, and operations.
• Migration risk index (MRI): How risky the schema change is to roll out. Lower is better.
• Evidence trust: Whether the report is backed by exact citations, whole-file citations, or coarse references. Weak trust means the claim may be directionally right but not specific enough to trust blindly.
• Citation quality: A count of exact line-span citations versus whole-file or coarse references.
• ELEMENTARY: Ready to ship based on the current evidence.
• REQUIRES INVESTIGATION: More work or review is needed before shipping.
• YOU SHALL NOT PASS: Do not ship this change in its current state.

---

Machine-readable reports are grouped by schema set in workflow artifacts.

---

Filed at 221B Repository Street