Okay, this is almost ready to go, I just need to figure out where to place the update checking logic in frontend. @Alystrasz any suggestions? ^^

Okay, this is almost ready to go, I just need to figure out where to place the update checking logic in frontend. @Alystrasz any suggestions? ^^

Sorry for the late answer, thought I answered already!
I'd suggest placing it in the most top-level component, namely App.vue.

Okay, this is almost ready to go, I just need to figure out where to place the update checking logic in frontend. @Alystrasz any suggestions? ^^

Sorry for the late answer, thought I answered already! I'd suggest placing it in the most top-level component, namely App.vue.

Actually, we can do even better, and put it in the store.ts module.
@GeckoEidechse there is already a _checkForFlightCoreUpdates method in there, should I replace it with your new update logic?

Well, done in ed42fd2.
@GeckoEidechse how do you simulate a new flightcore version being available? (to test the popup)

@GeckoEidechse how do you simulate a new flightcore version being available? (to test the popup)

Uh, idk if Tauri does the check for != or > current version. Need to check the docs. I think you can set it to strict and then it should prompt for update on any version difference, though idk if you also need the signing key to be set for that

Uh, idk if Tauri does the check for != or > current version. Need to check the docs. I think you can set it to strict and then it should prompt for update on any version difference, though idk if you also need the signing key to be set for that

I'm not sure we can do that, since the update checking magic is done by the updater plugin itself in the check method.
Also, looking at this official guide, I don't think we can test the update process without releasing builds...

Then we'll have to test in prod :>

Then we'll have to test in prod :>

You'll probably have to setup the CI somehow then :)