[dependabot]

Bumps jsonschema from 0.47.0 to 0.58.0.

Release notes

Sourced from jsonschema's releases.

[Python] Release 0.58.0

Performance

• oneOf and anyOf whose branches each require a property fixed to a distinct string validate only the branch matching the instance's value.
• meta.is_valid and meta.validate check a schema against the bundled drafts without converting it first, about 2x faster on the benchmarked schemas.

Fixed

• Crash on free-threaded Python when another thread resized a list or dict during validation.
• find_unsatisfiable missing a oneOf over $ref branches beside a sibling none of them admits.

[Ruby] Release 0.58.0

Performance

• oneOf and anyOf whose branches each require a property fixed to a distinct string validate only the branch matching the instance's value.
• Meta.valid? and Meta.validate! check a schema against the bundled drafts without converting it first, 2 to 5x faster on the benchmarked schemas.

Fixed

• Canonical.find_unsatisfiable missing a oneOf over $ref branches beside a sibling none of them admits.
• A value with no JSON form nested under type: null failing validation silently (it should raise TypeError).

[Rust] Release 0.58.0

Added

• backend = Pyo3 on #[jsonschema::validator], generating a validator that reads Python objects in place.
• backend = Magnus on #[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 of is_valid, validate, and iter_errors are generated.
• json::Jsonb, validating a Postgres jsonb value in place, behind the jsonb feature.

Performance

• oneOf and anyOf whose branches each require a property fixed to a distinct string validate only the branch matching the instance's value.
• Generated validate checks required in the same pass over an object as properties, instead of looking up each required name.

Fixed

• A oneOf over $ref branches beside a sibling none of them admits, which canonicalized to an allOf instead of false.
• multipleOf incorrectly accepted 1e-400 and other magnitudes below the smallest f64 subnormal with arbitrary-precision (they are not zero).
• Numeric keywords panicked on a custom representation holding a number past f64 without arbitrary-precision.

[Python] Release 0.57.1

Fixed

• Packaging issue.

[Ruby] Release 0.57.0

Added

... (truncated)

Changelog

Sourced from jsonschema's changelog.

[0.58.0] - 2026-09-25

Added

• backend = Pyo3 on #[jsonschema::validator], generating a validator that reads Python objects in place.
• backend = Magnus on #[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 of is_valid, validate, and iter_errors are generated.
• json::Jsonb, validating a Postgres jsonb value in place, behind the jsonb feature.

Performance

• oneOf and anyOf whose branches each require a property fixed to a distinct string validate only the branch matching the instance's value.
• Generated validate checks required in the same pass over an object as properties, instead of looking up each required name.

Fixed

• A oneOf over $ref branches beside a sibling none of them admits, which canonicalized to an allOf instead of false.
• multipleOf incorrectly accepted 1e-400 and other magnitudes below the smallest f64 subnormal with arbitrary-precision (they are not zero).
• Numeric keywords panicked on a custom representation holding a number past f64 without arbitrary-precision.

[0.57.0] - 2026-09-22

Added

• PreparedDocument::unsatisfiable, naming the keywords that leave each unsatisfiable subschema empty and where they are.

Changed

• PreparedDocument::unsatisfiable_pointers is replaced by PreparedDocument::unsatisfiable.

Fixed

• The instance path of a schema build error, which was empty instead of naming the keyword location that failed to compile.
• PreparedDocument::unsatisfiable_pointers passed over a subschema that admits no value only once its references resolve, such as an allOf over two $refs.

Performance

• Canonicalizing several subschemas of one prepared document parses each definition body once for the document instead of once per call.

[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

... (truncated)

Commits

• 894beed chore(ruby): Release 0.58.0
• ad33f36 chore(rust): Release 0.58.0
• 84ec127 docs: Update FHIR benchmark numbers
• 91ac6fa perf: Validate only the matching branch of discriminated oneOf and anyOf
• cb40352 perf: Reject undeclared properties before validating values
• 6e9859f perf: Benchmarks for jsonb instances
• 91fd2eb perf: Tune Ruby benchmark
• fc7502e test: Run the JSON Schema Test Suite over jsonb instances
• 1394de9 feat: Validating Postgres jsonb values in place
• 87b9933 test: Postgres jsonb corpus and live differential tests
• 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: Repository: flyingrobots/wesley/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 82b0082b-8d92-451a-b452-fc7ad1ea9fe2

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 #840

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

[dependabot]

Superseded by #841.