Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Build] Implement Flathub publishing for Linux (post-beta) — per ADR-003

Open
#491 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
dart, linux

Research direction

Start with docs/adr/003-linux-native-distribution-channel.md and ROADMAP 7.1 to confirm the distribution decision and post-beta timing. Then inspect the release assets and the app's beta.json/stable.json update check; implement the manifest, metainfo, desktop entry, icons, and Flatpak-aware banner behavior described here. Done means the acceptance criteria pass and the Flathub listing is live with store-managed updates.

Written by the indexing model from the issue text.

Description

area: packaging platform: linux priority: low stable status: blocked type: enhancement

Implementation follow-up to the ADR-003 decision (evaluation in #306): publish Caller's Compendium to Flathub as the first native Linux distribution channel, post-beta.

Blocked-until: post-beta (see ROADMAP 7.1). This is deliberately deferred; the beta ships fine on the GitHub Releases AppImage/tar.gz baseline.

Scope (from ADR-003)

  • Author the Flatpak manifest org.callerscompendium.compendiumApp.yml (freedesktop runtime; source the published, checksum-verified …-linux-x64.tar.gz release asset), plus AppStream metainfo, a .desktop entry, and icons.
  • Keep the sandbox tight: minimal finish-args, prefer XDG desktop portals for the file chooser and printing over broad --filesystem access.
  • Submit to Flathub (flathub/flathub PR for org.callerscompendium.compendiumApp); pass review.
  • Release automation: bump the pinned tag + sha256 on each GitHub Release (or wire Flathub's update bot) so Flathub rebuilds from the verified tarball.
  • App code: make the in-app update check Flatpak-aware — detect running-under-Flatpak (FLATPAK_ID / /.flatpak-info) and suppress/soften the Stage-1 update banner so Flathub users aren't told to hand-download an AppImage. Non-Flatpak installs keep the existing beta.json/stable.json check.

Acceptance criteria

  • A Flatpak build installs and runs on a clean Flatpak host with working import/export, backup, and printing (via portals).
  • Flathub listing live under org.callerscompendium.compendiumApp; store-managed updates work.
  • Under Flatpak, the app does not show the AppImage-download update banner; direct-download installs are unchanged.

Refs #306, ADR-003.

Dominant language
Dart
Stars
0
Forks
0
Avg merge
2h 59m
Merged PRs (30d)
469

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ibanner56/CallersCompendium

All issues in ibanner56/CallersCompendium

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.