Improve release workflow
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- macos
- Domain
- ci-cd, documentation, release
Research direction
Start by reviewing the CI release workflow and the existing script used for Apple and GPG signing. Check whether the Apple developer certificate can be moved to the Foundation's Mac Mini, then document the remaining manual release steps in a checklist; done means the process is less dependent on one person and the checklist covers non-automated work.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- Rust
- Stars
- 201
- Forks
- 80
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 7
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from seL4/microkit
-
Difficulty 2/5 Half a day Newbie friendliness 72/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100