Repository navigation
Publish the Flatpak from the project's own repository - #95
Merged
Merged
Conversation
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
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
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.
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 throughflatpak update, GNOME Software and Discover:packaging/flatpak/repo.sh(new) imports the.flatpakof the latest release into a new OSTree repository inside the built site, signs it, generates static deltas and writescorerules.flatpakrepoandio.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.flatpak remote-ls. It signs with theFLATPAK_GPG_PRIVATE_KEYsecret; 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)..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..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_KEYrepository secret must exist, or the site deploy on main fails:Testing
Locally with flatpak 1.14 and a test app: installing from the generated
.flatpakrefwith 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-keysinstalling and then updating from the repository, and the uninstall/install move from an unsigned bundle keeping the app's data. The site built withsite/build.pyplusrepo.shhas the.flatpakrefthe landing page links to. Both workflow files parse as YAML.Generated by Claude Code