The maintainers of the Foundation repository should care about the problem.
Not much that can be done about it.
Security fixes bump our version intentionally and I get an automatic notification when it happens.
Even if we prioritized our patches over security fixes, this update bumped the upstream version of the package, so the only alternative would be for us to bump the epoch of the package. That's not an option because it would make us eternally responsible for maintaining the package even after our patches are upstreamed.
Unfortunately, unless somebody has a better approach in mind, that means these things will happen sometimes