Repository navigation
ci: lean native/GUI gates, single release artifact and stale-safe Pages - #101
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Cross-thread synchronization (2026-10-28): approved source |
|
Update (2026-10-28): |
|
CI sync · 2026-10-28. Main at |
…s, fast UI gate and safe Pages
108e281 to
79408c2
Compare
Motivation
Recent ArSonMix PR history shows Windows Release MSVC and both Chromium+Firefox executing for every iterative PR, including GUI-only changes. Subsequent Pages deployment is appropriately gated on a successful main UI run but can enqueue obsolete revisions. Avoid burning Windows runners or waiting on unneeded browser installs while preserving the one verified Windows FAT artifact.
Changes
mainruntime/native inputs trigger a release build (including shippedweb/**); PR runs when changes can affect native JUCE/engine, CMake, Windows packaging or native test contracts. Remove ancient named-branch push triggers. PR still performs Release MSVC, CTest, packaging and independent ZIP provenance audit, but no automatic artifact upload.workflow_dispatchexplicitly builds+uploads FAT for a branch.mainproduces one verified ZIP after merge.mainpush UI runs may auto-publish. Resolve checked-out qualified SHA against currentmainbefore building/deploying; obsolete queued publishers skip cleanly. Do not introduce competing deploy workflows.docs/CI_WORKFLOW_STRATEGY_20261028.mddescribe expected behavior and required-check caveat. No modifications to DSP, GUI, Orbit or release packaging scripts.Verification gates