-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
EOL doesn't seem to propagate to Flatpak remote #484
Comments
This looks to be a problem in Flatpak's GitHub actions, PR to fix it submitted here: flatpak/flatpak-github-actions#157 Once that's fixed, I'll re-run the publish for your recent EoL'd apps and let you know. |
Thanks, @davidmhewitt! |
Still progressing this, found another issue with the GitHub actions and opened another PR: |
cassidyjames
added a commit
to cassidyjames/appcenter-reviews
that referenced
this issue
Aug 28, 2024
Includes @davidmhewitt's upstream fixes which should resolve elementary#484
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What Happened?
The only examples I see of EOL apps still show their pre-EOL updates in AppCenter, and don't warn when installing or updating from the CLI.
In all cases, the apps are showing the release information before their respective EOL update in the remote's AppStream data. For example, installing or updating LookBook doesn't recommend installing Icon Browser from the Flatpak CLI, and Clairvoyant is still showing its 2.0.0 release, meaning the 2.0.1 release never made it into the remote.
Steps to Reproduce
Expected Behavior
Marking an app as EOL in this repo should propagate that information to the Flatpak remote.
OS Version
7.x (Horus)
Software Version
Latest release (I have run all updates)
Log Output
No response
Hardware Info
No response
The text was updated successfully, but these errors were encountered: