Skip to content

ci(verify-release): verify the latest release nightly, and resolve an empty tag instead of guessing - #58

Merged
openviewmobile merged 1 commit into
mainfrom
chore/verify-nightly
Nov 10, 2026
Merged

openviewmobile merged 1 commit into
mainfrom
chore/verify-nightly

Conversation

@openviewmobile

Copy link
Copy Markdown
Owner

Two gaps left after #54/#57:

  1. Nothing re-checks what is already published. The workflow_run trigger proves "the thing released a minute ago is fine"; a broken page, a Pages drift or a key rotation is only caught if someone runs the workflow by hand. It now also runs on schedule: 17 3 * * * (UTC) against the current latest release.
  2. An empty TAG used to be fatal, and before that it silently verified whatever gh considered latest. A schedule event carries no tag at all, so a resolve the tag step now falls back to gh release view --json tagName and exports the resolved value; only if that also fails does the job go red.

Also changelogged the three CI false-reds found today (SIGPIPE on grep -q, the byte comparison judged from one transient apt-get download, the empty tag under workflow_run).

I could not exercise the manual dispatch to confirm #57 on v0.2.8: the UI dialog's POST to /actions/manual returns 422 with the CSRF header supplied, so the first proof of the new logic is the nightly run (or the next release). What I did check locally: the signed index's SHA256 for 0.2.8 equals the release checksum.

@openviewmobile
openviewmobile merged commit 4f4b062 into main Nov 10, 2026
2 checks passed
@openviewmobile
openviewmobile deleted the chore/verify-nightly branch November 10, 2026 08:04
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