chore(deps): update dependency rules_python to v0.18.0 #134
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.16.2
->0.18.0
Release Notes
bazelbuild/rules_python
v0.18.0
Compare Source
Using Bzlmod with Bazel 6
Add to your
MODULE.bazel
file:Using WORKSPACE
Paste this snippet into your
WORKSPACE
file:Gazelle plugin
Paste this snippet into your
WORKSPACE
file:Relevant Changes
Coverage
rules_python
now includes coverage as part of the toolchain as an opt-in feature. To get started, passregister_coverage_tool = True
topython_register_toolchains
orpython_register_multi_toolchains
.runfiles wheel
The
bazel-runfiles
wheel is now published to https://pypi.org/project/bazel-runfiles/.What's Changed
New Contributors
Full Changelog: bazelbuild/rules_python@0.17.3...0.18.0
v0.17.3
Compare Source
Note, the prior 0.17 tags (0.17.0, 0.17.1, and 0.17.2) were never published as releases and can be ignored.
Breaking Change
The Gazelle extension for Python has been updated to better integrate with the conventions of Python and Bazel. This includes changes to how test files with the prefix or suffix of "test_" and "*_test" are handled. If a test target is not present, these files will now be added to individual py_test targets. To align your projects with these changes, any test utility files that were previously included in py_library targets and have the aforementioned prefix or suffix, will need to be renamed for consistency.
To use the gazelle extension you must now fetch another external repository,
rules_python_gazelle_plugin
, see the snippet below.Also, change your gazelle binary registration to load from this new repository:
Using Bzlmod with Bazel 6
Add to your
MODULE.bazel
file:Using WORKSPACE
Paste this snippet into your
WORKSPACE
file:Gazelle plugin
Paste this snippet into your
WORKSPACE
file:What's Changed
CurrentRepository
from Bazel by @fmeum in https://github.com/bazelbuild/rules_python/pull/988strip_prefix
intool_versions
by @lummax in https://github.com/bazelbuild/rules_python/pull/975*.lib
interface inpython_headers
by @lummax in https://github.com/bazelbuild/rules_python/pull/976tool_versions
by @lummax in https://github.com/bazelbuild/rules_python/pull/973New Contributors
Full Changelog: bazelbuild/rules_python@0.16.2...0.17.3
v0.17.2
Compare Source
v0.17.1
Compare Source
v0.17.0
Compare Source
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 this update again.
This PR has been generated by Mend Renovate. View repository job log here.