-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Signing event: sign/migration-take-two #1348
Conversation
Current signing event stateEvent sign/migration-take-two (commit 9050b38) Signing event is successfulThreshold of signatures has been reached: this signing event can be reviewed and merged. |
This comment was marked as outdated.
This comment was marked as outdated.
9050b38
to
2b4bfaa
Compare
Current signing event stateEvent sign/migration-take-two (commit 2b4bfaa) ✅ rootRole ✅ targetsRole ✅ registry.npmjs.orgRole Signing event is successfulThreshold of signatures has been reached: this signing event can be reviewed and merged. |
We merged sign/migration but had to revert on. After a tuf-on-ci release we want to * "merge the same changes again" (aka revert the revert) * Include the tuf-on-ci upgrade This reverts the original revert commit f9b651b. Signed-off-by: Jussi Kukkonen <[email protected]>
This contains a workaround that should make online-sign succeed (even though the online-url in the metadata is not quite correct) Signed-off-by: Jussi Kukkonen <[email protected]>
2b4bfaa
to
29bed78
Compare
Current signing event stateEvent sign/migration-take-two (commit 29bed78) ✅ rootRole ✅ targetsRole ✅ registry.npmjs.orgRole Signing event is successfulThreshold of signatures has been reached: this signing event can be reviewed and merged. |
This is a second attempt at #1320:
The first item there should be a 1:1 match to sign/migration changes -- annoyingly it's not very easy to review a "reverted revert". |
Processing signing event sign/migration-take-two, please wait.