Skip to content

Release controller: owner-only exact-SHA comments, tri-OS roadmap, landing-only downloads #450

Open

Description

@masarray

Milestone B verified triage — 2026-11-17: P1 / release / operations / operational. Classification ≠ completion of product feature or physical FAT.

Scope / release boundary: Intentionally OPEN owner-authenticated release command endpoint.

Exit criteria:

  • Keep issue number 450 open for owner-only exact-SHA /arsonmix-release, /arsonmix-port and /arsonmix-publish commands; never close or repurpose it as bug board.
  • For each release prove immutable SHA, valid provenance/checksums, installer/portable success and Pages static catalog parity; reject duplicate/stale release requests.

Canonical issue ledger. Preserve historical evidence below; no speculative merging or rewriting approved audio.


CURRENT CHECKPOINT — 2026-11-08 (main c57720ea25585c861af89802e1365ffef7d03d17)

Release controller stays OPEN intentionally. It is the owner-authenticated issue-comment dispatch endpoint; closing it would obscure ongoing release operations. Exact-source Windows tag v0.5.0-alpha.5 at d7cf109ad1d45f0666431ce748d72572dd49facc exists. Linux native workflow #42446499625 and macOS #42446684702 both completed SUCCESS; native .tar.gz and universal .dmg assets are uploaded to the same tag, with per-OS provenance/checksums. Owner commands /arsonmix-release, /arsonmix-port and /arsonmix-publish are implemented in scripts/release_ci_dispatch.mjs. No duplicate same-SHA dispatch. Primary marketing host is Cloudflare Pages; GitHub Pages still publishes the same one GUI. At this checkpoint Cloudflare's static release-catalog.json had Windows only despite GitHub Pages already listing all three, so a fresh Pages build/deployment is required before closing release distribution acceptance.


Internal release controller — no manual owner Actions buttons

Agent-driven, cost-aware release qualification. This issue is not user-facing. User interaction stays at https://masarray.github.io/arsonmix/ (download buttons only).

After the fast PR and main qualification has passed, agent may post exactly one owner-authenticated comment:

/arsonmix-release v0.5.0-alpha.N <40-character release-candidate branch SHA>

The dispatcher must check OWNER identity, exact immutable releases/alpha/v0.5.0-alpha.N ref/commit, duplicate requests, already-published versions, and existing same-SHA run before requesting ONE release build. Release promotion must verify CTest and native app, portable package, Inno upgrade/uninstall, SHA256 and FactoryFX integrity, then publish and refresh the landing catalog. No push/schedule-based full release builds.

Linux/macOS are not released by relabeling Windows binaries. They require genuine cross-platform JUCE host backend portability, native compilation/installer, offline audio/Show tests and exact-SHA platform qualification. Gating them must not delay Windows mixer development. This issue stays open until full source-porting/release and non-GitHub user download workflow is verified.

Do not post the trigger speculatively: verify fresh main / active PR state and current SHA in the same interaction.

