Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add flatpakref file to artifacts #4388

Merged
merged 1 commit into from
Feb 17, 2023

Conversation

ilya-zlobintsev
Copy link
Contributor

@ilya-zlobintsev ilya-zlobintsev commented Feb 17, 2023

Pull request checklist:

  • CHANGELOG.md was updated, if applicable

Description

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 .flatpakref file to the artifacts. A .flatpakref file 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

@ilya-zlobintsev ilya-zlobintsev marked this pull request as draft February 17, 2023 16:22
@ilya-zlobintsev ilya-zlobintsev changed the title add flatpakref to artifacts Add flatpakref file to artifacts Feb 17, 2023
@pajlada pajlada enabled auto-merge (squash) February 17, 2023 19:45
@pajlada pajlada merged commit da97079 into Chatterino:master Feb 17, 2023
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