deps(core-py): bump the all group in /wren-core-py with 2 updates

[dependabot]

Bumps the all group in /wren-core-py with 2 updates: maturin and ruff.

Updates maturin from 1.8.2 to 1.8.3

Release notes

Sourced from maturin's releases.

v1.8.3

What's Changed

• Fix cargo run uniffi-bindgen when cross compiling by @​messense in PyO3/maturin#2476
• Use emcc.bat to query version on Windows by @​messense in PyO3/maturin#2478
• Add rnet python library to examples by @​0x676e67 in PyO3/maturin#2480
• bump the attest-build-provenance version in the generated ci file by @​kemingy in PyO3/maturin#2484
• Fix platform tag on Solaris/Illumos by @​kulikjak in PyO3/maturin#2483
• Auto detect PyPy 3.11 by @​messense in PyO3/maturin#2487
• Update manylinux/musllinux policies to the latest main by @​github-actions in PyO3/maturin#2491
• Update generate-ci options in user guide by @​wxh06 in PyO3/maturin#2501
• chore: Update cbindgen to 0.28.0 by @​pacman82 in PyO3/maturin#2498
• Don't install dependencies when running maturin develop --skip-install by @​messense in PyO3/maturin#2504
• Upgrade pyo3 to 0.24.0 by @​messense in PyO3/maturin#2511
• Update the TP docs to use pypi as the GH Env name by @​webknjaz in PyO3/maturin#2512
• fix auditwheel .so relocation for namespace modules by @​pascalkuthe in PyO3/maturin#2513
• Updates Rng legacy methods in tutorial by @​rafaelbeckel in PyO3/maturin#2514

New Contributors

• @​0x676e67 made their first contribution in PyO3/maturin#2480
• @​kemingy made their first contribution in PyO3/maturin#2484
• @​wxh06 made their first contribution in PyO3/maturin#2501
• @​pacman82 made their first contribution in PyO3/maturin#2498
• @​webknjaz made their first contribution in PyO3/maturin#2512
• @​pascalkuthe made their first contribution in PyO3/maturin#2513
• @​rafaelbeckel made their first contribution in PyO3/maturin#2514

Full Changelog: PyO3/maturin@v1.8.2...v1.8.3

Changelog

Sourced from maturin's changelog.

[1.8.3]

• Fix relocating shared library for namespace modules in #2513
• Don't install dependencies when running maturin develop --skip-install in #2504
• Use emcc.bat to query version on Windows in #2478
• Bump the attest-build-provenance version in the generated ci file in #2484
• Fix platform tag on Solaris/Illumos in #2483
• Fix cargo run uniffi-bindgen when cross compiling in #2476

Commits

