Run the release job on scheduled builds #34

Merged
TheDarkWizard merged 1 commit from fix-scheduled-release into main 2026-07-02 10:23:44 +00:00

The nightly scheduled builds have never published a release since the Forgejo migration: the release job's if requires github.ref == 'refs/heads/main', but Forgejo hands scheduled runs a minimal synthetic event (the same quirk behind the missing repository field fixed in #27), so the ref check is false on schedule and the job silently skips. Today's 06:00 run shows it: both builds succeeded and pushed the 20260702 tags, but no release was created until the PR #29 merge push published one at 09:52.

Allow the schedule event through the condition explicitly. Schedules only ever run from the default branch, so the main-only guarantee is unchanged; PRs and feature-branch pushes stay excluded.

Can't be tested before tomorrow's nightly without faking a schedule event, but the condition is trivially true for schedule and unchanged for everything else.

The nightly scheduled builds have never published a release since the Forgejo migration: the release job's `if` requires `github.ref == 'refs/heads/main'`, but Forgejo hands scheduled runs a minimal synthetic event (the same quirk behind the missing `repository` field fixed in #27), so the ref check is false on schedule and the job silently skips. Today's 06:00 run shows it: both builds succeeded and pushed the 20260702 tags, but no release was created until the PR #29 merge push published one at 09:52. Allow the `schedule` event through the condition explicitly. Schedules only ever run from the default branch, so the main-only guarantee is unchanged; PRs and feature-branch pushes stay excluded. Can't be tested before tomorrow's nightly without faking a schedule event, but the condition is trivially true for schedule and unchanged for everything else.
Run the release job on scheduled builds
Some checks failed
PR Rebase Hint / Post rebase command (pull_request) Successful in 3s
bluebuild / Release (pull_request) Has been cancelled
bluebuild / Generate Release (pull_request) Has been cancelled
bluebuild / Build GNOME (pull_request) Has been cancelled
bluebuild / Build GNOME NVIDIA (pull_request) Has been cancelled
71ba6b986c
Forgejo gives scheduled runs a minimal synthetic event (the same quirk behind
the missing repository field fixed earlier), so github.ref is not
refs/heads/main when the nightly fires and the release job's ref check
silently skipped it on every scheduled build since the migration. Nobody
noticed because pushes to main also publish releases.

Allow the schedule event explicitly; schedules only run from the default
branch, so the main-only guarantee holds.

🧪 Test this PR on a real install

Once the build checks on this PR pass, a signed test image is published for each edition. Pick the one matching your hardware and, from an existing Monolith install (which already has the signing policy), rebase onto it:

gnome

rpm-ostree rebase ostree-image-signed:docker://forge.waywardinn.com/monolith-os/gnome:pr-34-44
systemctl reboot

gnome-nvidia

rpm-ostree rebase ostree-image-signed:docker://forge.waywardinn.com/monolith-os/gnome-nvidia:pr-34-44
systemctl reboot

The tags are rebuilt on every new commit here, so rpm-ostree upgrade pulls the latest build. When you're done testing, return to your edition's released image (:latest).

The test tags stop updating once this PR is merged or closed.

### 🧪 Test this PR on a real install **Once the build checks on this PR pass**, a signed test image is published for each edition. Pick the one matching your hardware and, from an existing Monolith install (which already has the signing policy), rebase onto it: **`gnome`** ```bash rpm-ostree rebase ostree-image-signed:docker://forge.waywardinn.com/monolith-os/gnome:pr-34-44 systemctl reboot ``` **`gnome-nvidia`** ```bash rpm-ostree rebase ostree-image-signed:docker://forge.waywardinn.com/monolith-os/gnome-nvidia:pr-34-44 systemctl reboot ``` The tags are rebuilt on every new commit here, so `rpm-ostree upgrade` pulls the latest build. When you're done testing, return to your edition's released image (`:latest`). _The test tags stop updating once this PR is merged or closed._
Sign in to join this conversation.
No description provided.