<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=324194) </details> <!--IssueSummary end--> The following discussion from !54941 should be addressed: - [ ] @nolith started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/54941#note_524473329): (+1 comment) > @jacobvosmaer-gitlab do we have a follow-up issue to cleanup all the packaging and releasing code related to `GITLAB_WORKHORSE_VERSION`? <!-- start-discoto-summary --> ## Auto-Summary :robot: <details> <summary>Discoto Usage</summary> --- > **Points** > > Discussion points are declared by headings, list items, and single > lines that start with the text (case-insensitive) `point:`. For > example, the following are all valid points: > > * `#### POINT: This is a point` > * `* point: This is a point` > * `+ Point: This is a point` > * `- pOINT: This is a point` > * `point: This is a **point**` > > Note that any markdown used in the point text will also be propagated > into the topic summaries. > > **Topics** > > Topics can be stand-alone and contained within an issuable (epic, > issue, MR), or can be inline. > > Inline topics are defined by creating a new thread (discussion) > where the first line of the first comment is a heading that starts > with (case-insensitive) `topic:`. For example, the following are all > valid topics: > > * `# Topic: Inline discussion topic 1` > * `## TOPIC: **{+A Green, bolded topic+}**` > * `### tOpIc: Another topic` > > **Quick Actions** > > | Action | Description | > |-------------------------------|---------------------------------------------------------| > | `/discuss sub-topic TITLE` | Create an issue for a sub-topic. Does not work in epics | > | `/discuss link ISSUABLE-LINK` | Link an issuable as a child of this discussion | > --- </details> Last updated by [this job](https://gitlab.com/gitlab-org/secure/pocs/discoto-runner/-/jobs/1101556911) * **TOPIC** release-tools https://gitlab.com/gitlab-org/gitlab/-/issues/324194#note_527282293 * **TOPIC** GITLAB_WORKHORSE_VERSION being a symlink to VERSION might break the release process https://gitlab.com/gitlab-com/gl-infra/delivery/-/issues/1617 * Omnibus will require `GITLAB_WORKHORSE_VERSION` for versions < 13.9.X https://gitlab.com/gitlab-com/gl-infra/delivery/-/issues/1617#note_527838528 * Only auto-deploy tagging was affected by this and https://gitlab.com/gitlab-org/release-tools/-/merge_requests/1389 fixed it https://gitlab.com/gitlab-com/gl-infra/delivery/-/issues/1617#note_528014370 * We will propagate a bogus workhorse version to CNG Images and Omnibus, but they both ignore it now https://gitlab.com/gitlab-com/gl-infra/delivery/-/issues/1617#note_528014370 * CNG will require `GITLAB_WORKHORSE_VERSION` for versions < 13.8.X https://gitlab.com/gitlab-com/gl-infra/delivery/-/issues/1617#note_528029794 * **TOPIC** [14.1] Cleanup every workhorse code reference https://gitlab.com/gitlab-com/gl-infra/delivery/-/issues/1619 * **TOPIC** omnibus https://gitlab.com/gitlab-org/gitlab/-/issues/324194#note_527282509 * What will happen on the next security release? https://gitlab.com/gitlab-org/gitlab/-/issues/324194#note_527832573 * **TOPIC** CNG images https://gitlab.com/gitlab-org/gitlab/-/issues/324194#note_527282790 * What will happen on the next security release? https://gitlab.com/gitlab-org/gitlab/-/issues/324194#note_527834913 * **TOPIC** security release tooling / process https://gitlab.com/gitlab-org/gitlab/-/issues/324194#note_527283175 * **TOPIC** chatops https://gitlab.com/gitlab-org/gitlab/-/issues/324194#note_527368517 <!-- end-discoto-summary -->