What breaks between the version you run and the version you want.
You left Paperless on 3.0.5 for eight months. Now you want 3.4.1. Thirteen releases sit in between, and somewhere in there is the one that needs a manual migration. This site exists to stop you reading thirteen changelogs to find it.
Start with a tool
What this does and does not claim
Change extraction has not run yet. Right now this site publishes only what can be checked: which releases sit between two versions, when each came out, a link to every changelog, and whether the version you are on is still supported. That already saves the hunting. It does not tell you a span is safe — and a page that implied it did, without having looked, would be worse than no page at all.
Why not just read the changelog
Because the question is never "what changed in 3.4.1". It is "what changed across the eleven releases I skipped", and nothing answers that. Release trackers notify you per release. Dependency bots paste whole changelogs into a pull request. Both leave you to do the reading.
And some projects do not put their breaking changes in the release notes at all. Traefik's 3.0.0 notes are one line telling you to go and read a migration guide. Knowing that is itself the useful answer, so this site says it instead of pretending the notes were enough.
39 of 46 tools have collected history ·12,195 releases ·open source