deps(deps): bump jsonschema from 0.47.0 to 0.50.1

[dependabot]

Bumps jsonschema from 0.47.0 to 0.50.1.

Release notes

Sourced from jsonschema's releases.

[Python] Release 0.50.1

Added

• str() on Containment, Satisfiability, Distinctness and CanonicalKind members reads as the label.

Changed

• CanonicalSchema.satisfiability() answers YES for a string whose pattern or format a matching value can be built from.
• CanonicalSchema.satisfiability() answers NO where a format takes no string of the length the schema asks for.

Fixed

• CanonicalSchema.negate() taking apart a union that reads a definition through its own if, so a schema and its negation shared a value.
• CanonicalSchema.subtract() dropping a Draft 4 array member an element demand partly takes.
• CanonicalSchema.covers() answering Yes where a Draft 4 element demand refuses a member.
• A string schema whose maxLength is 0 keeping a pattern, format, or content facet unread, so the same constraints written in one object and written as an allOf reached different canonical forms.

Performance

• not over a wide object schema costs its branch count instead of its square.
• not over an object schema is linear in its property count, not quadratic.
• not over an object schema with additionalProperties: false no longer costs cubic time in its property count.

[Ruby] Release 0.50.1

Changed

• CanonicalSchema#satisfiability answers :yes for a string whose pattern or format a matching value can be built from.
• CanonicalSchema#satisfiability answers :no where a format takes no string of the length the schema asks for.

Fixed

• CanonicalSchema#negate taking apart a union that reads a definition through its own if, so a schema and its negation shared a value.
• CanonicalSchema#subtract dropping a Draft 4 array member an element demand partly takes.
• CanonicalSchema#covers answering Yes where a Draft 4 element demand refuses a member.
• A string schema whose maxLength is 0 keeping a pattern, format, or content facet unread, so the same constraints written in one object and written as an allOf reached different canonical forms.

Performance

• not over a wide object schema costs its branch count instead of its square.
• not over an object schema is linear in its property count, not quadratic.
• not over an object schema with additionalProperties: false no longer costs cubic time in its property count.

[Rust] Release 0.50.1

Changed

• CanonicalSchema::satisfiability answers Yes for a string whose pattern or format a matching value can be built from.
• CanonicalSchema::satisfiability answers No where a format takes no string of the length the schema asks for.

Fixed

... (truncated)

Changelog

Sourced from jsonschema's changelog.

[0.50.1] - 2026-08-22

Changed

• CanonicalSchema::satisfiability answers Yes for a string whose pattern or format a matching value can be built from.
• CanonicalSchema::satisfiability answers No where a format takes no string of the length the schema asks for.

Fixed

• CanonicalSchema::negate taking apart a union that reads a definition through its own if, so a schema and its negation shared a value.
• CanonicalSchema::subtract dropping a Draft 4 array member an element demand partly takes.
• CanonicalSchema::covers answering Yes where a Draft 4 element demand refuses a member.
• A string schema whose maxLength is 0 keeping a pattern, format, or content facet unread, so the same constraints written in one object and written as an allOf reached different canonical forms.

Performance

• not over a wide object schema costs its branch count instead of its square.
• not over an object schema is linear in its property count, not quadratic.
• not over an object schema with additionalProperties: false no longer costs cubic time in its property count.

[0.50.0] - 2026-08-20

Added

• CanonicalSchema::union and CanonicalSchema::subtract.
• CanonicalizationError::UnsupportedResult, reported where the canonical form does not support a set operation's result.
• OperandMismatch::DocumentRoots, reported where both operands read # and it names a different document on each side.
• CLI: jsonschema validate -i INSTANCE without a SCHEMA argument validates each instance against the schema named in its own $schema property. #1470

Changed

• CanonicalSchema::is_satisfiable is now CanonicalSchema::satisfiability, answering Yes, No, or Unknown - Yes wherever a value can be exhibited, not only for the forms listing their members.
• CanonicalSchema::covers decides through the difference as well: No where the argument keeps values the receiver rejects, Yes where nothing is left over.
• CanonicalSchema::is_subset_of is now CanonicalSchema::covers, answering Yes, No, or Unknown for whether the receiver admits every value the argument admits.
• CanonicalSchema::negate returns Result rather than Option.
• CanonicalizationError::UnmodeledOperand is now CanonicalizationError::UnsupportedOperand, and means only that an operand is a Raw pass-through.
• A conjunction over a $ref folds through the body it names, so canonicalizing a document and combining its parts with the set operations reach one form; a document holding a reference cycle keeps the form it had.

Fixed

• Combining nodes of two different documents repointing a $ref to # at the combined result instead of the document it was written in, including one named by a definition the result keeps.
• Intersecting a $ref whose target is true or false, which panicked.
• A key constraint left un-narrowed once a run is out of intersections, which panicked on the next read of it.
• CanonicalSchema::covers answering Unknown for a schema against itself, where that schema is a $ref.
• CanonicalSchema::union keeping a $ref beside the schema it names, where the other three operations read through it.
• CanonicalSchema::covers and CanonicalSchema::subtract cancelling two nodes written the same way whose # names a different document.
• Two results accepting the same values comparing unequal over the part of their documents neither reads.
• additionalProperties reaching a key the pattern map matches when a finite key constraint closes the map, which dropped values both operands accept.
• A recursive definition stopping every other pointer in the document from being read through.
• One $defs entry read past a wider schema written out at every use, rather than kept as the pointer it was.

... (truncated)

Commits

• 5993cf1 chore(ruby): Release 0.50.1
• e04ecc6 build(ruby): Exclude arm-linux-musl
• 1fc21b9 chore(python): Release 0.50.1
• 60a563d chore(rust): Release 0.50.1
• 0bce52e fix: CanonicalSchema::negate taking apart a union that reads a definition t...
• 3cabc18 perf: not over a wide object schema costs its branch count instead of its s...
• ed3ff96 perf: not over an object schema with additionalProperties: false no longe...
• fad8ed4 perf: not over an object schema is linear in its property count, not quadratic
• b646078 fix: CanonicalSchema::covers answering Yes where a Draft 4 element demand...
• d1b873d fix: A string schema whose maxLength is 0 keeping a pattern, format, ...
• 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.

[github-actions]

🔍 The Case of Pull Request #787

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 #789.