| Commit message (Collapse) | Author | Age |
| |
|
| |
|
|
|
|
|
| |
https://about.gitlab.com/releases/2020/02/22/gitlab-12-8-released/
https://about.gitlab.com/releases/2020/02/24/gitlab-12-8-1-released/
|
|
|
|
| |
https://about.gitlab.com/releases/2020/01/31/gitlab-12-7-5-released/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- CVE-2020-7966
- CVE-2020-8114
- CVE-2020-7973
- CVE-2020-6833
- CVE-2020-7971
- CVE-2020-7967
- CVE-2020-7972
- CVE-2020-7968
- CVE-2020-7979
- CVE-2020-7969
- CVE-2020-7978
- CVE-2020-7974
- CVE-2020-7977
- CVE-2020-7976
- CVE-2019-16779
- CVE-2019-18978
- CVE-2019-16892
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
- gitlab-shell no longer requires ruby for anything else than the
install script, so the bundlerEnv stuff could be dropped
- gitlab-shell and gitlab-workhorse now report their versions
correctly
|
|
GitLab recently restructured their repos; whereas previously they had
one gitlab-ce and one gitlab-ee repo, they're now one and the
same. All proprietary components are put into the ee subdirectory -
removing it gives us the foss / community version of GitLab. For more
info, see
https://about.gitlab.com/2019/02/21/merging-ce-and-ee-codebases/
This gives us the opportunity to simplify things quite a bit, since we
don't have to keep track of two separate versions of either the base
data or rubyEnv.
|