Sonarr v3: fix block on legacy (v2) upgrades #5554
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This corrects a bug in Sonarr v3 (#5515) where an upgrade from legacy Sonarr v2 was not blocked (in DSM6). This results in the distribution containing two sets of binaries and AppData directories which can break the deployment. This bug also creates issues with upgrades to Sonarr v4 (#5524) since the correct installed version cannot be determined.
Once published, it is recommended that Sonarr v3 (Version 20221216-21) be unpublished to avoid future use.
Checklist
all-supported
completed successfullyType of change