Fix scheduled builds failing on missing repository field #27

Merged

TheDarkWizard merged 4 commits from fix-scheduled-build into main 2026-07-01 10:46:00 +00:00

Conversation 1 Commits 4 Files changed 1 +25

TheDarkWizard commented 2026-07-01 10:29:48 +00:00

Owner

Copy link

Forgejo's scheduled-event payload omits the repository field, but the blue-build CLI deserializes GITHUB_EVENT_PATH into a struct that requires it (get_repo_url/get_registry), so nightly builds fail with missing field \repository``. GitHub's own schedule payload includes it, which is why manual workflow_dispatch runs are unaffected.

On scheduled runs, rebuild a valid payload from the github context and repoint the CLI at it via $GITHUB_ENV. default_branch is set to ref_name (main on a schedule) so on_default_branch() stays true and dated release tags are still produced.

Also adds a throwaway test-event-override workflow (workflow_dispatch) to verify the one uncertain part: that the GITHUB_EVENT_PATH override actually propagates via $GITHUB_ENV in the Forgejo runner. Run it on this branch, confirm the assert step passes, then remove the file before merge.

Forgejo's scheduled-event payload omits the `repository` field, but the blue-build CLI deserializes `GITHUB_EVENT_PATH` into a struct that requires it (`get_repo_url`/`get_registry`), so nightly builds fail with `missing field \`repository\``. GitHub's own schedule payload includes it, which is why manual workflow_dispatch runs are unaffected. On scheduled runs, rebuild a valid payload from the `github` context and repoint the CLI at it via $GITHUB_ENV. `default_branch` is set to `ref_name` (main on a schedule) so `on_default_branch()` stays true and dated release tags are still produced. Also adds a throwaway `test-event-override` workflow (workflow_dispatch) to verify the one uncertain part: that the `GITHUB_EVENT_PATH` override actually propagates via $GITHUB_ENV in the Forgejo runner. Run it on this branch, confirm the assert step passes, then remove the file before merge.

TheDarkWizard added 1 commit 2026-07-01 10:29:48 +00:00

Fix scheduled builds failing on missing repository field ... 761804a3bd

Forgejo's scheduled-event payload omits the repository field, but the
blue-build CLI deserializes GITHUB_EVENT_PATH into a struct that requires
it (get_repo_url/get_registry), so nightly builds fail with
"missing field `repository`". GitHub's own schedule payload includes it,
which is why manual workflow_dispatch runs are unaffected.

Rebuild a valid payload from the github context on scheduled runs and
repoint the CLI at it. default_branch is set to ref_name (main on a
schedule) so on_default_branch() stays true and dated release tags are
still produced.

Add a throwaway test-event-override workflow to verify the one uncertain
part, that the GITHUB_EVENT_PATH override propagates via $GITHUB_ENV in
the Forgejo runner. Remove it once verified.

forgejo-actions commented 2026-07-01 10:29:52 +00:00

Copy link

🧪 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-27-44
systemctl reboot

gnome-nvidia

rpm-ostree rebase ostree-image-signed:docker://forge.waywardinn.com/monolith-os/gnome-nvidia:pr-27-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-27-44 systemctl reboot ``` **`gnome-nvidia`** ```bash rpm-ostree rebase ostree-image-signed:docker://forge.waywardinn.com/monolith-os/gnome-nvidia:pr-27-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._

TheDarkWizard added 1 commit 2026-07-01 10:35:16 +00:00

Run event-override probe on pull_request ... 176b13e69b

Forgejo only lists workflow_dispatch workflows that live on the default
branch, so the probe couldn't be dispatched from a feature branch. Run it
on pull_request instead so it executes automatically on this PR.

TheDarkWizard added 1 commit 2026-07-01 10:37:43 +00:00

Overwrite event file in place instead of repointing it ... bae762d036

The probe showed this runner (act) ignores GITHUB_* overrides written to
$GITHUB_ENV, so repointing GITHUB_EVENT_PATH did not take effect. Overwrite
the file GITHUB_EVENT_PATH already points at instead, and update the probe
to prove the write is visible to a later step (via a sentinel value).

TheDarkWizard added 1 commit 2026-07-01 10:38:31 +00:00

Remove event-override probe now that the fix is verified 6237f7f05c

TheDarkWizard merged commit 2f2bc26ae3 into main 2026-07-01 10:46:00 +00:00

TheDarkWizard referenced this pull request from a commit 2026-07-01 10:46:02 +00:00

Fix scheduled builds failing on missing repository field (#27)

TheDarkWizard referenced this pull request 2026-07-02 10:00:04 +00:00

Run the release job on scheduled builds #34

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

bug

Something isn't working

  

dependencies

Pull requests that update a dependency file

  

documentation

Improvements or additions to documentation

  

duplicate

This issue or pull request already exists

  

enhancement

New feature or request

  

github_actions

Pull requests that update GitHub Actions code

  

good first issue

Good for newcomers

  

help wanted

Extra attention is needed

  

invalid

This doesn't seem right

  

question

Further information is requested

  

wontfix

This will not be worked on

No labels

bug

dependencies

documentation

duplicate

enhancement

github_actions

good first issue

help wanted

invalid

question

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

2 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

monolith-os/monolith!27

No description provided.