Bump jsonschema-rs from 0.18.1 to 0.29.1

[dependabot]

Bumps jsonschema-rs from 0.18.1 to 0.29.1.

Release notes

Sourced from jsonschema-rs's releases.

[Python] Release 0.29.1

Packaging

• Fix missing source distribution.

[Python] Release 0.29.0

Added

• Added Registry class for schema reuse and reference resolution.

Performance

• Significantly improved validator compilation speed by using pointer-based references to schema fragments instead of cloning them during traversal.

[Rust] Release 0.29.0

Breaking Changes

• All builder methods on ValidationOptions now take ownership of self instead of &mut self. This change enables better support for non-blocking retrieval of external resources during the process of building a validator. Update your code to chain the builder methods instead of reusing the options instance:

  // Before (0.28.x)
  let mut options = jsonschema::options();
  options.with_draft(Draft::Draft202012);
  options.with_format("custom", my_format);
  let validator = options.build(&schema)?;
  // After (0.29.0)
  let validator = jsonschema::options()
  .with_draft(Draft::Draft202012)
  .with_format("custom", my_format)
  .build(&schema)?;

• The Retrieve trait's retrieve method now accepts URI references as &Uri<String> instead of &Uri<&str>. This aligns with the async version and simplifies internal URI handling. The behavior and available methods remain the same, this is purely a type-level change.

  // Before
  fn retrieve(&self, uri: &Uri<&str>) -> Result<Value, Box<dyn std::error::Error + Send + Sync>>
  // After
  fn retrieve(&self, uri: &Uri<String>) -> Result<Value, Box<dyn std::error::Error + Send + Sync>>

• Simplified Registry creation API:

  • Removed RegistryOptions::try_new and RegistryOptions::try_from_resources in favor of Registry::build
  • Removed Registry::try_with_resource_and_retriever - use Registry::options().retriever() instead
  • Registry creation is now consistently done through the builder pattern

... (truncated)

Changelog

Sourced from jsonschema-rs's changelog.

Changelog

[Unreleased]

[0.29.0] - 2025-02-08

Breaking Changes

• All builder methods on ValidationOptions now take ownership of self instead of &mut self. This change enables better support for non-blocking retrieval of external resources during the process of building a validator. Update your code to chain the builder methods instead of reusing the options instance:

  // Before (0.28.x)
  let mut options = jsonschema::options();
  options.with_draft(Draft::Draft202012);
  options.with_format("custom", my_format);
  let validator = options.build(&schema)?;
  // After (0.29.0)
  let validator = jsonschema::options()
  .with_draft(Draft::Draft202012)
  .with_format("custom", my_format)
  .build(&schema)?;

• The Retrieve trait's retrieve method now accepts URI references as &Uri<String> instead of &Uri<&str>. This aligns with the async version and simplifies internal URI handling. The behavior and available methods remain the same, this is purely a type-level change.

  // Before
  fn retrieve(&self, uri: &Uri<&str>) -> Result<Value, Box<dyn std::error::Error + Send + Sync>>
  // After
  fn retrieve(&self, uri: &Uri<String>) -> Result<Value, Box<dyn std::error::Error + Send + Sync>>

• Simplified Registry creation API:

  • Removed RegistryOptions::try_new and RegistryOptions::try_from_resources in favor of Registry::build
  • Removed Registry::try_with_resource_and_retriever - use Registry::options().retriever() instead
  • Registry creation is now consistently done through the builder pattern

  // Before (0.28.x)
  let registry = Registry::options()
      .draft(Draft::Draft7)
      .try_new(
          "http://example.com/schema",
          resource
      )?;

... (truncated)

Commits

• f6a4048 chore(python): Release 0.29.1
• 8c072cb build(python): Fix sdist
• aeb98b9 chore(python): Release 0.29.0
• 44e787f chore(rust): Release 0.29.0
• 620b1b9 docs: Update MIGRATION.md
• d8df940 docs: Update CHANGELOG.md
• d69a5d3 feat: Async retriever
• 6a529dd feat(py): Schema Registry
• ab71a6d perf: Minor performance improvements
• 0f72d5c chore: Extend profiler
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.