Signing event: sign/migration

[github-actions]

Processing signing event sign/migration, please wait.

[github-actions]

Current signing event state

Event sign/migration (commit 7038bd2)

✅ root

Role root is verified and signed by 0/3 (3/3) signers (@dlorenc, @joshuagl, @bobcallaway).
Still missing signatures from @mnm678, @SantiagoTorres
Signers can sign these changes by running tuf-on-ci-sign sign/migration

✅ targets

Role targets is verified and signed by 3/3 signers (@dlorenc, @joshuagl, @bobcallaway).
Still missing signatures from @mnm678, @SantiagoTorres
Signers can sign these changes by running tuf-on-ci-sign sign/migration

✅ registry.npmjs.org

Role registry.npmjs.org is verified and signed by 1/1 signers (azurekms://npm-tuf-delegate.vault.azure.net/keys/npm-tuf-delegate-2024-08/e2772c1d01ca400da571096889f1660e).

Signing event is successful

Threshold of signatures has been reached: this signing event can be reviewed and merged.

[bobcallaway]

Current signing event state

Event sign/migration (commit 7038bd2)

✅ root

Role root is verified and signed by 0/3 (3/3) signers (@dlorenc, @joshuagl, @bobcallaway). Still missing signatures from @mnm678, @SantiagoTorres Signers can sign these changes by running tuf-on-ci-sign sign/migration

✅ targets

Role targets is verified and signed by 3/3 signers (@dlorenc, @joshuagl, @bobcallaway). Still missing signatures from @mnm678, @SantiagoTorres Signers can sign these changes by running tuf-on-ci-sign sign/migration

✅ registry.npmjs.org

Role registry.npmjs.org is verified and signed by 1/1 signers (azurekms://npm-tuf-delegate.vault.azure.net/keys/npm-tuf-delegate-2024-08/e2772c1d01ca400da571096889f1660e).

Signing event is successful

Threshold of signatures has been reached: this signing event can be reviewed and merged.

@jku @kommendorkapten note the count on root says 0/3 (3/3)

[jku]

This workflow that created the PR ran in dans fork: looks like we need to add some checks to the signing event workflow, it really shouldn't run in forks even if GH actions is enabled

@bobcallaway I just left a comment in the actual PR: it's a cosmetic migration issue that should not happen after this initial event

@dlorenc you can just close this one

[jku]

tuf-on-ci issue for this theupdateframework/tuf-on-ci#418