Release 2026.4.1rc2 β MOTD opt-in & upgrade checker fix π§ #48
Closed
b0bbywan
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Quick follow-up to rc1: 2026.4.1rc2 is out, mostly polishing the update-check mechanism introduced last week.
What changed
install_motd(false by default). Existing installs are no longer affected unless you explicitly enable it.git describe(TAG-N-gSHA) instead ofdev-<sha>, so semantic comparison works correctly. A commit made after rc1 is no longer flagged as needing an "upgrade" back to rc1. π€¦~/.cache/odio/upgrades.jsonis regenerated at the end of the install instead of waiting for the next daily timer fire, so the motd reflects reality on first login.Full changelog: 2026.4.1rc1...2026.4.1rc2
Still looking for input
The UX threads from the rc1 announce are still open β if you've been playing with webradios or have opinions on discovery / notifications, jump in:
And on the myMPD side β the customization prereq is still up for grabs if anyone wants to tackle it. π
All reactions