While @wetab73 correctly denoted …
… this may also happen at any other time, when a new SailfishOS release is available, see:
To avoid any mishaps (by mistyping or mis-guessing the truly installed SailfishOS release) one may use (as described in the bug report) to bring the SailfishOS installation into a consistent state again:
devel-su
ssu re "$(grep -F VERSION_ID /etc/os-release | cut -s -f 2 -d "=")"
rm -f /var/cache/ssu/features.ini
ssu ur
Then either run post_sfos-upgrade
(if sfos-upgrade is installed),
or manually execute the “Final clean up steps” (specifically killing the store-client followed by removing its cached SailfishOS upgrade release version info),
plus a zypper ref
(if zypper is installed)
and a pkcon refresh
(i.e., always when doing this manually instead of using post_sfos-upgrade
).