I managed to get the update checker plugin running (didn't really do anything, 
it started working with the latest library versions from gtk-osx). So I might 
add it to the next macOS release.

> I thought I had seen @techee make bugfix builds on the geany-osx repository, 
> I guess if they get uploaded to the Geany website that would be ok, but then 
> whats their version, if its the same then the update checker won't notice?

The URL

https://geany.org/service/version/

which the plugin uses only returns the latest Geany release version and not the 
actual build. I was forced to make a new macOS release when e.g. a new macOS 
release broke something in GTK and I needed to re-package the release with the 
latest GTK libraries containing the fix. Geany itself was the same though so 
the update checker wouldn't see such a change.

What I could imagine we could do is to send the current version and the build 
date to the server (which can be seen on the About page of Geany, such as 
`built on or after 2024-06-21`) and I think it would actually be best to leave 
the whole logic of whether the update is available or not on the server - it 
would just return `TRUE` or `FALSE` based on the info we send from the plugin. 
This would probably require a new URL, such as 
`https://geany.org/service/version/v2`.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1314#issuecomment-2194935826
You are receiving this because you are subscribed to this thread.

Message ID: <geany/geany-plugins/issues/1314/[email protected]>

Reply via email to