upgrade Bazel to use bzlmod

WORKSPACE without bzlmod has been deprecated

.bazelrc

@@ -0,0 +1,2 @@
+# Enable Bzlmod for every Bazel command
+common --enable_bzlmod

BUILD

@@ -0,0 +1,8 @@
+load("@rules_python//python:pip.bzl", "compile_pip_requirements")
+
+compile_pip_requirements(
+    name = "requirements",
+    src = "//:requirements.txt",
+    requirements_txt = "requirements_lock.txt",
+    visibility = ["//visibility:public"],
+)

Dockerfile

@@ -2,7 +2,7 @@ FROM gcr.io/bazel-public/bazel:7.4.1 AS builder
 
 WORKDIR /wgkex
 
-COPY BUILD WORKSPACE requirements.txt ./
+COPY .bazelrc BUILD MODULE.bazel MODULE.bazel.lock requirements_lock.txt ./
 COPY wgkex ./wgkex
 
 RUN ["bazel", "build", "//wgkex/broker:app"]

MODULE.bazel

@@ -0,0 +1,11 @@
+bazel_dep(name = "rules_python", version = "0.40.0")
+
+pip = use_extension("@rules_python//python/extensions:pip.bzl", "pip")
+
+pip.parse(
+    hub_name = "pip",
+    python_version = "3.11",
+    requirements_lock = "//:requirements_lock.txt",
+)
+
+use_repo(pip, "pip")

README.md

@@ -167,6 +167,15 @@ python3 -c 'from wgkex.worker.app import main; main()'
 
 ## Development
 
+### Updating PIP dependencies
+
+This package is using Bazel's `compile_pip_requirements` to get a requirements_lock.txt file.
+In order to update the respective depencencies after modifying the requirements.txt, run:
+
+```sh
+bazel run //:requirements.update
+```
+
 ### Unit tests
 
 The test can be run using `bazel test ... --test_output=all` or `python3 -m unittest discover -p '*_test.py'`.