[Bug]: CachyOS April 2026 Release thinks it's the March 2026 Release
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- linux
- Domain
- release
Research direction
Start by reproducing the release-info display in CachyOS Hello using the April 2026 live ISO described in the issue. Trace where the displayed release name and date come from, then verify that both live and installed systems show “CachyOS April 2026 Release” with the appropriate April release date.
Written by the indexing model from the issue text.
Description
Kernel
7.0.2-1-cachyos
Desktop Environment / Window Manager
KDE Plasma
CPU
AMD Ryzen 7 9800X3D
GPU / Driver
AMD Radeon RX 9070 XT
Description
I installed CachyOS today (for the first time) using the April live ISO released today: https://cachyos.org/blog/2604-april-release/
CachyOS Hello, both in the live session and in the installed CachyOS, thinks it's the March release:
I believe the installer ISO was misconfigured in some way.
Steps to Reproduce
- Create a bootable USB drive from the April 2026 release of CachyOS (SHA256: 9a280d1e9732cfe50ab02db6a7e44ae0d9e6a10e6ea394f73192f7c14e263118 cachyos-desktop-linux-260426.iso)
- Boot into the live session, CachyOS Hello opens automatically
- Click on Release info:
(screenshot is from an installed CachyOS, button layout is similar in the live session)
Expected Behavior
It should say "CachyOS April 2026 Release" with an appropriate release date.
Actual Behavior
It says "CachyOS March 2026 Release" with a March 08 release date.
Logs / Error Messages
(skipped)
Additional Context
I am 99.999% sure that I used the right ISO. Putting the drive into the PC, it's named "COS_202604", so I don't think I accidentally wrote the March image.
- Dominant language
- No language data
- Stars
- 27
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CachyOS/distribution
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
CachyOS/distribution#521 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
CachyOS/distribution#522 · 2 comments · 2 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
CachyOS/distribution#518 · 3 reactions ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
CachyOS/distribution#504 · 1 comment · 1 reaction ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
CachyOS/distribution#460 · 1 reaction ·
All issues in CachyOS/distribution
Similar issues
-
Help-Wanted Needs-Triage Package-Request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/winget-pkgs#438680 ·
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
documentation pkg infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
epiverse-trace/epiparameter#511 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100