Run the release job on scheduled builds #34
No reviewers
Labels
No labels
bug
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
monolith-os/monolith!34
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix-scheduled-release"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The nightly scheduled builds have never published a release since the Forgejo migration: the release job's
ifrequiresgithub.ref == 'refs/heads/main', but Forgejo hands scheduled runs a minimal synthetic event (the same quirk behind the missingrepositoryfield 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
scheduleevent 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.
🧪 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:
gnomegnome-nvidiaThe tags are rebuilt on every new commit here, so
rpm-ostree upgradepulls 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.