Unfortunately, I ran into an issue with cargo-semverchecks where it could no longer recognise some metadata that cargo outputs due to a future version being unrecognised.

Updating our packages gave me a newer version of the binary and allowed me to run the checks again.