Skip to content

ci: name updater artifacts uniquely; pick them explicitly - #46

Merged
ApocDev merged 1 commit into
mainfrom
ci/fix-updater-artifact-naming
Jun 30, 2026
Merged

ci: name updater artifacts uniquely; pick them explicitly#46
ApocDev merged 1 commit into
mainfrom
ci/fix-updater-artifact-naming

Conversation

@ApocDev

@ApocDev ApocDev commented Jun 30, 2026

Copy link
Copy Markdown
Owner

Two latest.json correctness bugs found in the v0.2.0 build:

  1. macOS collision — both arches emit PyOps.app.tar.gz (no arch), so the second upload clobbers the first; one arch then has a signature that doesn't match the binary. Fix: arch-suffix the macOS .app.tar.gz (+ .sig) — it's updater-only (users get the .dmg), so the rename is invisible.
  2. Linux ambiguity — both the AppImage and the deb get signed, so find … | head -1 could grab the deb (not an updater target). Fix: a per-platform updater glob (AppImage / app.tar.gz / setup.exe) selects the right artifact.

After merge: clear v0.2.0's assets and re-dispatch tag=v0.2.0.

Two latest.json bugs: both macOS arches emit PyOps.app.tar.gz (no arch) so they
clobber each other on upload, and Linux signs both the AppImage and the deb, so
grabbing the first .sig could pick the wrong one. Add a per-platform `updater`
glob to select the right artifact (AppImage / app.tar.gz / setup.exe), and
arch-suffix the macOS .app.tar.gz (+ .sig) so the two don't collide.
@ApocDev
ApocDev merged commit 764e4e0 into main Jun 30, 2026
1 check passed
@ApocDev
ApocDev deleted the ci/fix-updater-artifact-naming branch June 30, 2026 19:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant