deps(deps): bump jsonschema from 0.47.0 to 0.49.7

[dependabot]

Bumps jsonschema from 0.47.0 to 0.49.7.

Release notes

Sourced from jsonschema's releases.

[Python] Release 0.49.7

Added

• retriever, registry, and base_uri arguments to canonicalize.
• Canonicalization of a oneOf whose branches name disjoint targets, which degrades to a union.
• Canonicalization of a vacuous patternProperties entry beside schema-valued additionalProperties, where matching keys escape its value constraint.
• Canonicalization of a Draft 4 closed pattern map with a reference nested under a property.
• Canonicalization of Draft 4 closed pattern maps that meet through an applicator.
• The complement of a reference back to a target already being negated, which stays symbolic instead of declining.
• CanonicalSchema.definition resolving # to the document the schema was read against.

Performance

• Up to 150x faster canonicalization of not over a union of many branches.
• 2% faster emission of canonical schemas, which no longer formats copied string values.
• 5% faster emission of canonical schemas, which no longer formats object keys while copying them.
• Up to 12% faster canonicalization of schemas that repeatedly intersect the same branches.
• 13% faster canonicalization of a non-dynamic OpenAPI document, which no longer scans every schema object for dynamic references.
• Faster canonicalization of schemas with local $defs references, which avoid decoding unescaped definition names.
• 23% faster canonicalization of an object whose keys a finite property-name set spells.
• 3% faster intersection of schemas where one side constrains nothing.
• Up to 31x faster canonicalization of a oneOf whose many branches overlap.
• Up to 14x faster canonicalization of a union whose object branches share no values.
• 7% faster canonicalization of schemas that reach the same pair of nodes repeatedly.
• 5% faster canonicalization of objects, whose property maps no longer reach the allocator.
• Up to 8% faster canonicalization of schemas that reach true and false subschemas repeatedly.
• 2% faster canonicalization of schemas that assert known string formats.

Fixed

• CanonicalSchema.definition and CanonicalSchema.definitions handing out a target that names the document root without that document, where # points at the target instead.
• An items tail beyond an array's length ceiling surviving canonicalization, where it governs no element.
• CanonicalSchema.to_json_schema leaving the document root out of a node emitted below it, where # points at that node instead.

[Ruby] Release 0.49.7

Added

• retriever, registry, and base_uri keyword arguments to JSONSchema.canonicalize.
• Canonicalization of a oneOf whose branches name disjoint targets, which degrades to a union.
• Canonicalization of a vacuous patternProperties entry beside schema-valued additionalProperties, where matching keys escape its value constraint.
• Canonicalization of a Draft 4 closed pattern map with a reference nested under a property.
• Canonicalization of Draft 4 closed pattern maps that meet through an applicator.
• The complement of a reference back to a target already being negated, which stays symbolic instead of declining.
• CanonicalSchema#definition resolving # to the document the schema was read against.

Performance

• Up to 150x faster canonicalization of not over a union of many branches.
• 2% faster emission of canonical schemas, which no longer formats copied string values.
• 5% faster emission of canonical schemas, which no longer formats object keys while copying them.

... (truncated)

Changelog

Sourced from jsonschema's changelog.

[0.49.7] - 2026-08-07

Added

• CanonicalizeOptions::with_retriever to fetch external resources absent from the registry.
• CanonicalizeOptions::with_base_uri to resolve relative references in the root schema.
• Canonicalization of a oneOf whose branches name disjoint targets, which degrades to a union.
• Canonicalization of a vacuous patternProperties entry beside schema-valued additionalProperties, where matching keys escape its value constraint.
• Canonicalization of a Draft 4 closed pattern map with a reference nested under a property.
• Canonicalization of Draft 4 closed pattern maps that meet through an applicator.
• The complement of a reference back to a target already being negated, which stays symbolic instead of declining.
• CanonicalSchema::definition resolving # to the document the handle was read against.

Performance

• Up to 150x faster canonicalization of not over a union of many branches.
• 2% faster emission of canonical schemas, which no longer formats copied string values.
• 5% faster emission of canonical schemas, which no longer formats object keys while copying them.
• Up to 12% faster canonicalization of schemas that repeatedly intersect the same branches.
• 13% faster canonicalization of a non-dynamic OpenAPI document, which no longer scans every schema object for dynamic references.
• Faster canonicalization of schemas with local $defs references, which avoid decoding unescaped definition names.
• 23% faster canonicalization of an object whose keys a finite property-name set spells.
• 3% faster intersection of schemas where one side constrains nothing.
• Up to 31x faster canonicalization of a oneOf whose many branches overlap.
• Up to 14x faster canonicalization of a union whose object branches share no values.
• 7% faster canonicalization of schemas that reach the same pair of nodes repeatedly.
• 5% faster canonicalization of objects, whose property maps no longer reach the allocator.
• Up to 8% faster canonicalization of schemas that reach true and false subschemas repeatedly.
• 2% faster canonicalization of schemas that assert known string formats.

Fixed

• CanonicalSchema::definition and CanonicalSchema::definitions handing out a target that names the document root without that document, where # points at the target instead.
• An items tail beyond an array's length ceiling surviving canonicalization, where it governs no element.
• CanonicalSchema::to_json_schema leaving the document root out of a node emitted below it, where # points at that node instead.

[0.49.6] - 2026-08-06

Added

• Canonicalization of a negated uniqueItems, where the complement demands a repeated element under the length floor two elements imply.
• Canonicalization of a negated array tuple, where each position's complement stands under the length that reaches it.
• Canonicalization of contains demands sharing no value, where their counts add up into a length floor.
• CanonicalSchema::negate through references, where the complement of the resolved target takes the reference's place.
• Canonicalization of negated propertyNames and additionalProperties, where the complement spells the violating-key demand instead of a not residual.
• Canonicalization of negated additionalProperties under Draft 4, where the violating-key demand spells the closed property map.
• Canonicalization of not a reference, where the complement of the resolved target takes the pointer's place.
• Canonicalization of a negated oneOf, where the complement spells the values no branch admits beside the values two branches share.
• Canonicalization of negated items under Draft 4, where the violating-element demand spells the barred element schema.

... (truncated)

Commits

• 64df261 chore(ruby): Release 0.49.7
• ef60bb9 chore(python): Release 0.49.7
• b02e0d6 chore(rust): Release 0.49.7
• 6b2a720 fix: CanonicalSchema::to_json_schema leaving the document root out of a nod...
• a3c2d02 feat: CanonicalSchema::definition resolving # to the document the handle ...
• 70f9bda fix: An items tail beyond an array's length ceiling surviving canonicalizat...
• 515bcfd feat: The complement of a reference back to a target already being negated, w...
• 5b297ea feat: Canonicalization of Draft 4 closed pattern maps that meet through an ap...
• 91fa948 feat: Canonicalization of a Draft 4 closed pattern map with a reference neste...
• 7593bfd docs: Update changelogs
• 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 #781

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