deps(deps): bump jsonschema from 0.47.0 to 0.49.2

[dependabot]

Bumps jsonschema from 0.47.0 to 0.49.2.

Release notes

Sourced from jsonschema's releases.

[Python] Release 0.49.2

Fixed

• Canonical numeric bounds no float can hold are exposed as decimal.Decimal instead of a rounded, wider bound.

Performance

• Faster serialization of canonicalized schemas.
• Up to 70x faster canonicalize for multipleOf beside numeric bounds far from zero.

[Rust] Release 0.49.2

Performance

• Faster serialization of canonicalized schemas.
• Faster macro code generation for subschemas with many keywords.
• Up to 70x faster canonicalization of multipleOf beside numeric bounds far from zero.

[Python] Release 0.49.1

Fixed

• canonicalize rejecting pattern_options (it should take the same regex configuration as validators).

[Ruby] Release 0.49.1

Fixed

• JSONSchema.canonicalize rejecting pattern_options (it should take the same regex configuration as validators).
• InvalidPattern failures raising the base CanonicalizationError (they should raise JSONSchema::Canonical::InvalidPattern).

[Rust] Release 0.49.1

Fixed

• jsonschema-value: Ruby builds on x64-mingw-ucrt.

[Python] Release 0.49.0

Added

• Validation of recursive Python objects. #945
• EXPERIMENTAL: Schema canonicalization via jsonschema::canonicalize. It reduces a reasonable subset of JSON Schemas to their normal forms.

Fixed

• multipleOf incorrectly accepted integers past u64 that are not multiples of the divisor.
• list subclasses incorrectly rejected as unsupported types.
• Segmentation fault on enum members whose value resolves back to the member.

Performance

• Up to 5x faster validation by working on Python objects directly instead of converting them to serde_json. #239
• Up to 2x faster meta.is_valid / meta.validate by working on Python objects directly instead of converting them to serde_json.

... (truncated)

Changelog

Sourced from jsonschema's changelog.

[0.49.2] - 2026-07-28

Performance

• Faster serialization of canonicalized schemas.
• Faster macro code generation for subschemas with many keywords.
• Up to 70x faster canonicalization of multipleOf beside numeric bounds far from zero.

[0.49.1] - 2026-07-25

Fixed

• jsonschema-value: Ruby builds on x64-mingw-ucrt.

[0.49.0] - 2026-07-25

Added

• Generic JSON input: options_for builds a validator over any instance representation implementing json::Json, so instances validate without conversion to serde_json::Value. #239
• meta::validate_for and meta::is_valid_for for checking a schema document held in any representation implementing json::Json against its meta-schema.
• EXPERIMENTAL: Schema canonicalization via jsonschema::canonicalize. It reduces a reasonable subset of JSON Schemas to their normal forms.

Fixed

• multipleOf incorrectly accepted integers past u64 that are not multiples of the divisor.

[0.48.5] - 2026-07-22

Fixed

• Packaging issue again.

[0.48.4] - 2026-07-22

Fixed

• Packaging issue.

[0.48.3] - 2026-07-22

Changed

• INTERNAL. Extract common JSON Schema semantic into a separate jsonschema-value crate.

Performance

• Avoid map lookups in some properties validators.
• Faster validation of {"type": "array", "items": {...}} schemas.

[0.48.2] - 2026-07-21

... (truncated)

Commits

• 3fe5c3b chore(ruby): Release 0.49.2
• c9ef386 chore(python): Release 0.49.2
• d85e5f2 chore(rust): Release 0.49.2
• f9040ec perf: Up to 70x faster canonicalization of multipleOf beside numeric bounds...
• 21a3272 perf: Use arbitrary-precision for canonicalization benchmarks
• 9cdec99 perf: Faster macro code generation for subschemas with many keywords
• fad0015 perf: Tune codegen benchmarks
• 8d23dd2 perf: Faster serialization of canonicalized schemas
• bfe9ece perf: Extend benchmarks
• 80a0d91 perf: Tune canonicalization 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.

[github-actions]

🔍 The Case of Pull Request #773

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