Skip to content

Publish the Flatpak from the project's own repository - #95

Merged
brahm merged 1 commit into
mainfrom
claude/project-thread-7uusp1
Oct 25, 2026
Merged

brahm merged 1 commit into
mainfrom
claude/project-thread-7uusp1

Conversation

@brahm

@brahm brahm commented Oct 25, 2026

Copy link
Copy Markdown
Owner

Requested by Brahm · project thread

Summary

The website now serves a signed Flatpak repository next to the landing page, at https://brahm.github.io/corerules/flatpak/, instead of Flathub (decision P16). Installing from it gets every new version through flatpak update, GNOME Software and Discover:

flatpak install --user https://brahm.github.io/corerules/io.github.brahm.CoreRules.flatpakref
  • packaging/flatpak/repo.sh (new) imports the .flatpak of the latest release into a new OSTree repository inside the built site, signs it, generates static deltas and writes corerules.flatpakrepo and io.github.brahm.CoreRules.flatpakref (with Flathub as the runtime repository). It keeps no state: republishing the same release keeps the same commit, so installed apps see no update.
  • Landing page workflow builds the repository with the site, from the latest release, and checks it with flatpak remote-ls. It signs with the FLATPAK_GPG_PRIVATE_KEY secret; a pull request without the secret uses a throwaway key to test the rest, and main is never published without it. It can now also be started by hand (workflow_dispatch).
  • Packages workflow signs the Flatpak build with the same key and writes the repository's address and key into the .flatpak, so a release file installs and then updates from the repository. After a final release, it starts the Landing page workflow (releases made with the workflow token start no workflows by themselves), so the repository follows each release without anyone touching it.
  • README, landing page, release notes: install commands for the repository, how to move from the 1.0.0 .flatpak (uninstall, then install from the .flatpakref; data stays), and the maintainer notes on the secret. Roadmap and decision P16 updated.

Before merging

The FLATPAK_GPG_PRIVATE_KEY repository secret must exist, or the site deploy on main fails:

gpg --batch --passphrase '' --quick-gen-key 'Core Rules Flatpak' rsa4096 sign never
gpg --armor --export-secret-keys 'Core Rules Flatpak'   # the secret's value

Testing

Locally with flatpak 1.14 and a test app: installing from the generated .flatpakref with GPG verification on, updating after the repository was rebuilt from a newer bundle, "Nothing to do" after republishing the same bundle, a repository signed with another key refused, a bundle built with --repo-url/--gpg-keys installing and then updating from the repository, and the uninstall/install move from an unsigned bundle keeping the app's data. The site built with site/build.py plus repo.sh has the .flatpakref the landing page links to. Both workflow files parse as YAML.


Generated by Claude Code

The website now serves a signed Flatpak repository next to the landing
page, at https://brahm.github.io/corerules/flatpak/, so the app installs
with a .flatpakref and gets every new version through flatpak update,
GNOME Software and Discover.

- packaging/flatpak/repo.sh imports the .flatpak of the latest release
  into a new OSTree repository, signs it, generates static deltas and
  writes corerules.flatpakrepo and io.github.brahm.CoreRules.flatpakref.
  Republishing the same release keeps the commit, so installed apps see
  no update.
- The Landing page workflow builds the repository with the site, signed
  with the FLATPAK_GPG_PRIVATE_KEY secret, and checks it with flatpak
  remote-ls. A pull request without the secret signs with a throwaway
  key; main is never published without it.
- The Packages workflow signs the Flatpak build, writes the repository's
  address and key into the .flatpak, and starts the Landing page workflow
  after each final release, so the repository follows the releases.
- README, landing page and release notes give the repository's install
  commands and how to move from the 1.0.0 .flatpak; decision P16.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011s7PaQ7tbmcs25nc2jcUJz
@brahm brahm self-assigned this Oct 25, 2026
@brahm
brahm merged commit 67fc5e6 into main Oct 25, 2026
27 checks passed
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