The catalog stopped at v1.1.2 (the v1.2 upgrade census). The migration corpus already upgrades from v1.2.2, and the Bazel targets that replace migration-test.yml and cross-version-smoke.yml take their pinned release binaries from the catalog (@bd_releases), so it has to cover the releases since. Regenerated with `catalog generate` after raising maximumVersion to v1.3.1: five new stable versions (v1.2.0, v1.2.1, v1.2.2, v1.3.0, v1.3.1; three with a linux/amd64 asset) and five new proxy prereleases; no existing entry, drift record or repository-only exclusion changed. The count constants and the identity digest are updated to match, and the README now says how to add a release. Refs: ga-96smfk.19 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 (v0.9.1
through v1.3.1; the v1.2 upgrade census plus the releases since): 127 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.
Adding a release
Raise maximumVersion in main.go, run generate, and update the count
constants and expectedCatalogSHA256 the validator then reports. Every
release with a linux/amd64 asset digest automatically becomes a pinned Bazel
repository (@bd_releases//:<version>, tools/bazel/bd_releases.bzl).
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. Bazel consumes it: tools/bazel/bd_releases.bzl declares one
sha256-verified repository per release asset it records, which the
regression, migration (tests/migration) and cross-version targets run
instead of downloading release binaries.
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.