We could try using an rpmdeplint after using Packit to build an rpm.
If the rpm fails to build, well, we can check if it's due to a missing dependency. That could be caused by an incompatible version or the package is just missing.
To detect whether the package is low and can be bumped a semantic version, what should we do? It is possible that rpmdeplint will help here. It has a command, list-deps which may be able to list the dependencies as Fedora packages. Then we check the Fedora packages to see if any are legacy. If so, we report that and update when we get the chance.
If this idea doesn't work, we could try using Fedora release aliases in our check-fedora-versions script, much as Packit does. But that would not be a big gain.
We could try using an rpmdeplint after using Packit to build an rpm.
If the rpm fails to build, well, we can check if it's due to a missing dependency. That could be caused by an incompatible version or the package is just missing.
To detect whether the package is low and can be bumped a semantic version, what should we do? It is possible that rpmdeplint will help here. It has a command, list-deps which may be able to list the dependencies as Fedora packages. Then we check the Fedora packages to see if any are legacy. If so, we report that and update when we get the chance.
If this idea doesn't work, we could try using Fedora release aliases in our check-fedora-versions script, much as Packit does. But that would not be a big gain.