You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think you need to file a new feature request against this repo where you can add end-of-life and end-of-life properties to the json file. And I'm also not sure if the Flatpak builder action supports these parameters, so we might need an upstream feature request there as well
There may come a point where an application is no longer maintained. In order to inform users at update or install time that it will no longer get updates, create flathub.json with these contents:
{
"end-of-life": "This application is no longer maintained because..."
}
If the application has been renamed, you can additionally include end-of-life-rebase with the new ID. Recent flatpak versions will prompt user if they'd like to switch to the renamed app.
{
"end-of-life": "The application has been renamed to...",
"end-of-life-rebase": "the.new.appid"
}
Problem
Until recently, only apps with an RDNN were accepted according to the following scheme:
com.github.<user>.<repository>
.However, it should be possible to transfer an already published app to its own domain.
Proposal
It should be possible to specify the new RDNN with the entry
end-of-life-rebase
when a reason forend-of-life
is specified.Prior Art (Optional)
Flatpak
Posted by @danrabbit in #292 (comment)
Flathub
Source: https://github.com/flathub/flathub/wiki/App-Maintenance#end-of-life
The text was updated successfully, but these errors were encountered: