Bump rules_python from 1.9.0 to 2.2.0

[dependabot]

Bumps rules_python from 1.9.0 to 2.2.0.

Release notes

Sourced from rules_python's releases.

2.2.0

For more detailed setup instructions, see https://rules-python.readthedocs.io/en/latest/getting-started.html

For the user-facing changelog see here

Using Bzlmod

Add to your MODULE.bazel file:

bazel_dep(name = "rules_python", version = "2.2.0")
python = use_extension("@​rules_python//python/extensions:python.bzl", "python")
python.toolchain(
python_version = "3.13",
)
pip = use_extension("@​rules_python//python/extensions:pip.bzl", "pip")
pip.parse(
hub_name = "pypi",
python_version = "3.13",
requirements_lock = "//:requirements_lock.txt",
)
use_repo(pip, "pypi")

Using WORKSPACE

Paste this snippet into your WORKSPACE file:

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
name = "rules_python",
sha256 = "e11d2e1efce1589e5bdfa93986712c74fc7467a0f093143d489d2ef5ebb1ed2a",
strip_prefix = "rules_python-2.2.0",
url = "https://github.com/bazel-contrib/rules_python/releases/download/2.2.0/rules_python-2.2.0.tar.gz",
)
load("@​rules_python//python:repositories.bzl", "py_repositories")
py_repositories()

Gazelle plugin

Paste this snippet into your WORKSPACE file:

... (truncated)

Changelog

Sourced from rules_python's changelog.

2.2.0 - 2026-06-30

{#v2-2-0-changed}

Changed

• Renamed most public bzl_library targets from {foo}_bzl to {foo} to follow gazelle naming conventions. Deprecated aliases are left for backwards compatibility.
• (binaries/tests) Added a deprecation warning for targets relying on implicit __init__.py creation.

{#v2-2-0-fixed}

Fixed

• Fixed a flaky error on Windows 2022 when looking up the win32 version during site initialization by retrying the lookup (#3721).
• (binaries) Fixed building of legacy zipapps on Windows execution platforms by using a hermetic tool instead of host cat.
• (bootstrap) Fixed stage 1 bootstrap imports when target outputs shadow standard library modules.
• (coverage) Skip lcov report when no data was collected.
• (pypi) Fixed experimental_index_url checking truthiness before envsubst expansion.
• (rules) Fixed venv output paths for py_binary and py_test targets whose names contain path separators so distinct targets with the same basename no longer share the same venv output directory.
• (windows) Fixed build data generation on localized Windows installations.

{#v2-2-0-added}

Added

• Added {bzl:obj}features.loadable_symbols to allow detecting public symbols exported by bzl files.
• Exposed {bzl:obj}VenvSymlinkEntry and {bzl:obj}VenvSymlinkKind in {bzl:target}//python:py_info.bzl.
• (pypi) Added @pypi repo: a unified hub of pip.parse hubs.
• (pypi) Added a dep tag class to the pip bzlmod extension. This allows modules to declare abstract PyPI dependencies, ensuring target structures exist in the unified hub, while allowing other modules to provide the concrete implementation via pip.parse.
• (uv) Support for basic uv.lock generation via the lock rule and basic support for importing the uv.lock file itself. Since this may have bugs, please report this by creating new tickets. Work towards #2787 and #1975.

{#v2-1-0}

[2.1.0] - 2026-06-17

... (truncated)

Commits

• be0ae53 fix: run executable zip action with execution Python to better support window...
• df4acbd fix: use locale-neutral Windows ACL for build data (#3887)
• 721ca37 chore: replace version_next marker in download.md
• efa67e9 feat(pypi): add pip.dep to declare abstract pypi dependencies (#3850)
• b1fb23b fix: avoid stage1 bootstrap stdlib shadowing (#3854)
• f7751e4 chore(release) backport check_version_markers fix from #3880
• ee0acbd Prepare release v2.2.0 (#3874)
• 9af23e5 chore(release): use force push and clean up git helpers in prep tool (#3873)
• 8a825aa chore(release): reuse existing PRs and avoid early exit in prep tool (#3870)
• 9734b11 chore(release): add dry-run to release tool prepare command (#3869)
• 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)

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4d306d16fe

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Update the git override with the version bump

This line advertises rules_python 2.2.0, but the git_override for rules_python immediately below still pins commit bac549496f67b9f0109d914319c09acf653ccdea, which is the 1.9.0 release source. Because Bzlmod applies that override as the repository source, normal bazel build //... and downstream consumers continue loading the old code while Dependabot/readers believe 2.2.0 is being tested, so the upgrade is effectively not applied unless the override is updated or removed in the same change.

Useful? React with 👍 / 👎.