chore(deps): bump jsonschema from 0.47.0 to 0.48.1

[dependabot]

Bumps jsonschema from 0.47.0 to 0.48.1.

Release notes

Sourced from jsonschema's releases.

[Rust] Release 0.48.1

Fixed

• Missing required errors in evaluate() output for schemas with properties and a two-entry required array. #1220
• contentEncoding errors for invalid UTF-8 after decoding incorrectly had empty instance_path and schema_path.

Performance

• Faster code generation for #[jsonschema::validator] (~5% across benchmarked schemas), via aliasing repeated paths in the emitted code.

[Python] Release 0.48.0

Fixed

• meta.is_valid and meta.validate incorrectly accepted some Draft 2019-09 schemas that the meta-schema rejects.
• Integers just outside the i64/u64 range incorrectly compared against numeric bounds through lossy f64 rounding (e.g. {"minimum": -9223372036854775808} accepted -9223372036854775809).

Performance

• Faster multipleOf validation for integer instances with integer divisors, via integer arithmetic instead of floating-point modulo.

[Ruby] Release 0.48.0

Fixed

• JSONSchema::Meta.valid? and JSONSchema::Meta.validate! incorrectly accepted some Draft 2019-09 schemas that the meta-schema rejects.
• Integers just outside the i64/u64 range incorrectly compared against numeric bounds through lossy f64 rounding (e.g. {"minimum" => -9223372036854775808} accepted -9223372036854775809).

Performance

• Faster multipleOf validation for integer instances with integer divisors, via integer arithmetic instead of floating-point modulo.

[Rust] Release 0.48.0

Added

• iter_errors for #[jsonschema::validator]-generated validators.

Fixed

• Per-branch context on generated anyOf and oneOf validation errors, matching runtime validators.
• $recursiveRef in generated validators incorrectly resolved to the innermost $recursiveAnchor (it should resolve to the outermost one).
• Integer instances just outside the i64/u64 range incorrectly compared against numeric bounds through lossy f64 rounding under arbitrary-precision (e.g. {"minimum": -9223372036854775808} accepted -9223372036854775809).

Changed

• One canonical number spelling from canonical::json::to_string under arbitrary-precision ("1e-2" becomes "0.01", "1.50" becomes "1.5") and correctly-rounded float parsing (serde_json's float_roundtrip).

Performance

• Faster multipleOf validation for integer instances with integer divisors, via integer arithmetic instead of floating-point modulo.

Changelog

Sourced from jsonschema's changelog.

[0.48.1] - 2026-07-17

Fixed

• Missing required errors in evaluate() output for schemas with properties and a two-entry required array. #1220
• contentEncoding errors for invalid UTF-8 after decoding incorrectly had empty instance_path and schema_path.

Performance

• Faster code generation for #[jsonschema::validator] (~5% across benchmarked schemas), via aliasing repeated paths in the emitted code.

[0.48.0] - 2026-07-16

Added

• iter_errors for #[jsonschema::validator]-generated validators.

Fixed

• Per-branch context on generated anyOf and oneOf validation errors, matching runtime validators.
• $recursiveRef in generated validators incorrectly resolved to the innermost $recursiveAnchor (it should resolve to the outermost one).
• Integer instances just outside the i64/u64 range incorrectly compared against numeric bounds through lossy f64 rounding under arbitrary-precision (e.g. {"minimum": -9223372036854775808} accepted -9223372036854775809).

Changed

• One canonical number spelling from canonical::json::to_string under arbitrary-precision ("1e-2" becomes "0.01", "1.50" becomes "1.5") and correctly-rounded float parsing (serde_json's float_roundtrip).

Performance

• Faster multipleOf validation for integer instances with integer divisors, via integer arithmetic instead of floating-point modulo.

Commits

• 4313166 chore(rust): Release 0.48.1
• 7ac65d7 chore: Tune playground styles
• 66cbd1b chore: Tune playground styles
• 3869179 chore: Add links to playground
• 4dc5b12 feat: WebAssembly playground
• cec64ef fix: contentEncoding errors for invalid UTF-8 after decoding incorrectly ha...
• ed1225c build(deps): bump ruby/setup-ruby from 1.318.0 to 1.319.0
• 7659118 feat: WASM bindings
• 3f4585d fix: Missing required errors in evaluate() output for schemas with `prope...
• 3c917d0 build(deps): bump taiki-e/install-action from 2.83.2 to 2.83.3
• 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)

[github-actions]

Thanks @dependabot[bot] for taking the time to contribute.

This repository is observing a maintainer-managed PR intake gate in dry-run mode, so this pull request is staying open. This note helps maintainers prepare the allowlist before any enforcement is considered.

Please read CONTRIBUTING.md for the expected contribution shape. A maintainer can grant recurring PR access by commenting /lgtm on a pull request.

[Hmbown]

Maintainer triage: checks are green and this is not tied to a known v0.9.1 security advisory. Keeping the PR open and moving it to v0.9.2 so the v0.9.1 exact-head freeze is not destabilized by late workflow/Cargo.lock churn. We will harvest these dependency updates together immediately after the release train.