v9.3.2

README.md

@@ -1,4 +1,4 @@
-# Dockwatch v9.3.1
+# Dockwatch v9.3.2
 
 > Go module: `git.send.nrw/sendnrw/dockwatch`
 
@@ -391,3 +391,22 @@ node --check web/app.js
 The SQLite migration SQL is additionally smoke-tested against Python's SQLite engine because the temporary `modernc.org/sqlite` stub does not implement a real SQL driver.
 
 On a normal networked development machine or during `docker build`, run `go mod tidy && go test ./...` once against the real pinned dependencies.
+
+### Module metadata / `go mod tidy`
+
+The Docker builder runs `go mod tidy` after the full source tree has been copied and before compiling. This is intentional: Go 1.17+ module graph pruning may require transitive dependencies to be recorded as indirect requirements once the actual imported package graph is known. A checkout with an older/incomplete `go.mod` or without `go.sum` therefore still builds reproducibly in CI instead of failing late with `updates to go.mod needed`.
+
+For repository maintenance, run:
+
+```bash
+go mod tidy
+git add go.mod go.sum
+git commit -m "chore: tidy Go modules"
+```
+
+CI can use `make verify` to fail when `go.mod`/`go.sum` are not committed in tidy form.
+
+
+## v9.3.2 module-build fix
+
+v9.3.2 fixes Docker/CI builds that stopped at `go: updates to go.mod needed; to update it: go mod tidy`. The builder now runs `go mod tidy` after the complete source tree has been copied and before `go build`, so indirect requirements required by Go module graph pruning are materialized in the build stage. The Makefile also includes `tidy` and `verify` targets for maintaining committed `go.mod`/`go.sum` files.