-
Notifications
You must be signed in to change notification settings - Fork 2
chore(deps): update dependency rules_python to v0.22.0 #115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
f45c906
to
62f88fb
Compare
bb85ea9
to
9787bab
Compare
9787bab
to
f674c22
Compare
9a941b0
to
39a677a
Compare
513ee8c
to
088ae33
Compare
09b90ec
to
d78031f
Compare
f769939
to
0e3d5d5
Compare
db118d5
to
7449f53
Compare
7449f53
to
accbcc2
Compare
accbcc2
to
ff4aaac
Compare
a2a6f76
to
e862a71
Compare
e862a71
to
6da6a87
Compare
blocked by rules_k8s |
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update (0.22.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.5.0
->0.22.0
Release Notes
bazelbuild/rules_python
v0.22.0
Compare Source
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 theiruse_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: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:Using WORKSPACE
Paste this snippet into your
WORKSPACE
file:Gazelle plugin
Paste this snippet into your
WORKSPACE
file:What's Changed
tags
attribute. by @rickeylev in https://github.com/bazelbuild/rules_python/pull/1191example/build_file_generation/README.md
by @ofey404 in https://github.com/bazelbuild/rules_python/pull/1164New Contributors
Full Changelog: bazel-contrib/rules_python@0.21.0...0.22.0
v0.21.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:What's Changed
New Contributors
Full Changelog: bazel-contrib/rules_python@0.20.0...0.21.0
v0.20.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:What's Changed
New Contributors
Full Changelog: bazel-contrib/rules_python@0.19.0...0.20.0
v0.19.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:What's Changed
py_runtime.coverage_tool
for Bazel 6 and higher. by @rickeylev in https://github.com/bazelbuild/rules_python/pull/1061.dist
targets by @rickeylev in https://github.com/bazelbuild/rules_python/pull/1064Full Changelog: bazel-contrib/rules_python@0.18.0...0.19.0
v0.18.1
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
py_runtime.coverage_tool
for Bazel 6 and higher. (#1061)Full Changelog: bazel-contrib/rules_python@0.18.0...0.18.1
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
Post-release notes
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: bazel-contrib/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: bazel-contrib/rules_python@0.16.2...0.17.3
v0.16.2
Compare Source
Using Bzlmod with Bazel 6
Add to your
MODULE.bazel
file:Using WORKSPACE:
Paste this snippet into your
WORKSPACE
file:What's Changed
compile_pip_requirements
by @groodt in https://github.com/bazelbuild/rules_python/pull/945BUILD
->BUILD.bazel
by @groodt in https://github.com/bazelbuild/rules_python/pull/946New Contributors
Full Changelog: bazel-contrib/rules_python@0.16.1...0.16.2
v0.16.1
Compare Source
Using Bzlmod with Bazel 6
Add to your
MODULE.bazel
file: