### Proposal In order to get `semgrep` rule updates to customers as quickly as possible, we need to optimize the `semgrep` release process, which is the purpose of this epic. This will reduce the time spent by engineers creating the releases. Ideally, this process should also automatically create a new release post item which explains how many rule updates were created in total, as well as a break-down displaying the number of rule updates by language. In addition, we should also close related `sast-rule` issues when the rule is released in `semgrep`, as discussed [here](https://gitlab.com/gitlab-org/gitlab/-/issues/435113#note_1723604373). ### Implementation Plan 1. [ ] https://gitlab.com/gitlab-org/gitlab/-/issues/440373+s. 1. [ ] https://gitlab.com/gitlab-org/gitlab/-/issues/442491+s. 2. [ ] https://gitlab.com/gitlab-org/gitlab/-/issues/440523+s. 3. [ ] https://gitlab.com/gitlab-org/gitlab/-/issues/440377+s. 4. [ ] https://gitlab.com/gitlab-org/gitlab/-/issues/440518+s. /cc @twoodham @wayne