- grab each update and start a pr
- resolve the conflicts
- if conflicts cannot be resolved, indicate in the pr and wait for manual resolution
- launch headless chromium to update the webview hash
- generate the changelog section
- wait for merge
- generate the tag based on bundled vs code version and draft release
- add changelog section to the release notes
- wait for publish
- update the changelog with release date and and helm chart (probably no need for a pr, just push directly? or should it be another pr?)
So in the best case, the two manual steps would be to review and merge the update PR, and then to review and publish the draft release. In the worst case, manual conflict resolution is also required.
A notification for when the draft release is ready would also be handy (email? slack?)
So in the best case, the two manual steps would be to review and merge the update PR, and then to review and publish the draft release. In the worst case, manual conflict resolution is also required.
A notification for when the draft release is ready would also be handy (email? slack?)