Hello! I started versioning the app with year.minor.patch - 2023.1.5 for example. Now that I'm working on the windows build, I noticed the windows bundler refuses to accept this - max for major i 255. So, I'm trying to move to 23.1.5 instead. I changed my update server to support this, but tauri silently discards the update since it's "older" when comparing semver. Any workaround?
#"Downgrade" version number via updater
sick willow
gusty moss
generally it's possible but it requires 2 configs, one of which in the "old" app on the user's system you wanna upgrade.
In Rust: https://docs.rs/tauri/latest/tauri/updater/struct.UpdateBuilder.html#method.should_install - though i'm not sure if that works with the default dialog rn 🤔
In tauri.conf.json: https://tauri.app/v1/api/config#windowsconfig.allowdowngrades
The idea once was to always listen to what the dynamic update server (not the static one) tells the client but somehow that never got in without these configs :(
sick willow
Thanks!
sick willow
Do I have to use active: false in my tauri conf in order to only use my own UpdateBuilder?
gusty moss
that depends on how tauri sets the example from the method i linked. If it re-uses it for the default one, then no. If it doesn't use it then maybe. i think it should be fine to let the default config run on app start in this scenario, if it doesn't like the update's version it will just skip it and your own builder can take over