flatpak: GNOME 47 runtime EOL

[dholbach]

Info: runtime org.gnome.Platform branch 47 is end-of-life, with reason:
The GNOME 47 runtime is no longer supported as of October 15, 2025. Please ask your application developer to migrate to a supported platform.
Info: applications using this runtime:
sh.loft.devpod

[skevetter]

I am using 48 to build the flatpak image https://github.com/skevetter/devpod/releases

https://github.com/skevetter/devpod/blob/2a8030b80d87c6738655779faf81ea6f7d18daee/.github/workflows/release.yml#L204-L209

[Robula]

I am using 48 to build the flatpak image https://github.com/skevetter/devpod/releases

https://github.com/skevetter/devpod/blob/2a8030b80d87c6738655779faf81ea6f7d18daee/.github/workflows/release.yml#L204-L209

I guess that the majority of users (including myself) use the version published to Flathub (https://flathub.org/en/apps/sh.loft.devpod) which is on v0.6.10.

[lthnh]

Info: runtime org.gnome.Platform branch 48 is end-of-life, with reason:
The GNOME 48 runtime is no longer supported as of March 24, 2026. Please ask your application developer to migrate to a supported platform.
Info: applications using this runtime:
sh.loft.devpod

48 also reached EOL in March.

Copy of: flathub/sh.loft.devpod#11

End-of-Life Notice

Hi,

Flathub has recently updated its End-of-Life (EOL) runtime policies and published specific EOL criteria for unmaintained applications.

This issue has been opened because this application currently meets one or more of the following Flathub EOL criteria.

If no response is received within the one-month notice period or there is no one to maintain or solve the issues, the application will be marked as EOL.

Thank you for your time and contributions.

EOL criteria

An application on Flathub can be marked as End-of-Life under the following conditions:

1. Upstream development has formally ceased: This is valid when upstream has formally announced EOL, archived their git repository or removed upstream sources etc.

2. Upstream development appears abandoned: This is valid when upstream has not formally announced EOL, but there has been no signs of activity or development for at least 2 years.

3. Flatpak is unmaintained or abandoned: This is valid when the Flatpak on Flathub has no maintainers at all or there has been no signs of maintenance activity for at least 2 years.

4. Persistently behind runtime updates: This is valid when the Flatpak on Flathub is persistently behind at least 3 runtime updates without no explanation being provided by the maintainers. If a proper explanation is provided and there is an interest to migrate to newer runtimes in the future, this crtieria will not be applicable.

5. Persistent critical functionality issues: This is valid when the Flatpak on Flathub has major functionality or usability issues that render it unusable or significantly impairs its basic functionality, or when it generates a large number of user complaints and there is no maintainer available to respond to or resolve these issues within a reasonable timeframe.

6. Failure to comply with Flathub ToS or inclusion policy: This is valid when the Flatpak on Flathub through an update or change after acceptance is found to be violating Flathub ToS or inclusion policy which was present at the time it was accepted.

Source: https://docs.flathub.org/docs/for-app-authors/maintenance#eol-policy

[github-actions]

This issue is stale because it has been open for 60 days with no activity.
It will be closed in 30 days on inactivity.