Skip to content

Flatpak update to 5.10, and flatpak workflow addition#908

Open
mwilck wants to merge 10 commits intoAudiveris:masterfrom
mwilck:master
Open

Flatpak update to 5.10, and flatpak workflow addition#908
mwilck wants to merge 10 commits intoAudiveris:masterfrom
mwilck:master

Conversation

@mwilck
Copy link
Copy Markdown
Contributor

@mwilck mwilck commented Mar 12, 2026

  • Re-added flatpak/flathub submodule
  • flatpak/flathub: set to branch master
  • flatpak/flathub: update to 5.9.0
  • Update flatpak/flathub to current master (5.10.0)
  • flatpak: add junit-bom-5.13.4 dependency
  • flatpak: org.audiveris.audiveris.metainfo.xml: add vcs-browser URL
  • flatpak/flathub: Update to flathub master after 5.10.0 release
  • GitHub workflows: flatpak.yml: enable modifying repo name
  • GitHub workflows: flatpak: enable on PR on release
  • GitHub workflows: add workflow to create flathub PR

mwilck added 10 commits March 11, 2026 23:10
More precisely, 4a4792e ("Merge branch 'master' into development"),
which is a few commits ahead of 5.10.0.
For unknown reasons, this dependency is not detected by flatpakGradleGenerator.
No changes in the flathub code, just added the merge commit.
This allows building flatpaks from forks of the main repository.
Without this, commit SHAs that exist only in the fork won't be found,
and the flatpak builds will fail.
@mwilck
Copy link
Copy Markdown
Contributor Author

mwilck commented Mar 12, 2026

Hi Hervé,

here is the flatpak PR as announced. It includes the new GH workflow for automatic submission to the flathub/org.audiveris.audiveris. The PR submission requires a repository secret FLATHUB_TOKEN containing a personal access token with write permissions to the flathub repo.

As mentioned via email, please indicate if you'd prefer not to re-add the flathub submodule. In this case we should cleanly remove it, and add a gradle property to indicate the path to an independently checked out flathub repository.

Let me know how you wish to proceed.

@hbitteur
Copy link
Copy Markdown
Contributor

Hi Martin,

Is this PR still relevant?
I think not, but I'd like you to confirm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants