Add source-git-branch exception-to pegasus frontend

[j8r]

Likely what's the maintainer @mmatyas wish to (flathub/org.pegasus_frontend.Pegasus#44).

Update: this is required for a weekly update x-checker cron (flathub/org.pegasus_frontend.Pegasus#49)

[hfiguiere]

No. commit+branch mean the build WILL fail as soon as the branch HEAD changes. There is no going around.

Flathub is NOT for nightly builds.

[j8r]

There is commit and a branch, currently:

 - type: git
   url: https://github.com/mmatyas/pegasus-frontend.git
   branch: master
   commit: cc2497abf7ebb12e0cbdb57a16addaf62d6f50bd

The goal is to update the commit to the latest one in master, which is the latest release.
If not possible, we'll have to find another workaround then...

@mmatyas do you confirm that the latest commit in master is considered a stable release and not a nightly one? Otherwise, I guess an other release cycle will have to be found.

[barthalion]

Just drop specifying the branch? I’m not sure what you want to accomplish by setting both if the branch is rolling.

[bbhtt]

I guess an other release cycle will have to be found.

Yes please, one that doesn't involve updating daily to a new commit or tag or whatever.

If you want to do that, either update it with a custom workflow once a week like I mentioned in the original issue above or you are free to host it externally.

Doing nightlies is not sustainable for the infra.

[j8r]

Once a week sounds good, let's do like RPCS3. To have this flathub/org.pegasus_frontend.Pegasus#49 work, an exception will still be needed though?
Or, we'll have to make a custom script for that purpose 🤔

[j8r]

If I understand correctly the issue, this is more about the frequency of builds than the nature of the release?
For example, a stable release per day is more problematic than a nightly build per month.

[bbhtt]

Frequency is a problem for the infra as well as having software that is not "stable". End users expect software from Flathub to be stable, Nightly belongs in upstream CI.

an exception will still be needed though?

It's needed, can you update it to mention it's for x-checker, and a weekly custom workflow has been implemented.

[mmatyas]

@mmatyas do you confirm that the latest commit in master is considered a stable release and not a nightly one? Otherwise, I guess an other release cycle will have to be found.

The latest stable release is the last commit with an annotated Git tag (see https://github.com/mmatyas/pegasus-frontend/releases). I assume this would require a daily-running script, but if it's too much trouble, I'm fine with a weekly workflow too.

I also had good experience with externally hosting an auto-updated Flatpak release; we can set one up for nightlies if necessary.

[bbhtt]

If you switch to those weekly_ tags, exception is not needed anymore.

[j8r]

What do we do then @mmatyas, have a weekly cron taking the latest commit with the continuous tag?

[mmatyas]

Yes, that sounds good to me.