Repository navigation
Refresh Nightly approvals for pinned std-compatible installers - #967
Merged
Merged
Conversation
Keep the exact deployed-byte gate and the v0.2.1-pre-beta installer policy. Report expected and received hashes and verify that either unapproved endpoint blocks identity export. Closes wavefnd#966 Signed-off-by: LunaStev <luna@lunastev.org>
This was referenced Oct 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Nightly currently rejects the deployed installers because its approval file still contains hashes for the previous latest-only policy. Keep the intentional Wave v0.2.1-pre-beta pin and approve the std-compatible Bash and PowerShell installers from wave-platform #488, commit bdb59e5.
Exact-byte verification, the identified HTTP client, and the download limit remain in place. The failure now reports the affected URL and expected/received SHA-256 values without assuming a latest-only installer policy. A regression test checks both endpoints independently: old or otherwise changed bytes fail without exporting a Nightly source identity.
Validation: all 53 tests in
tools.test_nightly,tools.test_release_gates, andtools.test_release_publishpassed, plus whitespace checks. Installer validation passed its Bash suites, 15 Python cases, and 315 PowerShell 7.4.13 assertions on Linux; All four installer PR checks, including Windows PowerShell 5.1 amd64/arm64, passed in run 39275020996. No backend, dependency, compiler version, versioned-release policy, or unrelated std recovery changes are included.Deployment verified: wave-platform #488 merged as 1fdf58c1e33095ef83fdf710fc9f17c84b1b479a; the operator deployed it. Both public HTTPS installer files match these exact reviewed SHA-256 hashes, preserve v0.2.1-pre-beta, and pass
installers_ready()with the production HTTP client. The frontend build also preserves both files byte for byte. After deployment and canonical master CI, verify the existing Nightly workflow publishes and validates the complete release generation.Related: #966. Keep the issue open until deployment and actual Nightly publication are verified.