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.0Release Notes
bazelbuild/rules_python (rules_python_gazelle_plugin)
v0.26.0Compare 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
distribsattribute 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_internalmeans thepy_repositories()call is missing in
WORKSPACE.(bzlmod) The
pip.parseextension 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_binaryrule used to build it.New Python versions available:
3.8.17,3.11.5usinghttps://github.com/indygreg/python-build-standalone/releases/tag/20230826.
(gazelle) New
# gazelle:python_generation_mode filedirective to supportgenerating one
py_libraryper file.(python_repository) Support
netrcandauth_patternsattributes to enableauthentication against private HTTP hosts serving Python toolchain binaries.
//python:packaging_bzladded, abzl_libraryfor the Starlarkfiles
//python:packaging.bzlrequires.(py_wheel) Added the
incompatible_normalize_namefeature flag tonormalize the package distribution name according to latest Python
packaging standards. Defaults to
Falsefor the time being.(py_wheel) Added the
incompatible_normalize_versionfeature 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
Falsefor thetime being.
New Python versions available:
3.8.18,3.9.18,3.10.13,3.11.6,3.12.0usinghttps://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 removedin favour of the
py_console_script_binarymacro forbzlmodusers.(bzlmod) The
pip.parseno longer generates{hub_name}_{py_version}hub reposas the
entry_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.0Compare Source
Changed
pip.parsecan no longer automatically use the defaultPython version; this was an unreliable and unsafe behavior. The
python_versionarg must always be explicitly specified.Fixed
various APIs.
mainarg is now correctly computed and usually optional.pip.parseno longer requires a call for whatever the configureddefault Python version is.
Added
v0.24.0Compare Source
Changed
@python_aliasesrenamed to `@python_versionspip.parseargnamerenamed tohub_namepip.parseargincompatible_generate_aliasesremoved and alwaystrue.
Fixed
Added
pip.parsecan be called multiple times with different Pythonversions
pip.parseto reference the default python toolchain and interpreterwhl_modsDescription-Content-TypeandSummaryin METADATAProject-URLgenerate_hashesarg (default True) tocontrol generating hashes
v0.23.1Compare Source
Using Bzlmod with Bazel 6
Add to your
MODULE.bazelfile:Using WORKSPACE
Paste this snippet into your
WORKSPACEfile:Gazelle plugin
Paste this snippet into your
WORKSPACEfile:What's Changed
Full Changelog: bazel-contrib/rules_python@0.23.0...0.23.1
v0.23.0Compare 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.
namearg ofpython.toolchainhas been removed. The toolchain repo name format ispython_X_Ye.g.python_3_11.Add to your
MODULE.bazelfile:Using WORKSPACE
Paste this snippet into your
WORKSPACEfile:Gazelle plugin
Paste this snippet into your
WORKSPACEfile:What's Changed
import python.runfileswork with--experimental_python_import_all_repositories=falseby @rickeylev in https://github.com/bazelbuild/rules_python/pull/1243only-binaryfordownload_onlypip downloadby @lpulley in https://github.com/bazelbuild/rules_python/pull/1219New Contributors
Full Changelog: bazel-contrib/rules_python@0.22.0...0.23.0
v0.22.0Compare 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.bzlfile, 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
sedcommands should approximate the necessary changes:See
examples/bzlmod_build_file_generation/MODULE.bazelfor 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.bazelfile:Using WORKSPACE
Paste this snippet into your
WORKSPACEfile:Gazelle plugin
Paste this snippet into your
WORKSPACEfile:What's Changed
tagsattribute. by @rickeylev in https://github.com/bazelbuild/rules_python/pull/1191example/build_file_generation/README.mdby @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.0Compare Source
Using Bzlmod with Bazel 6
Add to your
MODULE.bazelfile:Using WORKSPACE
Paste this snippet into your
WORKSPACEfile:Gazelle plugin
Paste this snippet into your
WORKSPACEfile:What's Changed
New Contributors
Full Changelog: bazel-contrib/rules_python@0.20.0...0.21.0
v0.20.0Compare Source
Using Bzlmod with Bazel 6
Add to your
MODULE.bazelfile:Using WORKSPACE
Paste this snippet into your
WORKSPACEfile:Gazelle plugin
Paste this snippet into your
WORKSPACEfile:What's Changed
New Contributors
Full Changelog: bazel-contrib/rules_python@0.19.0...0.20.0
v0.19.0Compare Source
Using Bzlmod with Bazel 6
Add to your
MODULE.bazelfile:Using WORKSPACE
Paste this snippet into your
WORKSPACEfile:Gazelle plugin
Paste this snippet into your
WORKSPACEfile:What's Changed
py_runtime.coverage_toolfor Bazel 6 and higher. by @rickeylev in https://github.com/bazelbuild/rules_python/pull/1061.disttargets by @rickeylev in https://github.com/bazelbuild/rules_python/pull/1064Full Changelog: bazel-contrib/rules_python@0.18.0...0.19.0
v0.18.1Compare Source
Using Bzlmod with Bazel 6
Add to your
MODULE.bazelfile:Using WORKSPACE
Paste this snippet into your
WORKSPACEfile:Gazelle plugin
Paste this snippet into your
WORKSPACEfile:Relevant Changes
py_runtime.coverage_toolfor Bazel 6 and higher. (#1061)Full Changelog: bazel-contrib/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.