Here you go: *broken* Release: 2.0.4.13 (canary) 2019-01-29
It was this version specifically that had an issue. It’s one of the risks of using the Canary releases. Sticking with the Beta releases is the general recommendation as their stability is established before release.
Fortunately you don’t have to look at every single canary release notes (unless you really want to) as each beta release has a nice high-level summary of changes.
Here are the beta releases since 2.0.4.5:
2.0.5.1: Release v2.0.5.1-2.0.5.1_beta_2020-01-18 · duplicati/duplicati · GitHub
2.0.6.1: Release v2.0.6.1-2.0.6.1_beta_2021-05-03 · duplicati/duplicati · GitHub
2.0.6.3: Release v2.0.6.3-2.0.6.3_beta_2021-06-17 · duplicati/duplicati · GitHub
That’s a valid concern… if it ain’t broke, why fix it? You could mitigate much of the risk by backing up your sqlite databases before you upgrade.
Personally I keep up with the latest beta release, installing them out over the course of a week or two across all my machines.