-
v0.4.1 - House Party (01.03.2026) Pre-Release
released this
2026-03-31 17:04:40 +00:00 | 0 commits to main since this releaseThis release is dedicated to the front door. The home experience now feels far more alive, with listening-history-backed sections, stronger recommendations, and generated "For You" playlists. Around that, we also tightened up metadata enrichment, search, and playback handoff so the whole app feels sharper than v0.4.0.
Release stats: 54 commits, +11,264 / -1,617
New Features
- Added MusicBrainz metadata enrichment and Cover Art Archive support for better metadata without relying only on Spotify (#118) (#126)
- Added account-level cross-device playback controls and smoother playback session handoff between devices (#129)
Changes
- Reworked the homepage into a more dynamic discovery surface with listening-history-backed sections and generated "For You" playlists (#47) (#111) (#124)
- Search can now match genres more naturally and keeps a more useful history-driven flow (#58) (#134) (#133)
Improvements
- Reduced initial frontend bundle cost by lazy-loading app, admin, and debug routes (#108) (#132)
- Introduced React Compiler tooling and related frontend cleanup/performance work (#112)
- Improved homepage recommendation freshness, cache handling, and general playback behavior across the redesigned home surfaces (#124)
- Cleaned out the remaining
State<T>wrapper usage in this release slice and normalized genre matching for queries like "lo fi" (#58) (#73) (#133)
Stability
- Fixed context menu flashing and nested context menu rendering issues (#127) (#130)
- Fixed
/preferencesnot being fetched correctly after login and other stale preference refresh issues (#121) (#132) - Fixed playback state regressions around browser/media controls, search queuing behavior, and player bar population in certain playback contexts (#96) (#113) (#114) (#132)
- Fixed several search page caching and loading edge cases (#56) (#120)
- Fixed playlist artwork refresh issues and additional playback/session ownership edge cases (#136) (#137)
- Fixed a first-launch database migration failure on fresh setups when MusicBrainz columns already existed in the base schema
Downloads