fidget/Guksu-Motor
1
0
Fork 0
Code Issues 6 Pull requests Projects Releases 4 Packages Wiki Activity Actions

Remove or redesign inherited Marinara Pre-Alpha Platform Builds #6

New issue
Open
opened 2026-08-05 08:36:55 -04:00 by fidget · 0 comments
fidget commented 2026-08-05 08:36:55 -04:00
Owner
Copy link

Problem

.github/workflows/prealpha-platform-builds.yml is inherited Marinara Engine release infrastructure that cannot run in Guksu Motor as currently configured.

There are zero runs for it in the current 37-run Actions history. Its manual guard requires the refactor branch, but Guksu's live branches are only main, testing, and honcho-fixes.

Infrastructure mismatch

The workflow requires GitHub-hosted capacity that Guksu does not have:

  • ubuntu-latest / ubuntu-22.04
  • windows-latest
  • macos-latest

Guksu has one active NixOS host runner labeled [self-hosted, linux, x64, nix].

The publication path is also GitHub/Marinara-specific:

  • actions/github-script creates and publishes GitHub releases.
  • tauri-apps/tauri-action uploads through GITHUB_TOKEN.
  • gh release upload targets GitHub-style release behavior.
  • actions/upload-artifact@v4 is not automatically compatible with Forgejo's artifact protocol.
  • Product names, release notes, application IDs, and asset names are explicitly Marinara Engine Pre-Alpha.

The workflow has no exact repository-identity guard. If compatible hosted runners were added later, this inherited publisher could create upstream-branded releases and artifacts in the Guksu repository.

Proposed resolution

Choose one fail-closed outcome:

  1. Remove it from Guksu: delete the inherited workflow because Guksu already has separate APK, Windows installer, and container release paths.
  2. Replace it: build a Guksu-owned pre-alpha workflow around the actual Forgejo release API, available runner capacity, Guksu branding/application IDs, and explicit artifact provenance.
  3. Fence it as upstream-only: if retained solely to ease upstream merges, add an earliest exact repository-identity guard that prevents every publishing job from running in fidget/Guksu-Motor.

Acceptance criteria

  • No workflow in Guksu can publish Marinara Engine Pre-Alpha releases or application identities.
  • No job requests unavailable GitHub-hosted runner labels.
  • A retained upstream-only workflow fails closed before checkout, release creation, or artifact publication.
  • A Guksu replacement uses Forgejo-compatible release/asset APIs and compatible artifact actions.
  • Every artifact is branded for Guksu and bound to the selected source commit.
  • A real manual test proves draft creation, artifact upload, finalization, and prerelease/not-latest behavior without touching stable aliases.
## Problem `.github/workflows/prealpha-platform-builds.yml` is inherited Marinara Engine release infrastructure that cannot run in Guksu Motor as currently configured. There are zero runs for it in the current 37-run Actions history. Its manual guard requires the `refactor` branch, but Guksu's live branches are only `main`, `testing`, and `honcho-fixes`. ## Infrastructure mismatch The workflow requires GitHub-hosted capacity that Guksu does not have: - `ubuntu-latest` / `ubuntu-22.04` - `windows-latest` - `macos-latest` Guksu has one active NixOS host runner labeled `[self-hosted, linux, x64, nix]`. The publication path is also GitHub/Marinara-specific: - `actions/github-script` creates and publishes GitHub releases. - `tauri-apps/tauri-action` uploads through `GITHUB_TOKEN`. - `gh release upload` targets GitHub-style release behavior. - `actions/upload-artifact@v4` is not automatically compatible with Forgejo's artifact protocol. - Product names, release notes, application IDs, and asset names are explicitly `Marinara Engine Pre-Alpha`. The workflow has no exact repository-identity guard. If compatible hosted runners were added later, this inherited publisher could create upstream-branded releases and artifacts in the Guksu repository. ## Proposed resolution Choose one fail-closed outcome: 1. **Remove it from Guksu:** delete the inherited workflow because Guksu already has separate APK, Windows installer, and container release paths. 2. **Replace it:** build a Guksu-owned pre-alpha workflow around the actual Forgejo release API, available runner capacity, Guksu branding/application IDs, and explicit artifact provenance. 3. **Fence it as upstream-only:** if retained solely to ease upstream merges, add an earliest exact repository-identity guard that prevents every publishing job from running in `fidget/Guksu-Motor`. ## Acceptance criteria - [ ] No workflow in Guksu can publish `Marinara Engine Pre-Alpha` releases or application identities. - [ ] No job requests unavailable GitHub-hosted runner labels. - [ ] A retained upstream-only workflow fails closed before checkout, release creation, or artifact publication. - [ ] A Guksu replacement uses Forgejo-compatible release/asset APIs and compatible artifact actions. - [ ] Every artifact is branded for Guksu and bound to the selected source commit. - [ ] A real manual test proves draft creation, artifact upload, finalization, and `prerelease`/not-latest behavior without touching stable aliases.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
testing
honcho-fixes
v2.4.4a
v2.3.5c
v2.3.5b
v2.3.5a
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
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
fidget/Guksu-Motor#6
No description provided.