//scripts:scripts_test and //scripts/check-versions:check-versions_test drop their host-tools/no-remote-exec/no-remote-cache tags and run on the rbe-west workers like every other target (the worker image ships bash, git, python3, jq, yq, curl, openssl, unzip and coreutils; a missing tool fails the test under Bazel rather than skipping it). Go comes in hermetically as the registered SDK; check-versions.sh's `go build` is stood in for by the Bazel-built checker. The tests that walked the source checkout now get it as data: tools/bazel/go_srcs.py keeps a managed `repo_files` filegroup in every package and aggregates them into //:repo_files (exactly the tracked files Bazel can see; make bazel-sync-check fails on a package without one). scripts_test and docsync_test take it instead of hand-listed filegroups, and every TEST_SRCDIR/IsBazel skip and go-test-only block in them is gone. The release formula under .bazelignore'd .beads/ comes in through a @beads_formulas local repository; npm-package/ and .claude/ are visible to Bazel again (only their node_modules/worktrees stay ignored), so the npm manifest release check and the AGENTS.md skill links run under Bazel too. TestZZStdioNotLeaked falls back to TestMain's pre-run streams instead of skipping in a shard without its baseline. tools/bazel/equivalence_allowlist.txt shrinks from 20 skip entries to the two cmd/bd tests of plain go test's own bd build fallback, which Bazel never takes; pr-preflight-platforms now runs them on Linux, macOS and Windows. The scripts-go-checks scripts-test and allowlisted legs, their scripts (scripts-go-test.sh, allowlisted-go-tests.sh, run_allowlisted_go_tests.py) and main.yml's --compile-only warm for them are removed. The vet leg stays (ga-96smfk.18). Refs: ga-96smfk.16 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.