4.0.0

Enabled Renamarr jobs now run immediately at startup and repeat every hour by default.

Each Sonarr or Radarr instance supports a configurable schedule:

renamarr:
  enabled: true
  schedule:
    enabled: true
    interval: # every 6 hours
      days: 0
      hours: 6
      minutes: 0

To run Renamarr once—such as when using cron or another external scheduler—explicitly disable scheduling for every applicable service:

renamarr:
  enabled: true
  schedule:
    enabled: false

• renamarr.hourly_job option remains available, but is now deprecated
  • A warning message is logged; please update to the new renamarr.schedule.enabled configuration as it will be removed in a later release
• renamarr.schedule.enabled always takes precedence over renamarr.hourly_job
• Schedule intervals may combine days, hours, and minutes, with a maximum interval of 30 days.

Thanks to @Paknsoks for contributing configurable scheduling in #295 (#295).

Other changes

• Added native Docker health reporting backed by an application heartbeat. #313
• Updated the provided Compose configurations to use a read-only root filesystem with a writable /tmp mount for health reporting.
• Fixed bug relating to Sonarr folder rename response parsing. #319
• Updated dependencies and CI tooling.

Full Changelog: 3.0.0...4.0.0