Skip to content

Bump rules_python from 1.9.0 to 2.0.1 #64

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.

Sign up for GitHub

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
dependabot wants to merge 1 commit into from
Closed

Bump rules_python from 1.9.0 to 2.0.1 #64

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion MODULE.bazel
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ module(
version = "0.1.2",
)

bazel_dep(name = "rules_python", version = "1.9.0")
bazel_dep(name = "rules_python", version = "2.0.1")

@chatgpt-codex-connector chatgpt-codex-connector Bot May 13, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Update the git override with the version bump

This bump changes the requested module version to 2.0.1, but the adjacent git_override still pins rules_python to commit bac549496f67b9f0109d914319c09acf653ccdea, which the existing comment says is meant to stay pinned to the release source commit alongside the module version. In builds using Bzlmod overrides, Bazel will fetch the overridden Git source rather than the registry artifact, so this dependency remains on the old rules_python source while appearing to be upgraded.

Useful? React with 👍 / 👎.

bazel_dep(name = "bazel_skylib", version = "1.9.0")
bazel_dep(name = "rules_shell", version = "0.6.1")

Expand Down
Loading