Both.
This is a bug that we cannot fix the correct way yet*, because the package that owns /etc/os-release (the baselayout package) cannot be reliably upgraded without potentially bricking installed systems.
We are in the process of preparing a switch to a newer package repository version (v1 -> v2). This process is called the "epoch bump" in our internal discussions. Completing this process will enable us to update the baselayout package again.
We understand that it must be very confusing for some users to not see the updated version 4.6 in /etc/os-release.
However, in reality, the only thing that is different between a fully updated Solus 4.5 (or 4.4, or 4.3, or 4.2, or 4.1, or (...)) system and a fully updated Solus 4.6 system, is currently the contents of the /etc/os-release file.
In other words:
Every single other package on a fully updated 4.5 system is identical to the packages on a fully updated 4.6 system.
Do you understand now?
*: We are looking at workarounds that will silently update the /etc/os-release file on older Solus installs, just so we don't have to spend oodles of time engaging with confused users whose expectations don't match reality.
EDIT: As of the sync on 2024-10-29, the above issue should be fixed.
