public
/
nixpkgs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
nixpkgs/pkgs/applications/version-management/gitlab/data.json

13 lines
340 B
JSON
Raw Normal View History

gitlab: 11.4.4 -> 11.5.0, add data.json, make default.nix use it
2018-11-23 06:03:02 -08:00
{
gitlab: 12.3.4 -> 12.3.5
2019-10-08 07:35:50 -07:00
"version": "12.3.5",
"repo_hash": "12ywspgnbwm232vmzbqhkqmwmcrb9pvihsayzmw0cxvhlfwq6995",
gitlab: Refactor for new repo structure 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.
2019-10-08 06:52:11 -07:00
"owner": "gitlab-org",
"repo": "gitlab",
gitlab: 12.3.4 -> 12.3.5
2019-10-08 07:35:50 -07:00
"rev": "v12.3.5-ee",
gitlab: Refactor for new repo structure 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.
2019-10-08 06:52:11 -07:00
"passthru": {
"GITALY_SERVER_VERSION": "1.65.1",
"GITLAB_PAGES_VERSION": "1.9.0",
"GITLAB_SHELL_VERSION": "10.0.0",
"GITLAB_WORKHORSE_VERSION": "8.10.0"
gitlab: 11.4.4 -> 11.5.0, add data.json, make default.nix use it
2018-11-23 06:03:02 -08:00
}
gitlab-ee: 11.10.5 -> 11.10.8
2019-07-04 14:51:48 -07:00
}