• c200385 Sync version in Cargo.lock
• d0e878d Release v1.8.3 (#2515)
• b9da804 Update rand & pyo3 versions in user guide
• 0770d50 Updates Rng legacy methods in tutorial (#2514)
• 30cdcbd fix auditwheel .so relocation for namespace modules (#2513)
• c6e640f Update the TP docs to use pypi as the GH Env name (#2512)
• 5c0d16d Upgrade pyo3 to 0.24.0 (#2511)
• 17c76ae Merge pull request #2508 from PyO3/pre-commit-ci-update-config
• de28d0c [pre-commit.ci] pre-commit autoupdate
• 7986b3d Don't install dependencies when running maturin develop --skip-install (#2504)
• Additional commits viewable in compare view

Updates ruff from 0.9.10 to 0.11.0

Release notes

Sourced from ruff's releases.

0.11.0

Release Notes

This is a follow-up to release 0.10.0. The requires-python inference changes were unintentionally omitted from 0.10.0, and have been included here. This release also includes stabilization of the preview behavior for PGH004.

Breaking changes

• Changes to how the Python version is inferred when a target-version is not specified (#16319)

  In previous versions of Ruff, you could specify your Python version with:

  • The target-version option in a ruff.toml file or the [tool.ruff] section of a pyproject.toml file.
  • The project.requires-python field in a pyproject.toml file with a [tool.ruff] section.

  These options worked well in most cases, and are still recommended for fine control of the Python version. However, because of the way Ruff discovers config files, pyproject.toml files without a [tool.ruff] section would be ignored, including the requires-python setting. Ruff would then use the default Python version (3.9 as of this writing) instead, which is surprising when you've attempted to request another version.

  In v0.10, config discovery has been updated to address this issue:

  • If Ruff finds a ruff.toml file without a target-version, it will check for a pyproject.toml file in the same directory and respect its requires-python version, even if it does not contain a [tool.ruff] section.
  • If Ruff finds a user-level configuration, the requires-python field of the closest pyproject.toml in a parent directory will take precedence.
  • If there is no config file (ruff.tomlor pyproject.toml with a [tool.ruff] section) in the directory of the file being checked, Ruff will search for the closest pyproject.toml in the parent directories and use its requires-python setting.

Stabilization

The following behaviors have been stabilized:

• blanket-noqa (PGH004): Also detect blanked file-level noqa comments (and not just line level comments).

Preview features

• [syntax-errors] Tuple unpacking in for statement iterator clause before Python 3.9 (#16558)

Install ruff 0.11.0

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/ruff/releases/download/0.11.0/ruff-installer.sh | sh

Install prebuilt binaries via powershell script

powershell -ExecutionPolicy ByPass -c "irm https://github.com/astral-sh/ruff/releases/download/0.11.0/ruff-installer.ps1 | iex"
</tr></table> 

... (truncated)

Changelog

Sourced from ruff's changelog.

0.11.0

This is a follow-up to release 0.10.0. Because of a mistake in the release process, the requires-python inference changes were not included in that release. Ruff 0.11.0 now includes this change as well as the stabilization of the preview behavior for PGH004.

Breaking changes

• Changes to how the Python version is inferred when a target-version is not specified (#16319)

  In previous versions of Ruff, you could specify your Python version with:

  • The target-version option in a ruff.toml file or the [tool.ruff] section of a pyproject.toml file.
  • The project.requires-python field in a pyproject.toml file with a [tool.ruff] section.

  These options worked well in most cases, and are still recommended for fine control of the Python version. However, because of the way Ruff discovers config files, pyproject.toml files without a [tool.ruff] section would be ignored, including the requires-python setting. Ruff would then use the default Python version (3.9 as of this writing) instead, which is surprising when you've attempted to request another version.

  In v0.10, config discovery has been updated to address this issue:

  • If Ruff finds a ruff.toml file without a target-version, it will check for a pyproject.toml file in the same directory and respect its requires-python version, even if it does not contain a [tool.ruff] section.
  • If Ruff finds a user-level configuration, the requires-python field of the closest pyproject.toml in a parent directory will take precedence.
  • If there is no config file (ruff.tomlor pyproject.toml with a [tool.ruff] section) in the directory of the file being checked, Ruff will search for the closest pyproject.toml in the parent directories and use its requires-python setting.

Stabilization

The following behaviors have been stabilized:

• blanket-noqa (PGH004): Also detect blanked file-level noqa comments (and not just line level comments).

Preview features

• [syntax-errors] Tuple unpacking in for statement iterator clause before Python 3.9 (#16558)

0.10.0

Check out the blog post for a migration guide and overview of the changes!

Breaking changes

See also, the "Remapped rules" section which may result in disabled rules.

• Changes to how the Python version is inferred when a target-version is not specified (#16319)

  Because of a mistake in the release process, the requires-python inference changes are not included in this release and instead shipped as part of 0.11.0. You can find a description of this change in the 0.11.0 section.

... (truncated)

Commits

• 2cd25ef Ruff 0.11.0 (#16723)
• a22d206 [red-knot] Preliminary tests for typing.Final (#15917)
• 270318c [red-knot] fix: improve type inference for binary ops on tuples (#16725)
• d03b12e [red-knot] Assignments to attributes (#16705)
• 14c5ed5 [pygrep-hooks]: Detect file-level suppressions comments without rul… (#16720)
• 5955650 Fallback to requires-python in certain cases when target-version is not found...
• 2382fe1 [syntax-errors] Tuple unpacking in for statement iterator clause before Pyt...
• 27e9d1f Ruff v0.10 Release (#16708)
• acf35c5 Add new noqa specification to the docs (#16703)
• b9b2562 describe requires-python fallback in docs (#16704)
• 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[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.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
• @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.