{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreieudaj25to2neyygqm3lf7bpzpflq7kfchcd2jbhdduf34hmfieey",
    "uri": "at://did:plc:yrn4rbgwenb6lfhhzjegbtnc/app.bsky.feed.post/3mfh7jimpcob2"
  },
  "path": "/t/eol-runtime-working-team/6627#post_18",
  "publishedAt": "2026-02-20T03:08:05.000Z",
  "site": "https://discourse.flathub.org",
  "tags": [
    "docs.flathub.org – 24 Oct 25",
    "Enhanced License Compliance Tools for Flathub | Flathub Documentation",
    "@cassidyjames"
  ],
  "textContent": "> **End-of-life runtime transition:** To focus our resources on maintaining high-quality, up-to-date runtimes, we’ll be completing the removal of several end-of-life runtimes in **January 2026**. Apps using runtimes older than freedesktop-sdk 22.08, GNOME 45, KDE 5.15-22.08, or KDE 6.6 will be marked as EOL shortly.\n\ndocs.flathub.org – 24 Oct 25\n\n### Enhanced License Compliance Tools for Flathub | Flathub Documentation\n\ntl;dr: Flathub has improved tooling to make license compliance easier for developers. Distros should rebuild OS images with updated runtimes from Flathub; app developers should ensure they're using up-to-date runtimes and verify that licenses and...\n\n@cassidyjames I’ll mark 32 apps that are already informed about the situation as EOL at the end of February.\n\nThere are 60 games that use EOL runtimes, which I believe contain low risk, and they are on the exception list (meaning I don’t take any action against them).\n\nThere are also 73 apps that I will try to update to a supported runtime version or warn about EOL. My goal is to start on March 1 and inform the developer about EOL, giving them one month of grace period.\n\nSince I’m just a volunteer, none of them are official dates or actions.",
  "title": "EOL Runtime working team?"
}