You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, as you may remember there were arm build issues discussed in #236.
This is fixed now, but only on master branch.
However for flathub I usually only build from tags as this is what works with the update checker. Currently, while building from git master, the update checker is somewhat confused and suggests downgrades to the v2.10.0 tag.
A new fix release (2.10.1) would help with that.
Thanks :)
The text was updated successfully, but these errors were encountered:
Hi! Yes, I can definitely see how that would be helpful for packaging. Unfortunately, whenever I tag a release on GitHub, everyone who uses the plugin will see a screen asking them if they would like to update to the latest release the next time they open it. For that reason, I try to avoid tagging releases, except when there are new features/big fixes that folks can enjoy when they install the new version.
I wonder if this issue could be avoided via the "meta" repository we were discussing... that way we can tag releases in that repo whenever any plugin is updated and it won't affect the individual plugin repos?
Okay can see the problem here, didn't know the plugin has a built in update checker. In this case let's not annoy all the users with a new release which doesn't bring anything new to the table.
The meta repo could indeed solve it in this case so let's focus on that. I commented now on that corresponding issue.
Thanks a lot for working on this :)
Hi, as you may remember there were arm build issues discussed in #236.
This is fixed now, but only on master branch.
However for flathub I usually only build from tags as this is what works with the update checker. Currently, while building from git master, the update checker is somewhat confused and suggests downgrades to the v2.10.0 tag.
A new fix release (2.10.1) would help with that.
Thanks :)
The text was updated successfully, but these errors were encountered: