Repository navigation
Commit 67917a9
committed
fix(release): let a fork publish latest.json, unblocking desktop auto-update
Auto-update was not missing on this fork, it was one file short. The
buzz-desktop-latest rolling release already holds the AppImage and Windows
installer with their .sig files, BUZZ_UPDATER_ENDPOINT already points at this
repo, the .sig files already verify against this fork's own signing key, and the
app already polls on mount and every 6h. Only latest.json was never uploaded.
assemble-manifest gated on `[ ${#TRIPLES[@]} -ge 3 ]`. Both macOS jobs stay
pinned to block/buzz because Block's codesigning service is unreachable here, so
they skip, only linux + windows remain, and the job died on "too few platforms
(2)" every run.
I had written in AGENTS.md not to fix this by lowering the threshold, and this
does not. The count was a proxy for "no platform is missing" that could not tell
a job that skipped from a job that broke. Asserting on the job results says what
was meant, and is *stricter* than what it replaces: `-ge 3` passed when one macOS
platform failed -- 3 of 4 succeeded -- publishing a manifest that silently
stranded that platform's existing installs. That case now fails.
success | skipped -> fine (skipped == structurally not built for this repo)
anything else -> attempted and did not deliver, so publishing strands it
The remaining count check is a floor for the config error where every platform
skips at once, which the result loop alone would pass.
Exercised the guard over six result combinations before committing: fork today
(2 platforms, publishes), upstream all green (4, publishes), upstream one macOS
failed (blocks -- the case the old rule let through), fork with linux broken
(blocks), everything skipped (blocks), cancelled windows (blocks). YAML parses.
Only this fork is affected: syncs flow upstream -> fork, so the change cannot
reach block/buzz's own copy.
Untouched, and documented as such: macOS gets no auto-update here, and not
because of this guard -- macos-canary.yml passes no BUZZ_UPDATER_*, so build.rs
leaves buzz_updater_enabled unset and tauri_plugin_updater is never registered.
.deb stays non-updatable per Tauri.
Signed-off-by: adrienlacombe <[email protected]>1 parent 813279d commit 67917a9
2 files changed
Lines changed: 59 additions & 11 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
989 | 989 | | |
990 | 990 | | |
991 | 991 | | |
992 | | - | |
| 992 | + | |
| 993 | + | |
| 994 | + | |
| 995 | + | |
| 996 | + | |
| 997 | + | |
| 998 | + | |
| 999 | + | |
| 1000 | + | |
| 1001 | + | |
| 1002 | + | |
| 1003 | + | |
| 1004 | + | |
| 1005 | + | |
| 1006 | + | |
| 1007 | + | |
| 1008 | + | |
| 1009 | + | |
| 1010 | + | |
| 1011 | + | |
| 1012 | + | |
| 1013 | + | |
| 1014 | + | |
| 1015 | + | |
| 1016 | + | |
| 1017 | + | |
| 1018 | + | |
| 1019 | + | |
| 1020 | + | |
| 1021 | + | |
| 1022 | + | |
| 1023 | + | |
| 1024 | + | |
| 1025 | + | |
| 1026 | + | |
| 1027 | + | |
| 1028 | + | |
993 | 1029 | | |
994 | 1030 | | |
995 | 1031 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
93 | 93 | | |
94 | 94 | | |
95 | 95 | | |
96 | | - | |
| 96 | + | |
97 | 97 | | |
98 | 98 | | |
99 | 99 | | |
| |||
196 | 196 | | |
197 | 197 | | |
198 | 198 | | |
199 | | - | |
200 | | - | |
201 | | - | |
202 | | - | |
203 | | - | |
204 | | - | |
205 | | - | |
206 | | - | |
207 | | - | |
| 199 | + | |
| 200 | + | |
| 201 | + | |
| 202 | + | |
| 203 | + | |
208 | 204 | | |
209 | 205 | | |
210 | 206 | | |
211 | 207 | | |
| 208 | + | |
| 209 | + | |
| 210 | + | |
| 211 | + | |
| 212 | + | |
| 213 | + | |
| 214 | + | |
| 215 | + | |
| 216 | + | |
| 217 | + | |
| 218 | + | |
| 219 | + | |
| 220 | + | |
| 221 | + | |
| 222 | + | |
| 223 | + | |
212 | 224 | | |
213 | 225 | | |
214 | 226 | | |
| |||
0 commit comments