-
-
Notifications
You must be signed in to change notification settings - Fork 246
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
Request: publish release candidates on flathub-beta #278
Comments
Closed
Closed
heck, it would be nice to have the stable releases on flathub, as it stands it is missing a few releases past 0.17.0: https://github.com/flathub/im.fluffychat.Fluffychat/pulls |
This issue is stale because it has been open for 120 days with no activity. |
github-actions
bot
added
the
stale
The item is going to be closed soon because of inactivity
label
Jun 9, 2024
I am still interested, while this too is likely more or less blocked by flutter/flutter#41737. |
github-actions
bot
removed
the
stale
The item is going to be closed soon because of inactivity
label
Jun 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Currently FluffyChat's desktop release candidates are only published on Snap's
candidate
channel judging by https://gitlab.com/famedly/fluffychat/-/issues/767#linux-desktop-including-linux-phones and previous issues. I would like to install them from flathub-beta instead as I don't have Snap installed and I don't want to install it (due to everything being mounted and using space and permissions not handling external drives etc).I didn't find the documentation on how to do this, but Changes in Flathub land – Alexander Larsson has a Publish beta releases! section documenting it for end-users and pointing developers to beta branch of flathub/org.godotengine.Godot at GitHub on how it's setup.
The linked post says
So I think it matches the Snap candidate channel and could be a good match for FluffyChat rc testing.
The text was updated successfully, but these errors were encountered: