ci(desktop): publish Linux .deb + .AppImage bundles #128
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/lc-132-publish-linux-bundles"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Closes LC-132. Switches
build-desktop-linux.ymlandpublish-release.ymlfromDockerfile.desktop-linuxtoDockerfile.desktop-linux-bundlesso each push tomainand eachv*tag now publish a.deband an.AppImageto the Generic Packages registry alongside the raw binary.Filenames
Stable filenames on the registry side so the release manifest can hard-code download URLs:
lets-chat-desktop-linux-x86_64(raw binary, unchanged)lets-chat-desktop-linux-amd64.deblets-chat-desktop-linux-amd64.AppImageTauri stamps the bundles with the crate version (
lets-chat_0.1.0_amd64.deb, etc.); the workflow resolves the actual filenames vials artifacts/bundle-linux/*.deb | first | get nameso a future version bump does not require updating the upload step.Manifest
latest.jsongainslinux_debandlinux_appimageURL entries. The raw binary path stays unchanged so the existing desktop self-updater (update.rs) keeps working with no client-side change.Skipped the optional
$APPIMAGE-aware updater detection mentioned in LC-132; minimal solution first, can land as a separate follow-up if needed.Test plan
python3 -c 'import yaml; yaml.safe_load(open(f))'on both workflow files.just build-desktop-linux-bundles(local mirror of the CI bundle build) produceslets-chat_0.1.0_amd64.debandlets-chat_0.1.0_amd64.AppImageunderartifacts/bundle-linux/.nu -c 'ls artifacts/bundle-linux/*.deb | first | get name'resolves the right file (validates the filename-resolution snippet used in CI).${PACKAGE_OWNER}/generic/lets-chat/latest/.v*tag publishes thelatest.jsonmanifest withlinux_deb+linux_appimageURLs that resolve.