SteamDB Logs February 2026 RetroArch Patch Despite Official 2025 Release

SteamDB’s RetroArch patch record shows a recorded update entry with last-record activity on 2026-02-28 (UTC), creating a clear date mismatch with RetroArch’s main reference release history. The official v1.22.2 tag on the RetroArch GitHub is dated Nov 19, 2025, while the Steam-side entry logs activity more than three months later.

The SteamDB entry is logged as a patch record specific to RetroArch and lists 2026-02-28 as the last recorded activity in UTC. That SteamDB timestamp stands apart from the upstream repository timeline where the v1.22.2 tag carries the late 2025 date. The two concrete timestamps - Nov 19, 2025 on the GitHub tag and Feb 28, 2026 on the SteamDB log - frame the discrepancy precisely.

RetroArch’s v1.22.2 tag dated Nov 19, 2025 remains the main reference release in the official Git history. The presence of a SteamDB patch record on Feb 28, 2026 indicates that something changed on the Steam-distributed side after the upstream v1.22.2 tag. That divergence between the GitHub tag date and the SteamDB last activity date is the factual center of this report.

The practical impact of a SteamDB-recorded update on 2026-02-28 while the upstream tag stays at Nov 19, 2025 is visibility for anyone tracking version parity. Users comparing the Steam-distributed RetroArch build to the GitHub v1.22.2 tag will see the SteamDB activity timestamp and may reasonably expect differences in packaging, metadata, or build artifacts tied to the Feb 28, 2026 entry. The two dates provide a specific checklist for verification: the v1.22.2 tag dated Nov 19, 2025 and the SteamDB entry dated Feb 28, 2026.

Expect further clarifying entries if SteamDB records additional activity after Feb 28, 2026 or if RetroArch publishes a later GitHub tag that postdates Nov 19, 2025. Verify the SteamDB RetroArch patch record showing last-record activity on 2026-02-28 (UTC) against the v1.22.2 tag dated Nov 19, 2025 to determine whether the Steam-distributed build reflects a packaging change, an updated binary, or only metadata adjustments.