Activity

  1. masarray commented on Nov 8, 2026

    @masarray
    OwnerAuthor

    /arsonmix-release v0.5.0-alpha.2 30d7fa7

  2. masarray commented on Nov 8, 2026

    @masarray
    OwnerAuthor

    /arsonmix-release v0.5.0-alpha.3 1dcc699

  3. masarray commented on Nov 8, 2026

    @masarray
    OwnerAuthor

    /arsonmix-release v0.5.0-alpha.4 7447d82

  4. masarray commented on Nov 8, 2026

    @masarray
    OwnerAuthor

    2026-11-08 release reconciliation — Windows / Linux / macOS (repo audit, exact source)

    Authority: main 7447d82e84a52e583c7e4c30b9a7bbcded1abd11; integration #418 and installer / landing PRs #443, #445–#452, #454–#455 are merged. Do not create duplicate UI/engine or publisher branches. The scope is public delivery of the actual native mixer, not a screenshot/mock or differently named Windows EXE.

    Windows: v0.5.0-alpha.1 is a real published prerelease with verified native Setup.exe + Portable.zip and provenance. The next candidate v0.5.0-alpha.4 is currently in_progress, run https://github.com/masarray/arsonmix/actions/runs/42435834943; do not call it passed or available before CTest, native executable verification, Inno install/upgrade/uninstall, six asset uploads and Pages catalog refresh complete. Alpha.2 failed because its exact-SHA release notes were absent; Alpha.3 had a false PowerShell failure after an expected gh release view exit=1. #454/#455 remediate those issues; no repeated same-SHA runs.

    Linux/macOS are not public native binaries yet. Actual source blockers, currently detected by scripts/check_platform_portability.py:

    1. src/Main.cpp::webViewOptions selects Windows WebView2 rather than macOS/Linux WebKit, and WebView2-specific startup messages require a platform adapter. JUCE 8 supports native integration on WebKit, but it must be exercised with the same approved offline /preview/ bundle and native JS ACK/readback contract.
    2. CMakeLists.txt unconditionally enables Windows-only WebView2 and ASIO/WASAPI compile flags. Must conditionally retain these on Windows and use JUCE CoreAudio on macOS or ALSA/JACK on Linux without weakening ASIO priority on Windows.
    3. The initial fallback in src/LiveAudioEngine.h assumes Windows Audio; platform startup must choose verified actual backend/device identities and fail closed, never spoof PCM/FX/monitoring.
    4. No scripts/package_native_linux.sh or scripts/package_native_macos.sh; crossplatform workflow currently builds/CTest only, has no verifiable binary packaging or authorized public release publisher. A green cross-platform build alone must not enable its landing download.

    Cost-aware path: Stage A: one scoped port PR, pure/static portability tests and existing lightweight path-filtered contracts; no native paid runs during iteration. Stage B: one explicit owner-comment /arsonmix-port linux <branch> <sha> for cheap preflight then actual Ubuntu native compile/CTest. Repair genuine failures before next SHA; separately do one macOS lane only after its gate is ready. Stage C: independently verify genuine ELF x86_64 distribution and macOS .app/.dmg, runtime dependency closure, exact source/build SHA, VST3 and approved GUI signatures, checksums and OS-specific provenance. macOS signing/notarization policy must be explicit; do not mislabel an ad-hoc/unsigned app as trusted. Stage D: add platform assets to an explicitly owner-authorized source-matched prerelease without replacing Windows assets, re-evaluate the strict same-origin release-catalog.json, deploy via Pages, and verify actual direct downloads. Release catalog must remain null for unsupported OS.

    Release protocol: Never schedule a 3-OS matrix on ordinary commits or blind reruns. Do not trigger Windows again while Alpha.4 is active. A valid Windows installer and an unavailable Linux/macOS button is better than fabricated public support. Any OS binary needs native CTest + packaging/hash + landing-button verification; real physical CoreAudio/ALSA/ASIO listening FAT remains PENDING until measured on hardware. End-user journey is only https://masarray.github.io/arsonmix/ — no GitHub Actions, pull request or Release-page interaction needed.

  5. masarray commented on Nov 8, 2026

    @masarray
    OwnerAuthor

    /arsonmix-port linux feat/native-linux-macos-owner-release-20261108 5fcbc85

  6. masarray commented on Nov 8, 2026

    @masarray
    OwnerAuthor

    /arsonmix-port macos feat/native-linux-macos-owner-release-20261108 f65de53

  7. masarray commented on Nov 8, 2026

    @masarray
    OwnerAuthor

    /arsonmix-port linux feat/native-linux-macos-owner-release-20261108 bb8f119

  8. masarray commented on Nov 8, 2026

    @masarray
    OwnerAuthor

    /arsonmix-port macos feat/native-linux-macos-owner-release-20261108 2ba73c5

  9. masarray commented on Nov 8, 2026

    @masarray
    OwnerAuthor

    /arsonmix-release v0.5.0-alpha.5 d7cf109

  10. masarray commented on Nov 8, 2026

    @masarray
    OwnerAuthor

    2026-11-08 — approved open-source tri-OS release distribution checkpoint

    Source authority: main@d7cf109ad1d45f0666431ce748d72572dd49facc; #459 merged native Linux/macOS; #461 merged Windows installer ZIP + latest-release-aware official landing.

    Evidence already green:

    Candidate Alpha.5: exact branch releases/alpha/v0.5.0-alpha.5 at d7cf109ad1d45f0666431ce748d72572dd49facc, approved by owner comment; Windows publisher https://github.com/masarray/arsonmix/actions/runs/42444286494 (DO NOT claim published until success). Windows release must include Setup.zip containing byte-identical verified Inno Setup.exe, plus direct EXE and portable ZIP, SHA256SUMS and provenance (7 assets).

    Next exact-source gates: after Alpha.5 Windows public release is confirmed at the same SHA, owner may issue /arsonmix-publish linux v0.5.0-alpha.5 d7cf109ad1d45f0666431ce748d72572dd49facc, then /arsonmix-publish macos v0.5.0-alpha.5 d7cf109ad1d45f0666431ce748d72572dd49facc, one OS at a time. Each native publisher independently rebuilds/CTest/packages/signs ad-hoc if macOS and uploads only its exact native OS binary. Never launch a 3-OS automatic matrix, recycle an unsuccessful SHA or claim hardware FAT.

    Landing behavior: one same-origin static verified catalog; one optional read-only GitHub public release freshness check, fail-closed validated URLs/assets/digests and fallback when rate-limited. Windows ZIP prioritized over EXE on the newest version, while older releases remain accessible. ZIP does not bypass SmartScreen/Gatekeeper automatically.

    Windows Alpha.4 remains the last confirmed public download until Alpha.5 publish actually completes.

  11. masarray commented on Nov 8, 2026

    @masarray
    OwnerAuthor

    /arsonmix-publish linux v0.5.0-alpha.5 d7cf109

  12. masarray commented on Nov 8, 2026

    @masarray
    OwnerAuthor

    /arsonmix-publish macos v0.5.0-alpha.5 d7cf109

  13. masarray commented on Nov 8, 2026

    @masarray
    OwnerAuthor

    /arsonmix-port linux releases/alpha/v0.5.0-alpha.6 d6b7d6c

  14. masarray commented on Nov 8, 2026

    @masarray
    OwnerAuthor

    /arsonmix-port macos releases/alpha/v0.5.0-alpha.6 d6b7d6c

  15. masarray commented on Nov 9, 2026

    @masarray
    OwnerAuthor

    /arsonmix-port linux releases/alpha/v0.5.0-alpha.6 b2e1ff3

  16. 12 remaining items

  17. masarray commented on Nov 12, 2026

    @masarray
    OwnerAuthor

    /arsonmix-release v0.5.0-alpha.17 d30d7f4

  18. masarray commented on Nov 13, 2026

    @masarray
    OwnerAuthor

    /arsonmix-release v0.5.0-alpha.18 98ef30d

  19. masarray commented on Nov 13, 2026

    @masarray
    OwnerAuthor

    /arsonmix-release v0.5.0-alpha.19 746877e

  20. masarray commented on Nov 13, 2026

    @masarray
    OwnerAuthor

    /arsonmix-release v0.5.0-alpha.20 6cb5956

  21. masarray commented on Nov 13, 2026

    @masarray
    OwnerAuthor

    /arsonmix-release v0.5.0-alpha.21 1eb8e62

  22. masarray commented on Nov 13, 2026

    @masarray
    OwnerAuthor

    /arsonmix-release v0.5.0-alpha.22 906a3c6

  23. masarray commented on Nov 13, 2026

    @masarray
    OwnerAuthor

    /arsonmix-release v0.5.0-alpha.23 f31f4c2

  24. masarray commented on Nov 17, 2026

    @masarray
    OwnerAuthor

    /arsonmix-release v0.5.0-alpha.24 e9c5bdb

  25. masarray commented on Nov 17, 2026

    @masarray
    OwnerAuthor

    /arsonmix-release v0.5.0-alpha.25 9abfb00

  26. masarray commented on Nov 17, 2026

    @masarray
    OwnerAuthor

    /arsonmix-release v0.5.0-alpha.26 8ec5b8a

  27. masarray commented on Nov 17, 2026

    @masarray
    OwnerAuthor

    /arsonmix-release v0.5.0-alpha.27 a93759d

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions