github ProphetSe7en/clonarr v2.2.5

latest releases: v3.2.1, v3.2.0, v3.1.0...
one month ago

Two bug fixes and a couple of UX improvements around cleaning up after testing.

New — Restore deleted profiles

When you delete a profile in Radarr or Sonarr, Clonarr no longer drops its saved settings for that profile. The sync rule shows up as orphaned in the History tab (amber row, "orphaned" badge, auto-sync turned off). Two actions:

  • Restore — recreates the profile in Radarr/Sonarr with all the same custom formats, scores, quality settings and overrides you had. If a profile with that name already exists, you get prompted to use a different name.
  • Remove — permanently delete the saved settings.

The orphaned row goes away by itself once Restore succeeds.

Fixed — "Remove sync entry" looked broken

If you'd synced the same profile multiple times, clicking the red X to remove its sync history only removed one of the saved entries. The row reappeared, looking like the delete didn't work. Now one click clears the whole row.

Fixed — toast spam when bulk-deleting profiles in Arr

If you deleted 20+ profiles in Radarr/Sonarr at once, Clonarr would stack 20+ yellow toasts that needed their own scrollbar. Now you get one toast per Arr instance with the first few names and a "+N more" count.

Improved — Unused Custom Formats scan

The scan used to silently hide custom formats that Radarr/Sonarr can include in filenames (the "Use in renaming" flag — typically streaming-service tags like AMZN, NF, language tags, version tags). That made the scan less useful exactly when you needed it — after deleting profiles and wanting to clean up the leftover CFs.

Now the scan shows everything, with three tabs in the result:

  • All unmanaged — every CF not used by any sync rule
  • Rename-tagged only — the subset Radarr/Sonarr can include in filenames (yellow badge)
  • Managed by Clonarr — read-only list of CFs your sync rules use, with the Arr profile each one belongs to

If your file-naming format includes the {Custom Formats} token, a blue info box explains what deleting rename-tagged CFs does to future filenames (existing files on disk are not affected; re-syncing a profile from TRaSH or Profile Builder brings them back). If the token isn't in your format, a green box notes those CFs are safe to delete.

When rename-tagged CFs are present, you get two delete buttons: Delete safe only (keeps the rename-tagged ones) or Delete all (subtler outline). Both ask for confirmation before running.

Full changelog

Don't miss a new clonarr release

NewReleases is sending notifications on new releases.