Could their be any possible breaking changes?

[Pauldic]

I got this while upgrading to Django 3.1.1
django-reversion-compare 0.12.2 requires django<3.1,>=2.2, but you'll have django 3.1.1 which is incompatible.

[jedie]

We didn't restrict django version, see:

django-reversion-compare/pyproject.toml

Lines 40 to 43 in 9395300

	[tool.poetry.dependencies]
	python = ">=3.7,<4.0.0"
	django-reversion = "*"
	diff-match-patch = "*"

And django-reversion doesn't so this, too. See:

https://github.com/etianen/django-reversion/blob/161dfeeac5b56a580e838eb0e35a9d17fe4fb024/setup.py#L37-L39

So i don't know where "django<3.1" comes from.
If you startup the test project, than Django 3.1.6 is currently used and it seems to work fine.

The tests runs against these Django versions:

django-reversion-compare/pyproject.toml

Lines 141 to 143 in 9395300

	django2.2: django~=2.2.0
	django3.0: django~=3.0.0
	django3.1: django~=3.1.0

So i have no idea what's happening in your setup.

[sjdemartini]

This appears to have been fixed with this PR #134 and released in v0.13.0