Add flatpakref file to artifacts #4388
Merged
Conversation
This file contains 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
ilya-zlobintsev
changed the title
ilya-zlobintsev
force-pushed
the
add-flatpakref
branch
from
8b3414c
to
0a9310c
Compare
pajlada
approved these changes
Feb 17, 2023
1 task
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.
Pull request checklist:
CHANGELOG.mdwas updated, if applicableDescription
There are now automated nightly Flatpak builds available on Flathub: https://github.com/flathub/com.chatterino.chatterino/tree/branch/nightly
Users generally get pointed to the Chatterino releases page to get nightly releases, so for the purposes of discoverability it would make sense for them to be able to get a Flatpak release there. However, as the Flatpak package is built separately outside of the usual Chatterino workflow process (it's built on Flathub's buildbot to be specific), there is no build artifact to automatically include in releases.
A solution for this is adding a static
.flatpakreffile to the artifacts. A.flatpakreffile is basically just a link to the Flatpak repo, application id and branch to install. What this means in practice is that users can simply download the ref file and install it, either via a GUI application manager or via the Flatpak CLI. They will still get centralized updates from Flathub, the ref file doesn't change between releases.I have tested that the release process works in my fork: release