Bug 2568647 - Appstream metadata still has F45 in "development" state
Summary: Appstream metadata still has F45 in "development" state
Keywords:
Status: MODIFIED
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-appstream-metadata
Version: 44
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Timothée Ravier
QA Contact:
URL: https://src.fedoraproject.org/rpms/fe...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-07 15:56 UTC by pg_tips
Modified: 2026-11-11 23:45 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description pg_tips 2026-11-07 15:56:41 UTC
"org.fedoraproject.fedora.metainfo.xml" contains:

<release version="45" type="development" date="2026-11-03" date_eol="2027-12-08">

The latest commit changed the release date, but didn't change "development" to "stable" status.

This means that F44 users in (for example) KDE Discover aren't made aware of the available update to F45.

Reproducible: Always

Steps to Reproduce:
Review the contents of "org.fedoraproject.fedora.metainfo.xml".
Actual Results:
F45 is shown in "development" status.

Expected Results:
F45 should be shown in "stable" status.

Comment 1 Fedora Update System 2026-11-11 17:56:47 UTC
FEDORA-2026-708d43b08c (fedora-appstream-metadata-20261002-2.fc44 and PackageKit-1.4.0-3.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-708d43b08c

Comment 2 Fedora Update System 2026-11-11 17:56:50 UTC
FEDORA-2026-a78aec7d06 (fedora-appstream-metadata-20261002-2.fc45 and PackageKit-1.4.0-3.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-a78aec7d06

Comment 3 Fedora Update System 2026-11-11 17:57:24 UTC
FEDORA-2026-edd1148da5 (fedora-appstream-metadata-20261002-2.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-edd1148da5


Note You need to log in before you can comment on or make changes to this bug.