* test(bazel): add internal/testutil/bazeltest runfiles helpers Repository-path resolution for tests that works identically under plain go test (package cwd, full checkout), bazel test locally, and remote execution (declared runfiles only): - IsBazel, RepoRoot (BEADS_TEST_REPO_ROOT, then the runfiles workspace root, then a go.mod walk), OverrideRoot (drop-in condition for existing helpers; empty under plain go test), CallerDir - Runfile for $(rlocationpath) values, GOROOT for type-checking tests - ShardFreeEnv for helpers that re-exec a test binary Every helper reduces to the pre-Bazel behavior under go test. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> * test(bazel): declare source/data reads for 14 scan-guard targets Source-scanning and repo-file tests read files their Bazel targets never declared, so they failed under `bazel test` (and could not run on remote workers at all). Declare narrow inputs as `data` and resolve paths through bazeltest where the test located the tree via runtime.Caller: - tools/bazel/go_srcs.py (run by `make bazel-sync` after gazelle) keeps a managed `go_srcs` filegroup in the packages whose Go source tests scan, plus `//internal/storage:tree_go_srcs` for the storage-tree walk. Bazel globs stop at package boundaries, so the aggregate needs one filegroup per package; the script keeps it in sync and gazelle-stable. - Hand-written narrow inputs: //internal/storage/schema:migrations, //:docsync_files, //plugins/beads:plugin_files, and exports of .gitattributes, .claude-plugin/marketplace.json, cmd/bd list.go and ready.go, testutil/testdoltcommon.go, scripts README.md and the release catalog, each visible only to its consumer. - runtime.Caller-based roots in backend, backend/conformance, internal/storage, internal/formula and test/docsync now go through bazeltest.CallerDir / OverrideRoot; relative-path tests need data only. - integrations/ leaves .bazelignore (it is still gazelle-excluded) so the docsync link check can declare integrations/beads-mcp/PYPI.md. Under --config=prcore every target reports the same PASS/SKIP/FAIL test set as `go test -race -short` for its package, locally and remotely. Plain `go test` behavior is unchanged. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> * test(bazel): guard generated go_srcs and harden bazeltest root override - tools/bazel/go_srcs.py: add --check (print diff, exit 1 on stale blocks); new `make bazel-sync-check` target runs it. - scripts/bazel_policy_test.go: under go test, assert every tree_go_srcs (//internal/storage) lists exactly the BUILD.bazel packages below its root, run go_srcs.py --check, and forbid BUILD files under docs/ and engdocs/ (they would cut subtrees out of //:docsync_files). - bazeltest: honor BEADS_TEST_REPO_ROOT only when it holds go.mod (RepoRoot fails loudly otherwise); drop the unused GOROOT() helper, whose compiled-in branch could never fire under rules_go. - scripts/ci/lib/test-env.sh: unset BEADS_TEST_REPO_ROOT. - Document the hand-listed out-of-tree link targets in //:docsync_files. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> * build(bazel): re-sync BUILD files with main Regenerated with make bazel-sync after commits that landed while the scaffold PR was in CI (new internal/execenv, gitenv, gitignore packages and new sources/deps). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> * test(bazel): declare init_safety_help.go for docsync TestInitSafetyCLIHelpCoversReCloneGotchas (#6431) reads cmd/bd/init_safety_help.go; export it to //test/docsync only. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| BUILD.bazel | ||
| main.go | ||
| main_test.go | ||
| README.md | ||
Historical release catalog
../release-catalog.json pins the exact historical release universe used by the
v1.2 upgrade census: 122 stable module versions authenticated through the Go
proxy and SumDB, each with module / go.mod / source-zip / proxy-origin
provenance, explicit proxy prerelease and repository-only tag exclusions, and
the current repository tag drift.
The catalog command in this directory both regenerates and validates that
artifact (usage: catalog generate|validate <manifest.json>):
go run ./scripts/migration-test/catalog validate scripts/migration-test/release-catalog.jsonruns the strict offline validator: schema checks, semantic validation, canonical byte-form, and the pinned SHA-256 identity digest. Even a well-formed substitution is rejected until that digest is deliberately updated.go run ./scripts/migration-test/catalog generate scripts/migration-test/release-catalog.jsondeterministically rebuilds the catalog from the live Go proxy and GitHub release APIs (network plusgo/ghrequired). This is a manual maintenance path, not a CI step.
Status: self-validated reference anchor
Today the catalog is a reviewed-identity anchor. Its only automated enforcement
is TestCheckedCatalogIsCanonicalAndComplete in main_test.go, which runs
under go test ./... and holds the checked JSON to the pinned digest and its
invariants. Nothing in the migration-test harness (run.sh,
historical-dolt-upgrade-test.sh, legacy-bridge-test.sh) consumes it yet.
The intended consumer is the upgrade-coverage work stacked on top of this
change: runtime schema observations and family/path qualification will drive
upgrade tests against this finite, reproducible version universe. Until that
lands, regenerate deliberately with generate when upstream history changes —
drift from live upstream is not detected automatically.