A better option could be a theoretical [phantom-dependencies] table.
I stand behind what I said earlier that if your library's correctness relies on a bug fix in your dependency, you should upgrade your dependency requirement. Being "minimal-versions correct" isn't just about working under -Zminimal-versions, it's also about getting the appropriate versions to people who cargo add your library but already have older versions of your dependencies in their lockfile.
Especially if you're a "maximal-versions maximalist," you should be upgrading your dependency requirements for each release to be the most recent at the time of release. Or at the very least, to whatever the versions are in your lockfile. Those are the versions you tested against, so don't lie and say you work with earlier versions.