Canceled Signing event

[sigstore-bot]

Processing signing event sign/root-v12, please wait.

[sigstore-bot]

Current signing event state

Event sign/root-v12 (commit c40ad4b)

❌ root

Role root is unsigned and not yet verified
Still missing signatures from @mnm678, @SantiagoTorres, @joshuagl, @dlorenc, @bobcallaway
Signers can sign these changes by running tuf-on-ci-sign sign/root-v12

[jku]

This signing event is still in progress, please do not sign yet: We will notify
here and in slack channel when this is ready for signing.

• First commit is a simple version bump: this should fail the signing event
  because we now have a check for the keyid issue (the reason for this signing
  event)
• Second commit includes the keyid correction

Note that the result looks absolutely awful in git diff, apologies for that

• The only change is the online key keyid changing and as a result that key moving
  a little in the sorted keys object. No key content changes here.
  • old: "7247f0dbad85b147e1863bade761243cc785dcb7aa410e7105dd3d2b61a36d2c"
  • new: "0c87432c3bf09fd99189fdc32fa5eaedf4e4a5fac7bab73fa04a2e0fc64af6f5"
• Unfortunately the way Git shows this is a disaster
• I have a small script that you can run on main branch (to see current situtation)
  and on the sign/root-v12 branch (to see situation in signing event) if that helps:
  https://gist.github.com/jku/4379186fd4ffb2a19798734c83deb695.

[jku]

oops we needed to upgrade tuf-on-ci first