packaging(flatpak): CI build/validate check + Flathub auto-update prep#372
Closed
adibhanna wants to merge 3 commits into
Closed
packaging(flatpak): CI build/validate check + Flathub auto-update prep#372adibhanna wants to merge 3 commits into
adibhanna wants to merge 3 commits into
Conversation
Add .github/workflows/flatpak-check.yml, mirroring aur-check.yml: it runs appstreamcli + desktop-file-validate on every change and a full flatpak-builder against the freedesktop 25.08 runtime once the release AppImage is published, so the package is verified without a Linux box. Add x-checker-data (GitHub releases JSON query) to the manifest so Flathub's flatpak-external-data-checker auto-opens url/sha256 bump PRs on each release. Rewrite the README's publishing section with the real org.zennotes.ZenNotes submission steps and drop the stale com.adibhanna app-id note (the id maps to zennotes.org, which we own).
Flathub's flatpak-builder-lint rejects broad --filesystem=home (finish-args-home-filesystem-access), which failed the submission's manifest validation. Grant xdg-documents/xdg-download/xdg-desktop instead; vaults kept elsewhere can be re-granted via Flatseal.
Flathub builds x86_64 AND aarch64; the manifest hardcoded the x64 AppImage, so the arm build failed with 'Exec format error'. Split into only-arches x86_64/aarch64 sources pointing at the x64 and arm64 AppImages (both already shipped in each release), each with its own x-checker-data.
Contributor
Author
|
Closing — we've decided not to ship on Flathub, and Flatpak packaging has been removed entirely (see main). Linux stays covered by the GitHub installers, AUR, Nix, and Docker. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Prep so ZenNotes can be published to Flathub and verified without a Linux machine.
.github/workflows/flatpak-check.yml— mirrorsaur-check.yml. Validates AppStream metainfo (appstreamcli validate) and the desktop entry on every change, and runs a fullflatpak-builderagainst the freedesktop 25.08 runtime once the release AppImage is published (skips the build, like the AUR check, when the asset isn't up yet).x-checker-dataon the manifest — Flathub'sflatpak-external-data-checkerwill auto-open url/sha256 bump PRs on each GitHub release.org.zennotes.ZenNotesFlathub submission steps; dropped the stalecom.adibhannaapp-id note (the id maps tozennotes.org, which we own).Verified locally
Full Linux
flatpak-builderruns in the new CI job on this PR.