search

flathub / eu.betterbird.Betterbird

https://flathub.org/apps/details/eu.betterbird.Betterbird
9 stars 1 forks source link

How does upstream notify of new versions? #6

Closed Betterbird closed 2 years ago

Betterbird commented 2 years ago

Hi @hfiguiere and @mfschumann: New version 102.2.1-bb15, see https://github.com/Betterbird/thunderbird-patches/commit/526010ec03eb942a5f5379d402386a6b6c890b44. How does upstream notify you?

Change eu.betterbird.Betterbird.appdata.xml for now?

Also please note for issue #2 that if you build from source, you'll have to build against the corresponding tag, in this case 102.2.1-bb15.

mfschumann commented 2 years ago

I will look into setting up a GitHub action that watches for new tags or changes to the .appdata.xml in your repo.

Betterbird commented 2 years ago

So should we edit the "local" XML file to trigger a new build?

mfschumann commented 2 years ago

Actually I think it's best to trigger only on a new tag in your repo. Like that we can use a workflow like this:

  1. You update the version in .appdata.xml some time during preparing the next release.
  2. Once the release is ready, you push a tag containing the version number of the release to your repo (just as you already do), triggering a github action in my repo.
  3. The github action updates the flatpak manifest for the new version, commits the changes and creates a pull request.
  4. The pull request triggers the flathub build bot to create a test build.
  5. Once I have tested the created flatpak, I complete the pull request, triggering the flathub build bot to create an official build that will be published.

The only piece that's missing to realize this automated workflow is the github action in step 3, so this step is currently manual.

Betterbird commented 2 years ago

I'm fine with triggering the flatpak via the application of the tag.

mfschumann commented 2 years ago

So I'll close this issue. Implementing the GitHub action is tracked in #9.