22 Release Branches
Donald Webster edited this page 4 years ago

Selecting the right branch

If you're using Sonarr v2, you can choose between master and develop. But if you're using Sonarr v3, your only option is phantom-develop. If you have a very old v3 installation, it might still be set to phantom which isn't used anymore. You cannot use a v3 branch w/ v2 and you cannot use a v2 branch w/ v3.

Sonarr v2

  • master: Is stable, it has been tested by users on develop branch and it's not known to have any major issues.
  • develop: This was the bleeding edge, when development was being done on v2. It is released as soon as code is committed and passes all automated tests. This build may have not been used by us or other users yet. There is no guarantee that it will even run in some cases. Use this branch only if you know what you are doing and are willing to get your hands dirty to recover a failed update.

Sonarr v3

  • phantom-develop: Currently this is the only branch and it is similar to v2's develop. It gets updated often, occasionally breaks and is usually fixed quickly w/ the help of users running it and providing useful bug reports. It is released as soon as code is committed and passes all automated tests.

How to change your branch

For Built-In Updater

  1. Go to Settings and then the General tab and show advanced settings (use the toggle by the save button).

  2. Under the Development section change the branch name to you chosen option, master, develop or phantom-develop.

  3. Save

This will not install the bits from that branch immediately, it will happen during the next update.

For Ubuntu/Debian aptitude/apt-get

You probably should update your sources.list file too if you installed using aptitude/apt-get:

deb http://apt.sonarr.tv/ develop main

Installing a newer version

  1. Go to System and then the Updates tab

  2. Newer versions that are not yet installed will have an update button next to them, clicking that button will install the update.

Can I switch from develop back to master?

We don't recommend manually switching back to master, since other branches are commonly running newer code which might not be compatible with the older code in master. We have plans to mitigate this in the future.