If you had release restrictions in your database prior to the updates tonight, you’ll want to make sure they are still there, there was an issue with the migration and it replaced the release restrictions with a single ? instead of their proper values.
It would have affected anyone that got the update within the first couple hours of the release. You can [restore] (https://github.com/Sonarr/Sonarr/wiki/Backup-and-Restore) a backup from before the update then start Sonarr up again which will update it to the latest version again, copying everything over, so you don’t have to reenter them by hand & memory.
Thanks for testing these changes before everyone else!
The issue affected: 2.0.0.2266 (released at 10:54pm PST, Nov 18th) & 2.0.0.2267 and was fixed in 2.0.0.2268 (released at 12:05am PST, Nov 19th). PST is GMT-8.