Skip to content

ci: revalidate unchanged master for Nightly publication - #968

Merged
LunaStev merged 1 commit into
wavefnd:masterfrom
LunaStev:ci/revalidate-nightly
Oct 19, 2026
Merged

LunaStev merged 1 commit into
wavefnd:masterfrom
LunaStev:ci/revalidate-nightly

Conversation

@LunaStev

Copy link
Copy Markdown
Member

Revalidate the unchanged master tree through a fresh canonical push CI run so Nightly can resume after the pinned installer deployment.

This is an empty DCO commit: its Git tree is exactly ded9e5eb079722340660dcf812f5279debe1842d, identical to master 40d1c05e7ea71ab59192ab12a603af76ccf3bb11. No source, workflow, dependency, version, approval hash, or publication rule changes are included.

PR #967 passed all 35 checks. Canonical CI run 39278377798 produced all 35 verification reports without failure or timeout, but GitHub's run/check/job APIs remain queued. Normal cancellation was accepted without reaching a completed state; force cancellation reports the run is already completed, while the official rerun API rejects it as already running. A fresh ordinary master push is a recovery attempt; it still must pass the existing complete CI eligibility checks before Nightly can publish.

Related: #966. The operator deployed wave-platform #488 and both public installer hashes have been verified. Keep v0.2.1-pre-beta pinned, retain exact-byte deployment verification, and leave #966 open until actual Nightly publication is verified.

All 35 reports from the prior canonical CI contain no failure, but GitHub keeps the run queued and returns conflicting cancellation and rerun states. Trigger a fresh normal master push validation with the identical source tree and unchanged publication checks.

Related: wavefnd#966
Signed-off-by: LunaStev <luna@lunastev.org>
@LunaStev
LunaStev merged commit 8f73666 into wavefnd:master Oct 19, 2026
1 of 35 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant