chore(deps): update dependency rules_python_gazelle_plugin to v0.26.0 #192
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.18.0
->0.26.0
Release Notes
bazelbuild/rules_python (rules_python_gazelle_plugin)
v0.26.0
Compare Source
Changed
Python version patch level bumps:
(deps) Upgrade rules_go 0.39.1 -> 0.41.0; this is so gazelle integration works with upcoming Bazel versions
(multi-version) The
distribs
attribute is no longer propagated. Thisattribute has been long deprecated by Bazel and shouldn't be used.
Calling
//python:repositories.bzl#py_repositories()
is required. It hasalways been documented as necessary, but it was possible to omit it in certain
cases. An error about
@rules_python_internal
means thepy_repositories()
call is missing in
WORKSPACE
.(bzlmod) The
pip.parse
extension will generate os/arch specific lockfile entries on
bazel>=6.4
.Added
(bzlmod, entry_point) Added
py_console_script_binary
, whichallows adding custom dependencies to a package's entry points and customizing
the
py_binary
rule used to build it.New Python versions available:
3.8.17
,3.11.5
usinghttps://github.com/indygreg/python-build-standalone/releases/tag/20230826.
(gazelle) New
# gazelle:python_generation_mode file
directive to supportgenerating one
py_library
per file.(python_repository) Support
netrc
andauth_patterns
attributes to enableauthentication against private HTTP hosts serving Python toolchain binaries.
//python:packaging_bzl
added, abzl_library
for the Starlarkfiles
//python:packaging.bzl
requires.(py_wheel) Added the
incompatible_normalize_name
feature flag tonormalize the package distribution name according to latest Python
packaging standards. Defaults to
False
for the time being.(py_wheel) Added the
incompatible_normalize_version
feature flagto 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 to
False
for thetime being.
New Python versions available:
3.8.18
,3.9.18
,3.10.13
,3.11.6
,3.12.0
usinghttps://github.com/indygreg/python-build-standalone/releases/tag/20231002.
3.12.0
support is considered beta and may have issues.Removed
(bzlmod) The
entry_point
macro is no longer supported and has been removedin favour of the
py_console_script_binary
macro forbzlmod
users.(bzlmod) The
pip.parse
no longer generates{hub_name}_{py_version}
hub reposas the
entry_point
macro has been superseded bypy_console_script_binary
.(bzlmod) The
pip.parse
no 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
Compare Source
Changed
pip.parse
can no longer automatically use the defaultPython version; this was an unreliable and unsafe behavior. The
python_version
arg must always be explicitly specified.Fixed
various APIs.
main
arg is now correctly computed and usually optional.pip.parse
no longer requires a call for whatever the configureddefault Python version is.
Added
v0.24.0
Compare Source
Changed
@python_aliases
renamed to `@python_versionspip.parse
argname
renamed tohub_name
pip.parse
argincompatible_generate_aliases
removed and alwaystrue.
Fixed
Added
pip.parse
can be called multiple times with different Pythonversions
pip.parse
to reference the default python toolchain and interpreterwhl_mods
Description-Content-Type
andSummary
in METADATAProject-URL
generate_hashes
arg (default True) tocontrol generating hashes
v0.23.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:What's Changed
Full Changelog: bazelbuild/rules_python@0.23.0...0.23.1
v0.23.0
Compare Source
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:
register_toolchains()
yourself. Dependingon 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.
name
arg ofpython.toolchain
has been removed. The toolchain repo name format ispython_X_Y
e.g.python_3_11
.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
import python.runfiles
work with--experimental_python_import_all_repositories=false
by @rickeylev in https://github.com/bazelbuild/rules_python/pull/1243only-binary
fordownload_only
pip download
by @lpulley in https://github.com/bazelbuild/rules_python/pull/1219New Contributors
Full Changelog: bazelbuild/rules_python@0.22.0...0.23.0
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: bazelbuild/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: bazelbuild/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: bazelbuild/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: bazelbuild/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: bazelbuild/rules_python@0.18.0...0.18.1
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, 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.