enricobuehler 91b8f1a939 ci(android): a manual dispatch can publish, so a lost merge run is not a dead end ...

Merging two PRs seconds apart can leave the older merge sha with no run at all -
Gitea attributes the window's runs to the newer head. 1e5dca4c (PR #235, the pad
Select/KEYCODE_BACK fix) lost its run to b5cace3a 12 s later and reached main
having never been built, so no canary carries it.

Re-running the PR run cannot recover that: a re-run replays the original
pull_request event, and all four publish steps are gated on a push, so they stay
skipped. Until now the only cure was inventing a filler push touching one of
android.yml's paths.

Add a workflow_dispatch 'publish' input, default false, and widen the four gates
to accept a dispatch that opts in. A plain manual run stays build-only, so a
stray click still cannot reach testers. String-typed and compared against 'true'
to match apple.yml's testflight input, the form proven on this Gitea.

2026-08-14 22:55:13 +02:00

..

releases

ci(android): a manual dispatch can publish, so a lost merge run is not a dead end

2026-08-14 22:55:13 +02:00

embedding-the-c-abi.md

feat(abi/apple): carry the trigger motors to non-Rust clients — ABI 18, next_rumble_cmd2

2026-08-09 23:30:02 +02:00