rules_python@0.39.0, rules_python_gazelle_plugin@0.39.0#3171
rules_python@0.39.0, rules_python_gazelle_plugin@0.39.0#3171publish-to-bcr-bot[bot] wants to merge 1 commit intobazelbuild:mainfrom
Conversation
|
Hello @rickeylev, @f0rmiga, modules you maintain (rules_python, rules_python_gazelle_plugin) have been updated in this PR. Please review the changes. |
|
Hello @aignas, modules you maintain (rules_python) have been updated in this PR. Please review the changes. |
bazel-io
left a comment
There was a problem hiding this comment.
Hello @bazelbuild/bcr-maintainers, all modules in this PR have been approved by their maintainers. Please take a final look to merge this PR.
|
Can we drop Bazel 6 for Bzlmod support? Bazel 7 had tons of Bzlmod improvement ( |
|
And maybe add |
Yes, we dropped bazel 6 bzlmod with this release. I have bazel-contrib/rules_python#2404 to fix that upstream. I started #3180 to verify adding bazel 8.x to presubmit.yml actually works (It should 😅, but this is the first run of it under BCR). So, you can force merge this (all the failures are Bazel 6, so fine to ignore), or un-draft 3180 and merge that instead (it's a copy of this, but with presubmit.yml changes). |
|
I've switched #3180 to non-draft. Let's close this in favor of that one. It, at the least, has green presubmits. |
BCR config for rules_python and rules_python_gazelle_plugin 0.39.0 This is #3171, but with presubmit changes to remove Bazel 6 from the test matrix.
Release: https://github.com/bazelbuild/rules_python/releases/tag/0.39.0
Automated by Publish to BCR