# Mopidy 4.0 release candidates

**URL:** <https://discourse.mopidy.com/t/mopidy-4-0-release-candidates/6214>\
**Category:** Development\
**Created:** [April 15, 2026, 6:32pm UTC](https://discourse.mopidy.com/t/mopidy-4-0-release-candidates/6214 "2026-04-15T18:32:18Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![jodal](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/jodal/32/2564_2.png) [@jodal](https://discourse.mopidy.com/u/jodal)\
**Post date:** [April 15, 2026, 6:32pm UTC](https://discourse.mopidy.com/t/mopidy-4-0-release-candidates/6214/1 "2026-04-15T18:32:18Z")

</div>

Mopidy 4.0 is just around the corner. I’ve released 4.0.0rc1 and 4.0.0rc2 today, and will shortly (on the scale of hours to days) release 4.0.0 final if I don’t find any other issues.

In other words, it is a good time to give it a spin and try it out with your favorite extensions!

---

<div class="post-metadata">

**Author:** ![Matthias\_Meulien](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/matthias_meulien/32/2260_2.png) [@Matthias\_Meulien](https://discourse.mopidy.com/u/Matthias_Meulien)\
**Post date:** [April 18, 2026, 7:04pm UTC](https://discourse.mopidy.com/t/mopidy-4-0-release-candidates/6214/2 "2026-04-18T19:04:45Z")

</div>

Are there DEB packages available or should one use the sources to test?

---

<div class="post-metadata">

**Author:** ![jodal](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/jodal/32/2564_2.png) [@jodal](https://discourse.mopidy.com/u/jodal)\
**Post date:** [April 18, 2026, 8:49pm UTC](https://discourse.mopidy.com/t/mopidy-4-0-release-candidates/6214/3 "2026-04-18T20:49:50Z")

</div>

There’s only the PyPI release or Git.

I’m kind of hoping that other Debian Developers will pick up most of the maintenance of the Debian packages going forward. Since moving them from a dedicated Mopidy team into the Debian Python Team, that has so far worked out great, with lots of modernizations and improvements done to the packages.

By not mentally connecting making a Mopidy release to having to update Debian packages too, I’m hoping to become better at releasing improvements continuously, at the cost of letting the Debian packages only catch up eventually.

---

<div class="post-metadata">

**Author:** ![Matthias\_Meulien](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/matthias_meulien/32/2260_2.png) [@Matthias\_Meulien](https://discourse.mopidy.com/u/Matthias_Meulien)\
**Post date:** [April 19, 2026, 8:16am UTC](https://discourse.mopidy.com/t/mopidy-4-0-release-candidates/6214/4 "2026-04-19T08:16:23Z")

</div>

Ok, thank you for your quick answer and all the great work!

I’ll switch to the PyPI packages and test v4.0.0rc2

Should not release candidate have their documentation visible on ReadTheDocs? What do you recommend to read install instructions for a release candidate?

EDIT: Reading from sources is quite comfortable.

 ![image](https://canada1.discourse-cdn.com/flex036/uploads/mopidy/original/2X/2/294008a38e1d80cdb0a9d568d99ffd9e4cac6a46.png)

---

<div class="post-metadata">

**Author:** ![jodal](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/jodal/32/2564_2.png) [@jodal](https://discourse.mopidy.com/u/jodal)\
**Post date:** [April 19, 2026, 10:44am UTC](https://discourse.mopidy.com/t/mopidy-4-0-release-candidates/6214/5 "2026-04-19T10:44:50Z")

</div>

On Read the Docs `stable` is the latest stable release, while `latest` tracks the `main` branch, so everything that has been merged into `main` is visible in the `latest` docs.

You can find the combined changelog for all the changes in 4.0 in  
[the `latest` changelog](https://docs.mopidy.com/latest/changelog/).

For a bit more details about what is in each alpha or release candidate, [GitHub Releases](https://github.com/mopidy/mopidy/releases) has a bit more details.

---

<div class="post-metadata">

**Author:** ![Matthias\_Meulien](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/matthias_meulien/32/2260_2.png) [@Matthias\_Meulien](https://discourse.mopidy.com/u/Matthias_Meulien)\
**Post date:** [April 19, 2026, 6:47pm UTC](https://discourse.mopidy.com/t/mopidy-4-0-release-candidates/6214/6 "2026-04-19T18:47:44Z")

</div>

It was a laborious day: I first had to upgrade from Bookworm to Trixie, fight `pipewire`, and finally switched from system user to a user running Mopidy in a virtual environment.

Mopidy-Local (v4.0.0a6) work has expected.

All other extensions I use are broken ( **EDIT: most is fixed!** ):

- Mopidy-Listenbrainz and Mopidy-Somafm fail to load due to missing `pkg_ressources` package;
- Mopidy-InternetArchive, Mopidy-Podcast and Mopidy-SomaFM don’t populate the library, no error in Mopidy output

The playlists created with the m3u extension don’t load anymore.

I’ll have a look on the work to be done to migrate Mopidy-Listenbrainz.

EDIT ~~: ⚠ Browsing directories with Argos doesn’t work anymore: Directories containing tracks appear empty, as if the returned tracks weren’t considered valid by Argos (but no particular log). Same observation with Somafm library: appears empty.~~ See [Support for Mopidy 4.0 · Issue #204 · orontee/argos · GitHub](https://github.com/orontee/argos/issues/204) where a fix is provided.

---

<div class="post-metadata">

**Author:** ![Matthias\_Meulien](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/matthias_meulien/32/2260_2.png) [@Matthias\_Meulien](https://discourse.mopidy.com/u/Matthias_Meulien)\
**Post date:** [April 19, 2026, 8:30pm UTC](https://discourse.mopidy.com/t/mopidy-4-0-release-candidates/6214/7 "2026-04-19T20:30:03Z")

</div>

A fix for Mopidy-Listenbrainz is available from [GitHub - orontee/mopidy-listenbrainz at support-4.0.0 · GitHub](https://github.com/orontee/mopidy-listenbrainz/tree/support-4.0.0) ; I’ll submit a PR to upstream once 4.0.0 will be released.

Same for Mopidy-Somafm: [GitHub - orontee/mopidy-somafm at support-v4.0.0 · GitHub](https://github.com/orontee/mopidy-somafm/tree/support-v4.0.0) . But still not validated.

---

<div class="post-metadata">

**Author:** ![tkem](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/tkem/32/22_2.png) [@tkem](https://discourse.mopidy.com/u/tkem)\
**Post date:** [April 20, 2026, 3:24pm UTC](https://discourse.mopidy.com/t/mopidy-4-0-release-candidates/6214/8 "2026-04-20T15:24:37Z")

</div>

Mopidy v4.0.0a6 is an older alpha version. The current release candidate is 4.0.0rc2: [History](https://pypi.org/project/mopidy/#history)

The latest releases of Mopidy-InternetArchive and Mopidy-Podcast should work fine with RC2.