There are two main things for Microkit as part of the release:
- producing the SDKs (and signing them on macOS)
- updating projects (mainly the seL4 docs site and Microkit tutorial).
With the last release the SDKs are produced all by CI, I then download them and then do the Apple code-signing and then the GPG signing. I have a script to do it so it only takes a couple seconds but still, it's a manual process. The main issue is that the Apple code-signing requires an Apple account that is associated with me/my local macOS machine.
Solving this issue should:
- See if it's possible to move the Apple developer certificate to the Foundation's Mac Mini, and do that instead to make the process less dependent on me.
- Write a release checklist for all the things that cannot be automated.
There are two main things for Microkit as part of the release:
With the last release the SDKs are produced all by CI, I then download them and then do the Apple code-signing and then the GPG signing. I have a script to do it so it only takes a couple seconds but still, it's a manual process. The main issue is that the Apple code-signing requires an Apple account that is associated with me/my local macOS machine.
Solving this issue should: