Doing a security release involves quite a bit of manual work from the release coordinator. For an initial cut, let's see if we can automate assembling the internal commits into a branch, and exporting the changes from that branch on release day.
Comment From: gopherbot
Change https://go.dev/cl/486515 mentions this issue: internal/task: create a basic Git wrapper, use it for the fake Gerrit
Comment From: gopherbot
Change https://go.dev/cl/486575 mentions this issue: cmd/relui,internal/task: add workflow for re-syncing go-private master
Comment From: cagedmantis
We should consider automating the process where we replace the placeholder text for the GitHub issues with the actual security notice automatically.
Comment From: gopherbot
Change https://go.dev/cl/515075 mentions this issue: internal/task: create a basic Git wrapper, use it for the fake Gerrit
Comment From: gopherbot
Change https://go.dev/cl/612116 mentions this issue: internal/task: add workflow to build internal security release branches
Comment From: gopherbot
Change https://go.dev/cl/685516 mentions this issue: internal/task: build internal security branch for next RC too