Skip to content

Commit fa28dab

Browse files
authored
chore: update example to latest bazel deps (#49)
1 parent c9f15ae commit fa28dab

File tree

1 file changed

+4
-11
lines changed

1 file changed

+4
-11
lines changed

examples/MODULE.bazel

Lines changed: 4 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,12 @@
11
bazel_dep(name = "toolchains_protoc", version = "0.0.0")
22
bazel_dep(name = "aspect_bazel_lib", version = "2.11.0")
3-
bazel_dep(name = "aspect_rules_py", version = "1.0.0")
3+
bazel_dep(name = "aspect_rules_py", version = "1.3.2")
44
bazel_dep(name = "platforms", version = "0.0.11")
55
bazel_dep(name = "rules_java", version = "8.6.3")
66
bazel_dep(name = "rules_proto", version = "7.1.0")
7-
bazel_dep(name = "rules_python", version = "1.0.0")
8-
bazel_dep(name = "rules_go", version = "0.52.0")
9-
bazel_dep(name = "rules_uv", version = "0.52.0")
10-
11-
# Pick up https://github.com/theoremlp/rules_uv/pull/207/commits
12-
git_override(
13-
module_name = "rules_uv",
14-
commit = "6330187e9158931d07397e92870a7d5ed12b81f3",
15-
remote = "https://github.com/alexeagle/rules_uv.git",
16-
)
7+
bazel_dep(name = "rules_python", version = "1.1.0")
8+
bazel_dep(name = "rules_go", version = "0.53.0")
9+
bazel_dep(name = "rules_uv", version = "0.56.0")
1710

1811
# This example is in the same repo with the ruleset, so we should point to the code at HEAD
1912
# rather than use any release on the Bazel Central Registry.

0 commit comments

Comments
 (0)