Vendor route-proxy's SDK so its provider builds offline (issue 1019)

2026-10-17 18:15:43 +02:00
parent 1586bd1134
commit 65d570f114
12 changed files with 1988 additions and 2 deletions
@@ -9,8 +9,8 @@ race="${race:-}"
 # nested_modules vets and tests every Go module of its own below the root, `modules/<name>/go.mod` (novox/hq ADR 0420
 # §5, issue 1025): `./...` stops at a nested go.mod, so a module that lives whole in this repository would have its
 # unit tests run by nobody. None is a pass. Each runs in its own directory, outside the vendor directory this
-# repository's own packages are built from; how its dependencies are found offline is issue 1019's (the move of the
-# first two modules in), and it is settled there. A failing module fails the check; the others are still run.
+# repository's own packages are built from; a nested module vendors what the forge holds (its own `vendor/`, so the
+# check runs offline), as this repository's root module does (issue 1019). A failing module fails the check; the others are still run.
 nested_modules() {
 	nested=0
 	for gomod in modules/*/go.mod; do