Update mockito
Description
Environment
is related to
Activity
Ian YoungMarch 6, 2024 at 2:28 PM
No change here: current version 5.11.0 is still being signed by the same key. Its expiry hasn’t been updated as far as I can tell, and it’s still not referenced from the repository (there’s a “yeah, that’s the right one” in the issue comment thread, but it’s a little vague).
This repository’s attached releases are just source code, so I can’t compare the Maven Central version of the artifact with anything to do a local signature, either.
I will poke them again.
Ian YoungAugust 14, 2023 at 3:23 PM
Poked the GitHub issue again.
Interestingly the version of the key I was able to pick up today from the Ubuntu server expired shortly after I posted that issue:
It’s still being used to sign releases, though. That could either be an error that somehow no-one else has noticed, or it may be that he has updated the expiry (that’s a thing you can do, expiry of keys and subkeys is determined by a self-signature).
We’re using quite a moderately old version of Mockito in our tests (3.9.0, from 2021-04). It would be nice to catch up, however their more recent versions (even more recent 3.x ones) are signed with a new key.
I have opened an issue on the mockito repository requesting publication of their signing keys.