diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-01-11 15:10:32 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-01-11 15:10:32 +0000 |
| commit | ec971a05e380fa580ae75dea30ab963112096525 (patch) | |
| tree | 33d9fee648491f9900024ba25e681535a7684997 /workhorse/PROCESS.md | |
| parent | f469daf1dc805d4c6a689067094112d4ed68d775 (diff) | |
| download | gitlab-ce-ec971a05e380fa580ae75dea30ab963112096525.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'workhorse/PROCESS.md')
| -rw-r--r-- | workhorse/PROCESS.md | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/workhorse/PROCESS.md b/workhorse/PROCESS.md index 07f553dd387..797de59d47e 100644 --- a/workhorse/PROCESS.md +++ b/workhorse/PROCESS.md @@ -42,6 +42,7 @@ maintainers. The release process is: - the new version will only be deployed to `gitlab.com` if [`GITLAB_WORKHORSE_VERSION`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/GITLAB_WORKHORSE_VERSION) is updated accordingly; if applicable, please remind the person who originally asked for a new release to make this change (the MR should include a link back to the [version tag](https://gitlab.com/gitlab-org/gitlab-workhorse/-/tags) and a copy of the changelog) +- the person who updates GITLAB_WORKHORSE_VERSION should also run `scripts/update-workhorse` after commiting the new GITLAB_WORKHORSE_VERSION. If they forget they will be reminded by CI. ## Security releases |