chore(deps): update dependency rules_python to v0.27.1
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| rules_python | bazel_dep | minor | 0.21.0 -> 0.27.1 |
| rules_python | http_archive | minor | 0.21.0 -> 0.27.1 |
[!WARNING] Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
bazelbuild/rules_python (rules_python)
v0.27.1
Using Bzlmod with Bazel 6
NOTE: bzlmod support is still beta. APIs subject to change.
Add to your MODULE.bazel file:
bazel_dep(name = "rules_python", version = "0.27.1")
pip = use_extension("@​rules_python//python/extensions:pip.bzl", "pip")
pip.parse(
name = "pip",
requirements_lock = "//:requirements_lock.txt",
)
use_repo(pip, "pip")
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 = "e85ae30de33625a63eca7fc40a94fea845e641888e52f32b6beea91e8b1b2793",
strip_prefix = "rules_python-0.27.1",
url = "https://github.com/bazelbuild/rules_python/releases/download/0.27.1/rules_python-0.27.1.tar.gz",
)
load("@​rules_python//python:repositories.bzl", "py_repositories")
py_repositories()
Gazelle plugin
Paste this snippet into your WORKSPACE file:
load("@​bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
name = "rules_python_gazelle_plugin",
sha256 = "e85ae30de33625a63eca7fc40a94fea845e641888e52f32b6beea91e8b1b2793",
strip_prefix = "rules_python-0.27.1/gazelle",
url = "https://github.com/bazelbuild/rules_python/releases/download/0.27.1/rules_python-0.27.1.tar.gz",
)
### To compile the rules_python gazelle extension from source,
### we must fetch some third-party go dependencies that it uses.
load("@​rules_python_gazelle_plugin//:deps.bzl", _py_gazelle_deps = "gazelle_deps")
_py_gazelle_deps()
Full Changelog: https://github.com/bazelbuild/rules_python/compare/0.27.0...0.27.1
v0.27.0
Changed
-
Make
//python/pip_install:pip_repository_bzlbzl_librarytarget internal as all of the publicly available symbols (etc.package_annotation) are re-exported via//python:pip_bzlbzl_library. -
(gazelle) Gazelle Python extension no longer has runtime dependencies. Using
GAZELLE_PYTHON_RUNTIME_DEPSfrom@rules_python_gazelle_plugin//:def.bzlis no longer necessary. -
(pip_parse) The installation of
pip_parserepository rule toolchain dependencies is now done as part ofpy_repositoriescall. -
(pip_parse) The generated
requirements.bzlfile now has an additional symbolall_whl_requirements_by_packagewhich provides a map from the normalized PyPI package name to the target that provides the built wheel file. Usepip_utils.normalize_namefunction from@rules_python//python:pip.bzlto convert a PyPI package name to a key in theall_whl_requirements_by_packagemap. -
(pip_parse) The flag
incompatible_generate_aliaseshas been flipped toTrueby default onnon-bzlmodsetups allowing users to use the same label strings during the transition period. For example, instead of@pypi_foo//:pkg, you can now use@pypi//fooor@pypi//foo:pkg. Other labels that are present in thefoopackage aredist_info,whlanddata. Note, that the@pypi_foo//:pkglabels are still present for backwards compatibility. -
(gazelle) The flag
use_pip_repository_aliasesis now set toTrueby default, which will causegazelleto change third-party dependency labels from@pip_foo//:pkgto@pip//fooby default. -
The
compile_pip_requirementsnow defaults topyproject.tomlif thesrcorrequirements_inattributes are unspecified, matching the upstreampip-compilebehaviour more closely. -
(gazelle) Use relative paths if possible for dependencies added through the use of the
resolvedirective. -
(gazelle) When using
python_generation_mode file, onepy_testtarget is made per test file even if a target named__test__or a file named__test__.pyexists in the same package. Previously in these cases there would only be one test target made.
Breaking changes:
-
(pip)
pip_installrepository rule in this release has been disabled and will fail by default. The API symbol is going to be removed in the next version, please migrate topip_parseas a replacement. Thepip_parserule no longer supportsrequirementsattribute, please userequirements_lockinstead. -
(py_wheel) switch
incompatible_normalize_nameandincompatible_normalize_versiontoTrueby default to enforcePEP440for wheel names built byrules_python. -
(tools/wheelmaker.py) drop support for Python 2 as only Python 3 is tested.
Fixed
-
Skip aliases for unloaded toolchains. Some Python versions that don't have full platform support, and referencing their undefined repositories can break operations like
bazel query rdeps(...). -
Python code generated from
proto_librarywithstrip_import_prefixcan be imported now. -
(py_wheel) Produce deterministic wheel files and make
RECORDfile entries follow the order of files written to the.whlarchive. -
(gazelle) Generate a single
py_testtarget whengazelle:python_generation_mode projectis used. -
(gazelle) Move waiting for the Python interpreter process to exit to the shutdown hook to make the usage of the
exec.Commandmore idiomatic. -
(toolchains) Keep tcl subdirectory in Windows build of hermetic interpreter.
-
(bzlmod) sub-modules now don't have the
//conditions:defaultclause in the hub repos created bypip.parse. This should fix confusing error messages in case there is a misconfiguration of toolchains or a bug inrules_python.
Added
-
(bzlmod) Added
.whlpatching support viapatchesandpatch_striparguments to the newpip.overridetag class. -
(pip) Support for using PEP621 compliant
pyproject.tomlfor creating a resolvedrequirements.txtfile. -
(utils) Added a
pip_utilsstruct with anormalize_namefunction to allow users to find out howrules_pythonwould normalize a PyPI distribution name.
v0.26.0
Changed
-
Python version patch level bumps:
- 3.8.15 -> 3.8.18
- 3.9.17 -> 3.9.18
- 3.10.12 -> 3.10.13
- 3.11.4 -> 3.11.6
-
(deps) Upgrade rules_go 0.39.1 -> 0.41.0; this is so gazelle integration works with upcoming Bazel versions
-
(multi-version) The
distribsattribute is no longer propagated. This attribute has been long deprecated by Bazel and shouldn't be used. -
Calling
//python:repositories.bzl#py_repositories()is required. It has always been documented as necessary, but it was possible to omit it in certain cases. An error about@rules_python_internalmeans thepy_repositories()call is missing inWORKSPACE. -
(bzlmod) The
pip.parseextension will generate os/arch specific lock file entries onbazel>=6.4.
Added
-
(bzlmod, entry_point) Added
py_console_script_binary, which allows adding custom dependencies to a package's entry points and customizing thepy_binaryrule used to build it. -
New Python versions available:
3.8.17,3.11.5using https://github.com/indygreg/python-build-standalone/releases/tag/20230826. -
(gazelle) New
# gazelle:python_generation_mode filedirective to support generating onepy_libraryper file. -
(python_repository) Support
netrcandauth_patternsattributes to enable authentication against private HTTP hosts serving Python toolchain binaries. -
//python:packaging_bzladded, abzl_libraryfor the Starlark files//python:packaging.bzlrequires. -
(py_wheel) Added the
incompatible_normalize_namefeature flag to normalize the package distribution name according to latest Python packaging standards. Defaults toFalsefor the time being. -
(py_wheel) Added the
incompatible_normalize_versionfeature flag to normalize the package version according to PEP440 standard. This also adds support for local version specifiers (versions with a+in them), in accordance with PEP440. Defaults toFalsefor the time being. -
New Python versions available:
3.8.18,3.9.18,3.10.13,3.11.6,3.12.0using https://github.com/indygreg/python-build-standalone/releases/tag/20231002.3.12.0support is considered beta and may have issues.
Removed
-
(bzlmod) The
entry_pointmacro is no longer supported and has been removed in favour of thepy_console_script_binarymacro forbzlmodusers. -
(bzlmod) The
pip.parseno longer generates{hub_name}_{py_version}hub repos as theentry_pointmacro has been superseded bypy_console_script_binary. -
(bzlmod) The
pip.parseno longer generates{hub_name}_{distribution}hub repos.
Fixed
-
(whl_library) No longer restarts repository rule when fetching external dependencies improving initial build times involving external dependency fetching.
-
(gazelle) Improve runfiles lookup hermeticity.
v0.25.0
Changed
- Python version patch level bumps:
- 3.9.16 -> 3.9.17
- 3.10.9 -> 3.10.12
- 3.11.1 -> 3.11.4
- (bzlmod)
pip.parsecan no longer automatically use the default Python version; this was an unreliable and unsafe behavior. Thepython_versionarg must always be explicitly specified.
Fixed
- (docs) Update docs to use correct bzlmod APIs and clarify how and when to use various APIs.
- (multi-version) The
mainarg is now correctly computed and usually optional. - (bzlmod)
pip.parseno longer requires a call for whatever the configured default Python version is.
Added
- Created a changelog.
- (gazelle) Stop generating unnecessary imports.
- (toolchains) s390x supported for Python 3.9.17, 3.10.12, and 3.11.4.
v0.24.0
Changed
- BREAKING (gazelle) Gazelle 0.30.0 or higher is required
- (bzlmod)
@python_aliasesrenamed to `@python_versions - (bzlmod)
pip.parseargnamerenamed tohub_name - (bzlmod)
pip.parseargincompatible_generate_aliasesremoved and always true.
Fixed
- (bzlmod) Fixing Windows Python Interpreter symlink issues
- (py_wheel) Allow twine tags and args
- (toolchain, bzlmod) Restrict coverage tool visibility under bzlmod
- (pip) Ignore temporary pyc.NNN files in wheels
- (pip) Add format() calls to glob_exclude templates
- plugin_output in py_proto_library rule
Added
- Using Gazelle's lifecycle manager to manage external processes
- (bzlmod)
pip.parsecan be called multiple times with different Python versions - (bzlmod) Allow bzlmod
pip.parseto reference the default python toolchain and interpreter - (bzlmod) Implementing wheel annotations via
whl_mods - (gazelle) support multiple requirements files in manifest generation
- (py_wheel) Support for specifying
Description-Content-TypeandSummaryin METADATA - (py_wheel) Support for specifying
Project-URL - (compile_pip_requirements) Added
generate_hashesarg (default True) to control generating hashes - (pip) Create all_data_requirements alias
- Expose Python C headers through the toolchain.
v0.23.1
Using Bzlmod with Bazel 6
Add to your MODULE.bazel file:
bazel_dep(name = "rules_python", version = "0.23.1")
pip = use_extension("@​rules_python//python:extensions.bzl", "pip")
pip.parse(
name = "pip",
requirements_lock = "//:requirements_lock.txt",
)
use_repo(pip, "pip")
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 = "84aec9e21cc56fbc7f1335035a71c850d1b9b5cc6ff497306f84cced9a769841",
strip_prefix = "rules_python-0.23.1",
url = "https://github.com/bazelbuild/rules_python/releases/download/0.23.1/rules_python-0.23.1.tar.gz",
)
load("@​rules_python//python:repositories.bzl", "py_repositories")
py_repositories()
Gazelle plugin
Paste this snippet into your WORKSPACE file:
load("@​bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
name = "rules_python_gazelle_plugin",
sha256 = "84aec9e21cc56fbc7f1335035a71c850d1b9b5cc6ff497306f84cced9a769841",
strip_prefix = "rules_python-0.23.1/gazelle",
url = "https://github.com/bazelbuild/rules_python/releases/download/0.23.1/rules_python-0.23.1.tar.gz",
)
### To compile the rules_python gazelle extension from source,
### we must fetch some third-party go dependencies that it uses.
load("@​rules_python_gazelle_plugin//:deps.bzl", _py_gazelle_deps = "gazelle_deps")
_py_gazelle_deps()
What's Changed
- fix(bzlmod+gazelle): update BCR release presubmit to use correct example by @rickeylev in https://github.com/bazelbuild/rules_python/pull/1264
Full Changelog: https://github.com/bazelbuild/rules_python/compare/0.23.0...0.23.1
v0.23.0
Using Bzlmod with Bazel 6
NOTE: bzlmod support is still experimental; apis are still subject to change
This release introduces two notable changes to bzlmod support:
- A default toolchain is automatically registered for you. You no longer need to call
register_toolchains()yourself. Depending on rules_python through bazel_dep is sufficient. Note, however, the Python version used for this default toolchain will change frequently/unexpectedly to track the a recent Python version. - The
namearg ofpython.toolchainhas been removed. The toolchain repo name format ispython_X_Ye.g.python_3_11.
Add to your MODULE.bazel file:
bazel_dep(name = "rules_python", version = "0.23.0")
pip = use_extension("@​rules_python//python:extensions.bzl", "pip")
pip.parse(
name = "pip",
requirements_lock = "//:requirements_lock.txt",
)
use_repo(pip, "pip")
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 = "8272287b125a23bfc79650ecbbc045ebcaee4d632338b1a50aad34357bcbadce",
strip_prefix = "rules_python-0.23.0",
url = "https://github.com/bazelbuild/rules_python/releases/download/0.23.0/rules_python-0.23.0.tar.gz",
)
load("@​rules_python//python:repositories.bzl", "py_repositories")
py_repositories()
Gazelle plugin
Paste this snippet into your WORKSPACE file:
load("@​bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
name = "rules_python_gazelle_plugin",
sha256 = "8272287b125a23bfc79650ecbbc045ebcaee4d632338b1a50aad34357bcbadce",
strip_prefix = "rules_python-0.23.0/gazelle",
url = "https://github.com/bazelbuild/rules_python/releases/download/0.23.0/rules_python-0.23.0.tar.gz",
)
### To compile the rules_python gazelle extension from source,
### we must fetch some third-party go dependencies that it uses.
load("@​rules_python_gazelle_plugin//:deps.bzl", _py_gazelle_deps = "gazelle_deps")
_py_gazelle_deps()
What's Changed
- feat(bzlmod): Allowing multiple python.toolchain extension calls by @chrislovecnm in https://github.com/bazelbuild/rules_python/pull/1230
- build: Upgrade Gazelle to v0.31.0 by @linzhp in https://github.com/bazelbuild/rules_python/pull/1240
- fix: make
import python.runfileswork with--experimental_python_import_all_repositories=falseby @rickeylev in https://github.com/bazelbuild/rules_python/pull/1243 - feat(bzlmod): Moving register.toolchains internal by @chrislovecnm in https://github.com/bazelbuild/rules_python/pull/1238
- docs(compile_pip_requirements): Add note on requirements.txt VC by @boomanaiden154 in https://github.com/bazelbuild/rules_python/pull/1245
- cleanup: Set toolchain target_setting directly instead of via inline ternary by @rickeylev in https://github.com/bazelbuild/rules_python/pull/1246
- fix(bzlmod): give precedence to the first seen versioned toolchain by @rickeylev in https://github.com/bazelbuild/rules_python/pull/1244
- chore: add a pre-commit hook to maintain deleted packages by @aignas in https://github.com/bazelbuild/rules_python/pull/1208
- chore: auto-publish gazelle module to BCR by @kormide in https://github.com/bazelbuild/rules_python/pull/1247
- fix(coverage): bump to latest coverage.py and fix import shadowing by @aignas in https://github.com/bazelbuild/rules_python/pull/1249
- feat: add ppc64le releases and update to 3.10.11, 3.11.3 for python-build-standalone by @clnperez in https://github.com/bazelbuild/rules_python/pull/1234
- fix(bzlmod)!: Remove ability to specify toolchain repo name. by @rickeylev in https://github.com/bazelbuild/rules_python/pull/1258
- fix: update correct requirements lock file when using os specific lock files by @Rasrack in https://github.com/bazelbuild/rules_python/pull/1123
- fix: use
only-binaryfordownload_onlypip downloadby @lpulley in https://github.com/bazelbuild/rules_python/pull/1219 - feat: Adding variable support for distribution in py_wheel by @ns-tkonduri in https://github.com/bazelbuild/rules_python/pull/1251
- feat(bzlmod): Register a default toolchain by @rickeylev in https://github.com/bazelbuild/rules_python/pull/1259
New Contributors
- @boomanaiden154 made their first contribution in https://github.com/bazelbuild/rules_python/pull/1245
- @clnperez made their first contribution in https://github.com/bazelbuild/rules_python/pull/1234
- @lpulley made their first contribution in https://github.com/bazelbuild/rules_python/pull/1219
- @ns-tkonduri made their first contribution in https://github.com/bazelbuild/rules_python/pull/1251
Full Changelog: https://github.com/bazelbuild/rules_python/compare/0.22.0...0.23.0
v0.22.0
Notable and Breaking Changes
Bzlmod extension paths have changed
As part of fixing some fundamental issues with the bzlmod support, we had to change the path to our extensions. Instead of all extensions being in a single extensions.bzl file, each extension is in its own file. Users must update the file path in their use_repo() statements as follows:
-
use_extension("@​rules_python//python:extensions.bzl", "python")->use_extension("@​rules_python//python/extensions:python.bzl", "python") -
use_extension("@​rules_python//python:extensions.bzl", "pip")->use_extension("@​rules_python//python/extensions:pip.bzl", "pip")
The following sed commands should approximate the necessary changes:
sed 'sXuse_extension("@​rules_python//python:extensions.bzl", "python")Xuse_extension("@​rules_python//python/extensions:python.bzl", "python")X'`
sed 'sXuse_extension("@​rules_python//python:extensions.bzl", "pip")Xuse_extension("@​rules_python//python/extensions:pip.bzl", "pip")X'`
See examples/bzlmod_build_file_generation/MODULE.bazel for an example of the new paths.
Lockfile output churn
The output of lockfiles has slightly changed. Though functionally the same, their integrity hashes will change.
Using Bzlmod with Bazel 6
NOTE: Bzlmod support is still in beta.
Add to your MODULE.bazel file:
bazel_dep(name = "rules_python", version = "0.22.0")
pip = use_extension("@​rules_python//python/extensions:pip.bzl", "pip")
pip.parse(
name = "pip",
requirements_lock = "//:requirements_lock.txt",
)
use_repo(pip, "pip")
### (Optional) Register a specific python toolchain instead of using the host version
python = use_extension("@​rules_python//python/extensions:python.bzl", "python")
python.toolchain(
name = "python3_9",
python_version = "3.9",
)
use_repo(python, "python3_9_toolchains")
register_toolchains(
"@​python3_9_toolchains//:all",
)
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 = "863ba0fa944319f7e3d695711427d9ad80ba92c6edd0b7c7443b84e904689539",
strip_prefix = "rules_python-0.22.0",
url = "https://github.com/bazelbuild/rules_python/releases/download/0.22.0/rules_python-0.22.0.tar.gz",
)
load("@​rules_python//python:repositories.bzl", "py_repositories")
py_repositories()
Gazelle plugin
Paste this snippet into your WORKSPACE file:
load("@​bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
name = "rules_python_gazelle_plugin",
sha256 = "863ba0fa944319f7e3d695711427d9ad80ba92c6edd0b7c7443b84e904689539",
strip_prefix = "rules_python-0.22.0/gazelle",
url = "https://github.com/bazelbuild/rules_python/releases/download/0.22.0/rules_python-0.22.0.tar.gz",
)
### To compile the rules_python gazelle extension from source,
### we must fetch some third-party go dependencies that it uses.
load("@​rules_python_gazelle_plugin//:deps.bzl", _py_gazelle_deps = "gazelle_deps")
_py_gazelle_deps()
What's Changed
- fix: remove reference to @bazel_tools//tools/python/private:defs.bzl by @comius in https://github.com/bazelbuild/rules_python/pull/1173
- docs: Tell how to use GitHub to find commits in an upcoming release. by @rickeylev in https://github.com/bazelbuild/rules_python/pull/1092
- fix: compile_pip_requirements test from external repositories by @Rasrack in https://github.com/bazelbuild/rules_python/pull/1124
- feat: add Python 3.8.16 by @jml-derek in https://github.com/bazelbuild/rules_python/pull/1168
- test: Set mac platform for test_mac_requires_darwin_for_execution by @rickeylev in https://github.com/bazelbuild/rules_python/pull/1179
- fix: Don't reference deleted private bazel_tools bzl file by @rickeylev in https://github.com/bazelbuild/rules_python/pull/1180
- docs: Add starlark directive to code snippet by @blorente in https://github.com/bazelbuild/rules_python/pull/1170
- tests: Upgrade rules_testing to 0.0.5 by @rickeylev in https://github.com/bazelbuild/rules_python/pull/1184
- tests: Set linux platform for test_non_mac_doesnt_require_darwin_for_execution by @rickeylev in https://github.com/bazelbuild/rules_python/pull/1183
- fix(bzlmod): correctly template repository macros for requirements, etc by @aignas in https://github.com/bazelbuild/rules_python/pull/1190
- type:docs Update README.md by @yuanweixin in https://github.com/bazelbuild/rules_python/pull/1186
- fix: Allow passing a tuple to the
tagsattribute. by @rickeylev in https://github.com/bazelbuild/rules_python/pull/1191 - tests: Add skylib to various test dependencies to fix CI by @chrislovecnm in https://github.com/bazelbuild/rules_python/pull/1199
- feat: removing bzlmod from example by @chrislovecnm in https://github.com/bazelbuild/rules_python/pull/1200
- feat: propagate visibility attribute for py_wheel publishing by @chrislovecnm in https://github.com/bazelbuild/rules_python/pull/1203
- docs: fix typos in pip_repository docs by @martis42 in https://github.com/bazelbuild/rules_python/pull/1202
- tests: Force analysis test labels to resolve within @rules_python context by @rickeylev in https://github.com/bazelbuild/rules_python/pull/1187
- fix(update_deleted_packages.sh): allow to run from anywhere in the repo by @aignas in https://github.com/bazelbuild/rules_python/pull/1206
- feat(bzlmod): expose platform-agnostic repo target for toolchain interpreter by @chrislovecnm in https://github.com/bazelbuild/rules_python/pull/1155
- fix(update_deleted_packages.sh): wheels example should not be included in .bazelrc by @aignas in https://github.com/bazelbuild/rules_python/pull/1207
- fix: Strip trailing newline from python output by @illicitonion in https://github.com/bazelbuild/rules_python/pull/1212
- fix: manually ignore bazel-* directories to make using custom Bazel builds easier by @rickeylev in https://github.com/bazelbuild/rules_python/pull/1181
- test(bzlmod): explicitly enable bzlmod in the test harness by @aignas in https://github.com/bazelbuild/rules_python/pull/1204
- feat(bzlmod): Cleaning up interpreter resolution by @chrislovecnm in https://github.com/bazelbuild/rules_python/pull/1218
- feat(bzlmod)!: Move each bzlmod extension into its own file by @chrislovecnm in https://github.com/bazelbuild/rules_python/pull/1226
- Adding bzlmod support document by @chrislovecnm in https://github.com/bazelbuild/rules_python/pull/1214
- test(coverage): add a test to check the sys.path under bzlmod by @aignas in https://github.com/bazelbuild/rules_python/pull/1223
- fix(toolchain): set correct return attrs to remove non-hermeticity warning by @aignas in https://github.com/bazelbuild/rules_python/pull/1231
- fix: allow url fragments in requirements file by @mattoberle in https://github.com/bazelbuild/rules_python/pull/1195
- fix:
example/build_file_generation/README.mdby @ofey404 in https://github.com/bazelbuild/rules_python/pull/1164 - fix: Using canonical name in requirements.bzl by @linzhp in https://github.com/bazelbuild/rules_python/pull/1176
- feat(bzlmod): support entry_point macro by @aignas in https://github.com/bazelbuild/rules_python/pull/1220
New Contributors
- @Rasrack made their first contribution in https://github.com/bazelbuild/rules_python/pull/1124
- @jml-derek made their first contribution in https://github.com/bazelbuild/rules_python/pull/1168
- @blorente made their first contribution in https://github.com/bazelbuild/rules_python/pull/1170
- @yuanweixin made their first contribution in https://github.com/bazelbuild/rules_python/pull/1186
- @ofey404 made their first contribution in https://github.com/bazelbuild/rules_python/pull/1164
Full Changelog: https://github.com/bazelbuild/rules_python/compare/0.21.0...0.22.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
- [ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Renovate Bot.