tauri icon indicating copy to clipboard operation
tauri copied to clipboard

[feat] improve naming convention for updater files

Open thewh1teagle opened this issue 1 year ago • 0 comments

Describe the problem

When using tauri/updater the current generated update file is app.tar.gz or myapp-setup.nsis.zip and as you can see it doesn't include the architecture of the update, and that's mean that many times developers will need to handle themself the naming of it, for instance, I host static json in Github and upload updater files (.tar.gz) using Github action into Github releases currenly I need to handle it myself and change the name to the current architecture.

Describe the solution you'd like

Use naming convention for update files, similar how you already do with the installer files. eg: app_0.0.4_aarch64.dmg app_0.0.2_x64-setup.exe

instad of app.tar.gz

Alternatives considered

No response

Additional context

In general, the updater need a little enhancments. We can easily use Github action + static JSON for uploading the updater files to Github releases and updating the static JSON file automaticlly from CI. Currently users needs to find their way to use Github actions for automatically upload updater files (.sig, .tar.gz) and update the static JSON file and handling naming conventions

Another things: The updater continue asking for update everytime the user opens the app even after choosing no

The docs shows the update files with their architecture so I'm wondering if maybe that's already possible and I missed it

That's probably because tauri action does the magic tauri-action/src/utils.ts#L44

thewh1teagle avatar Feb 03 '24 17:02 thewh1teagle