tauri-apps/binary-releases

Prebuilt binaries for Tauri projects

binary-releases's Issues

What if the releases can't be download in build process?

Like:
Error failed to bundle project: https://github.com/tauri-apps/binary-releases/releases/download/nsis-3/nsis-3.zip: Network Error: Network Error: Error encountered in the status line:`

Then I try download by hand and extract to C:\Users\user\AppData\Local\tauri, but I get:
Warn NSIS directory is missing some files. Recreating it.

And I can't get more steps by searching in internet

linuxdeploy-aarch64.AppImage is not available

I tried to build arm64 and armhf target of tauri app on linux, but when it try to build AppImage, it failed on downloading https://github.com/tauri-apps/binary-releases/releases/download/linuxdeploy/linuxdeploy-aarch64.AppImage which is not available in https://github.com/tauri-apps/binary-releases/releases/tag/linuxdeploy.

See more details on https://github.com/liudonghua123/pxt-microbit-app/actions/runs/6563010887/job/17826365343#step:11:15055.

Update Linuxdeploy

tauri build has been broken for a while now on up-to-date Linux systems, as it failed on building the AppImage.
This was caused by an update to glibc breaking Linuxdeploy (linuxdeploy/linuxdeploy#210).
This has just now been fixed in linuxdeploy/linuxdeploy#211 , but the linuxdeploy release of this repo still needs to be updated to point to the new artifacts.

CI run of the new version: https://github.com/linuxdeploy/linuxdeploy/actions/runs/2878293346
Fixed AppImage artifact: https://github.com/linuxdeploy/linuxdeploy/suites/7861608611/artifacts/333221700

Describe how this works

This is an important part of our toolchain, but its brittle, adds another dependency in our complex chain of releasing and I am not even sure anymore why we need it. It is not integrated in our automation, and using GitHub as a CDN is fragile. Therefore I feel like we need several things:

• Readme in the style of an architecture.md doc that explains what is here, how it works, why it exists
• Full integration in our release pipeline
• Some type of notifier on the site about the versions
• Distribution mechanism like IPFS or something else that is more resilient