Files
pulse/scripts
rcourtman b1a8b4f866 Let the release metadata tests accept beta versions
The release train now cuts a beta every two days before the release
candidate. Its first beta, v6.6.0-beta.1, failed its preparation checks
twice: the governance test that maps VERSION to its release packet only
matched -rc.N, and two tests required the release index to say "current
v6 release candidate packet" while the metadata tool writes "current v6
beta packet" for a beta.

Accept -beta.N where the packet paths are derived and derive the expected
index wording from the version. Release candidates and stable releases
are checked exactly as before.

Contract-Neutral: Release metadata tests only; no runtime, API, install or customer contract change.
2026-10-11 21:08:44 +01:00
..
…
…
…
2026-10-05 21:53:41 +01:00