JakeHillion/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
09a1ae83f9
nixpkgs/pkgs/applications/version-management/gitlab/rubyEnv/Gemfile.lock

1337 lines
33 KiB
Plaintext
Raw Normal View History

nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
GEM
remote: https://rubygems.org/
specs:
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
RedCloth (4.3.2)
gitlab: 9.5.2 -> 9.5.5
2017-09-21 19:23:16 +01:00
abstract_type (0.0.7)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
ace-rails-ap (4.1.2)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
acme-client (2.0.2)
faraday (~> 0.9, >= 0.9.1)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
actioncable (5.2.3)
actionpack (= 5.2.3)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
nio4r (~> 2.0)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
websocket-driver (>= 0.6.1)
actionmailer (5.2.3)
actionpack (= 5.2.3)
actionview (= 5.2.3)
activejob (= 5.2.3)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
mail (~> 2.5, >= 2.5.4)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
rails-dom-testing (~> 2.0)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
actionpack (5.2.3)
actionview (= 5.2.3)
activesupport (= 5.2.3)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
rack (~> 2.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
rack-test (>= 0.6.3)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
rails-dom-testing (~> 2.0)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
rails-html-sanitizer (~> 1.0, >= 1.0.2)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
actionview (5.2.3)
activesupport (= 5.2.3)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
builder (~> 3.1)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
erubi (~> 1.4)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
rails-dom-testing (~> 2.0)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
rails-html-sanitizer (~> 1.0, >= 1.0.3)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
activejob (5.2.3)
activesupport (= 5.2.3)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
globalid (>= 0.3.6)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
activemodel (5.2.3)
activesupport (= 5.2.3)
activerecord (5.2.3)
activemodel (= 5.2.3)
activesupport (= 5.2.3)
arel (>= 9.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
activerecord-explain-analyze (0.1.0)
activerecord (>= 4)
pg
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
activestorage (5.2.3)
actionpack (= 5.2.3)
activerecord (= 5.2.3)
marcel (~> 0.3.1)
activesupport (5.2.3)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
concurrent-ruby (~> 1.0, >= 1.0.2)
i18n (>= 0.7, < 2)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
minitest (~> 5.1)
tzinfo (~> 1.1)
gitlab-ce: 11.9.11 -> 11.10.4
2019-05-03 19:21:55 +01:00
acts-as-taggable-on (6.0.0)
activerecord (~> 5.0)
gitlab: 9.5.2 -> 9.5.5
2017-09-21 19:23:16 +01:00
adamantium (0.2.0)
ice_nine (~> 0.11.0)
memoizable (~> 0.4.0)
gitlab: 10.0.2 -> 10.1.1
2017-11-03 21:27:58 +00:00
addressable (2.5.2)
public_suffix (>= 2.0.2, < 4.0)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
aes_key_wrap (1.0.1)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
akismet (2.0.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
apollo_upload_server (2.0.0.beta.3)
graphql (>= 1.8)
rails (>= 4.2)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
arel (9.0.0)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
asana (0.8.1)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
faraday (~> 0.9)
faraday_middleware (~> 0.9)
faraday_middleware-multi_json (~> 0.0)
oauth2 (~> 1.0)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
asciidoctor (2.0.10)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
asciidoctor-include-ext (0.3.1)
asciidoctor (>= 1.5.6, < 3.0.0)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
asciidoctor-plantuml (0.0.9)
asciidoctor (>= 1.5.6, < 3.0.0)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
ast (2.4.0)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
atlassian-jwt (0.2.0)
jwt (~> 2.1.0)
gitlab: 10.7.0 -> 10.8.0
2018-05-23 21:23:48 +01:00
attr_encrypted (3.1.0)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
encryptor (~> 3.0.0)
gitlab-ce: 11.9.11 -> 11.10.4
2019-05-03 19:21:55 +01:00
attr_required (1.0.1)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
awesome_print (1.8.0)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
aws-sdk (2.9.32)
aws-sdk-resources (= 2.9.32)
aws-sdk-core (2.9.32)
aws-sigv4 (~> 1.0)
jmespath (~> 1.0)
aws-sdk-resources (2.9.32)
aws-sdk-core (= 2.9.32)
aws-sigv4 (1.0.0)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
axiom-types (0.1.1)
descendants_tracker (~> 0.0.4)
ice_nine (~> 0.11.0)
thread_safe (~> 0.3, >= 0.3.1)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
babosa (1.0.2)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
base32 (0.3.2)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
batch-loader (1.4.0)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
bcrypt (3.1.12)
gitlab: 9.4.5 -> 9.5.2
2017-09-03 14:38:28 +01:00
bcrypt_pbkdf (1.0.0)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
benchmark-ips (2.3.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
benchmark-memory (0.1.2)
memory_profiler (~> 0.9)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
better_errors (2.5.0)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
coderay (>= 1.0.0)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
erubi (>= 1.0.0)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
rack (>= 0.9.0)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
bindata (2.4.3)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
binding_ninja (0.2.3)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
binding_of_caller (0.8.0)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
debug_inspector (>= 0.0.1)
gitlab: 12.3.5 -> 12.4.0 - 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
2019-10-23 21:47:24 +01:00
bootsnap (1.4.5)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
msgpack (~> 1.0)
gitlab-ce: 11.9.11 -> 11.10.4
2019-05-03 19:21:55 +01:00
bootstrap_form (4.2.0)
actionpack (>= 5.0)
activemodel (>= 5.0)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
brakeman (4.2.1)
gitlab: 11.2.3 -> 11.3.0
2018-09-25 01:32:02 +01:00
browser (2.5.3)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
builder (3.2.3)
bullet (5.5.1)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
activesupport (>= 3.0.0)
gitlab: 8.10.6 -> 8.11.2
2016-08-26 13:08:53 +01:00
uniform_notifier (~> 1.10.0)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
bundler-audit (0.5.0)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
bundler (~> 1.2)
thor (~> 0.18)
gitlab: 11.6.3 -> 11.7.4
2019-02-05 19:40:41 +00:00
byebug (9.1.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
capybara (3.22.0)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
addressable
gitlab: 9.5.5 -> 10.0.2
2017-09-28 19:09:31 +01:00
mini_mime (>= 0.1.3)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
nokogiri (~> 1.8)
rack (>= 1.6.0)
rack-test (>= 0.6.3)
regexp_parser (~> 1.5)
xpath (~> 3.2)
gitlab: 11.6.3 -> 11.7.4
2019-02-05 19:40:41 +00:00
capybara-screenshot (1.0.22)
capybara (>= 1.0, < 4)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
launchy
gitlab: 11.6.3 -> 11.7.4
2019-02-05 19:40:41 +00:00
carrierwave (1.3.1)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
activemodel (>= 4.0.0)
activesupport (>= 4.0.0)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
mime-types (>= 1.16)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
cause (0.1)
gitlab: 11.7.5 -> 11.8.2
2019-03-16 23:52:22 +00:00
character_set (1.1.2)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
charlock_holmes (0.7.6)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
childprocess (0.9.0)
gitlab: 10.1.1 -> 10.3.3
2018-01-07 03:59:27 +00:00
ffi (~> 1.0, >= 1.0.11)
gitlab: 8.10.6 -> 8.11.2
2016-08-26 13:08:53 +01:00
chronic (0.10.2)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
chunky_png (1.3.5)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
citrus (3.0.2)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
claide (1.0.3)
claide-plugins (0.9.2)
cork
nap
open4 (~> 1.3)
gitlab: 11.2.3 -> 11.3.0
2018-09-25 01:32:02 +01:00
coderay (1.1.2)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
coercible (1.0.0)
descendants_tracker (~> 0.0.1)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
colored2 (3.1.2)
gitlab: 11.2.3 -> 11.3.0
2018-09-25 01:32:02 +01:00
commonmarker (0.17.13)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
ruby-enum (~> 0.5)
gitlab: 9.5.2 -> 9.5.5
2017-09-21 19:23:16 +01:00
concord (0.1.5)
adamantium (~> 0.2.0)
equalizer (~> 0.0.9)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
concurrent-ruby (1.1.5)
gitlab: 11.3.4 -> 11.4.0
2018-10-23 11:24:11 +01:00
connection_pool (2.2.2)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
contracts (0.11.0)
cork (0.3.0)
colored2 (~> 3.1)
countries (3.0.0)
i18n_data (~> 0.8.0)
sixarm_ruby_unaccent (~> 1.1)
unicode_utils (~> 1.4)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
crack (0.4.3)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
safe_yaml (~> 1.0.0)
gitlab: 10.7.0 -> 10.8.0
2018-05-23 21:23:48 +01:00
crass (1.0.4)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
creole (0.5.0)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
css_parser (1.5.0)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
addressable
gitlab: 11.3.4 -> 11.4.0
2018-10-23 11:24:11 +01:00
daemons (1.2.6)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
danger (6.0.9)
claide (~> 1.0)
claide-plugins (>= 0.9.2)
colored2 (~> 3.1)
cork (~> 0.1)
faraday (~> 0.9)
faraday-http-cache (~> 2.0)
git (~> 1.5)
kramdown (~> 2.0)
kramdown-parser-gfm (~> 1.0)
no_proxy_fix
octokit (~> 4.7)
terminal-table (~> 1)
gitlab: 11.6.3 -> 11.7.4
2019-02-05 19:40:41 +00:00
database_cleaner (1.7.0)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
debug_inspector (0.0.3)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
debugger-ruby_core_source (1.3.8)
gitlab: 11.7.5 -> 11.8.2
2019-03-16 23:52:22 +00:00
deckar01-task_list (2.2.0)
gitlab: 8.12.8 -> 8.13.5
2016-11-10 05:16:42 +00:00
html-pipeline
gitlab: 10.0.2 -> 10.1.1
2017-11-03 21:27:58 +00:00
declarative (0.0.10)
declarative-option (0.1.0)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
default_value_for (3.2.0)
activerecord (>= 3.2.0, < 6.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
derailed_benchmarks (1.3.5)
benchmark-ips (~> 2)
get_process_mem (~> 0)
heapy (~> 0)
memory_profiler (~> 0)
rack (>= 1)
rake (> 10, < 13)
thor (~> 0.19)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
descendants_tracker (0.0.4)
thread_safe (~> 0.3, >= 0.3.1)
gitlab: 10.7.0 -> 10.8.0
2018-05-23 21:23:48 +01:00
device_detector (1.0.0)
gitlab: 12.3.5 -> 12.4.0 - 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
2019-10-23 21:47:24 +01:00
devise (4.7.1)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
bcrypt (~> 3.0)
orm_adapter (~> 0.1)
gitlab: 12.3.5 -> 12.4.0 - 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
2019-10-23 21:47:24 +01:00
railties (>= 4.1.0)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
responders
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
warden (~> 1.2.3)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
devise-two-factor (3.0.0)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
activesupport
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
attr_encrypted (>= 1.3, < 4, != 2)
devise (~> 4.0)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
railties
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
rotp (~> 2.0)
gitlab: 9.4.5 -> 9.5.2
2017-09-03 14:38:28 +01:00
diff-lcs (1.3)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
diffy (3.1.0)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
discordrb-webhooks-blackst0ne (3.3.0)
rest-client (~> 2.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
docile (1.3.1)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
domain_name (0.5.20180417)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
unf (>= 0.0.5, < 1.0.0)
gitlab: 10.7.0 -> 10.8.0
2018-05-23 21:23:48 +01:00
doorkeeper (4.3.2)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
railties (>= 4.2)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
doorkeeper-openid_connect (1.5.0)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
doorkeeper (~> 4.3)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
json-jwt (~> 1.6)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
ed25519 (1.2.4)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
elasticsearch (5.0.3)
elasticsearch-api (= 5.0.3)
elasticsearch-transport (= 5.0.3)
elasticsearch-api (5.0.3)
multi_json
elasticsearch-model (0.1.9)
activesupport (> 3)
elasticsearch (> 0.4)
hashie
elasticsearch-rails (0.1.9)
elasticsearch-transport (5.0.3)
faraday
multi_json
gitlab: 8.15.4 -> 8.16.1
2017-01-24 20:28:13 +00:00
email_reply_trimmer (0.1.6)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
email_spec (2.2.0)
htmlentities (~> 4.3.3)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
launchy (~> 2.1)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
mail (~> 2.7)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
encryptor (3.0.0)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
equalizer (0.0.11)
gitlab: 12.3.5 -> 12.4.0 - 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
2019-10-23 21:47:24 +01:00
erubi (1.9.0)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
escape_utils (1.2.1)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
et-orbi (1.2.1)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
tzinfo
gitlab: 11.3.4 -> 11.4.0
2018-10-23 11:24:11 +01:00
eventmachine (1.2.7)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
excon (0.62.0)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
execjs (2.6.0)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
expression_parser (0.9.0)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
extended-markdown-filter (0.6.0)
html-pipeline (~> 2.0)
gitlab: 12.3.5 -> 12.4.0 - 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
2019-10-23 21:47:24 +01:00
factory_bot (5.1.0)
activesupport (>= 4.2.0)
factory_bot_rails (5.1.0)
factory_bot (~> 5.1.0)
railties (>= 4.2.0)
gitlab: 10.0.2 -> 10.1.1
2017-11-03 21:27:58 +00:00
faraday (0.12.2)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
multipart-post (>= 1.2, < 3)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
faraday-http-cache (2.0.0)
faraday (~> 0.8)
gitlab: 10.7.0 -> 10.8.0
2018-05-23 21:23:48 +01:00
faraday_middleware (0.12.2)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
faraday (>= 0.7.4, < 1.0)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
faraday_middleware-aws-signers-v4 (0.1.7)
aws-sdk-resources (~> 2)
faraday (~> 0.9)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
faraday_middleware-multi_json (0.0.6)
faraday_middleware
multi_json
gitlab: 10.3.4 -> 10.5.4
2018-03-14 13:14:03 +00:00
fast_blank (1.0.0)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
fast_gettext (1.6.0)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
ffaker (2.10.0)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
ffi (1.11.1)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
flipper (0.13.0)
flipper-active_record (0.13.0)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
activerecord (>= 3.2, < 6)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
flipper (~> 0.13.0)
flipper-active_support_cache_store (0.13.0)
gitlab: 10.3.4 -> 10.5.4
2018-03-14 13:14:03 +00:00
activesupport (>= 3.2, < 6)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
flipper (~> 0.13.0)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
flowdock (0.7.1)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
httparty (~> 0.7)
multi_json
gitlab: 11.8.2 -> 11.9.0
2019-03-22 23:48:02 +00:00
fog-aliyun (0.3.3)
fog-core
fog-json
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
ipaddress (~> 0.8)
xml-simple (~> 1.1)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
fog-aws (3.5.2)
gitlab: 11.8.2 -> 11.9.0
2019-03-22 23:48:02 +00:00
fog-core (~> 2.1)
fog-json (~> 1.1)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
fog-xml (~> 0.1)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
ipaddress (~> 0.8)
gitlab: 11.8.2 -> 11.9.0
2019-03-22 23:48:02 +00:00
fog-core (2.1.0)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
builder
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
excon (~> 0.58)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
formatador (~> 0.2)
gitlab: 11.8.2 -> 11.9.0
2019-03-22 23:48:02 +00:00
mime-types
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
fog-google (1.9.1)
gitlab: 11.8.2 -> 11.9.0
2019-03-22 23:48:02 +00:00
fog-core (<= 2.1.0)
fog-json (~> 1.2)
fog-xml (~> 0.1.0)
gitlab: 11.2.3 -> 11.3.0
2018-09-25 01:32:02 +01:00
google-api-client (~> 0.23.0)
gitlab: 11.8.2 -> 11.9.0
2019-03-22 23:48:02 +00:00
fog-json (1.2.0)
fog-core
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
multi_json (~> 1.10)
gitlab: 11.8.2 -> 11.9.0
2019-03-22 23:48:02 +00:00
fog-local (0.6.0)
fog-core (>= 1.27, < 3.0)
fog-openstack (1.0.8)
fog-core (~> 2.1)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
fog-json (>= 1.0)
ipaddress (>= 0.8)
fog-rackspace (0.1.1)
fog-core (>= 1.35)
fog-json (>= 1.0)
fog-xml (>= 0.1)
ipaddress (>= 0.8)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
fog-xml (0.1.3)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
fog-core
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
nokogiri (>= 1.5.11, < 2.0.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
font-awesome-rails (4.7.0.4)
railties (>= 3.2, < 6.0)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
foreman (0.84.0)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
thor (~> 0.19.1)
formatador (0.2.5)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
fugit (1.2.1)
et-orbi (~> 1.1, >= 1.1.8)
gitlab: 11.7.5 -> 11.8.2
2019-03-16 23:52:22 +00:00
raabro (~> 1.1)
gitlab: 9.4.5 -> 9.5.2
2017-09-03 14:38:28 +01:00
fuubar (2.2.0)
rspec-core (~> 3.0)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
ruby-progressbar (~> 1.4)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
gemoji (3.0.1)
gitlab: 9.5.2 -> 9.5.5
2017-09-21 19:23:16 +01:00
gemojione (3.3.0)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
json
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
get_process_mem (0.2.3)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
gettext (3.2.9)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
locale (>= 2.0.5)
text (>= 1.3.0)
gettext_i18n_rails (1.8.0)
fast_gettext (>= 0.9.0)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
gettext_i18n_rails_js (1.3.0)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
gettext (>= 3.0.2)
gettext_i18n_rails (>= 0.7.1)
po_to_json (>= 1.0.0)
rails (>= 3.2.0)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
git (1.5.0)
gitlab: 12.3.5 -> 12.4.0 - 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
2019-10-23 21:47:24 +01:00
gitaly (1.65.0)
gitlab: 11.5.0 -> 11.5.1
2018-12-04 19:06:09 +00:00
grpc (~> 1.0)
gitlab: 10.7.0 -> 10.8.0
2018-05-23 21:23:48 +01:00
github-markup (1.7.0)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
gitlab-labkit (0.5.2)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
actionpack (~> 5)
activesupport (~> 5)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
grpc (~> 1.19)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
jaeger-client (~> 0.10)
opentracing (~> 0.4)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
redis (> 3.0.0, < 5.0.0)
gitlab-license (1.0.0)
gitlab-ce: 11.9.11 -> 11.10.4
2019-05-03 19:21:55 +01:00
gitlab-markup (1.7.0)
gitlab: 12.3.5 -> 12.4.0 - 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
2019-10-23 21:47:24 +01:00
gitlab-net-dns (0.9.1)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
gitlab-peek (0.0.1)
railties (>= 4.0.0)
gitlab-sidekiq-fetcher (0.5.2)
gitlab: 11.3.4 -> 11.4.0
2018-10-23 11:24:11 +01:00
sidekiq (~> 5)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
gitlab-styles (2.8.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
rubocop (~> 0.69.0)
gitlab: 10.3.4 -> 10.5.4
2018-03-14 13:14:03 +00:00
rubocop-gitlab-security (~> 0.1.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
rubocop-performance (~> 1.1.0)
gitlab: 10.3.4 -> 10.5.4
2018-03-14 13:14:03 +00:00
rubocop-rspec (~> 1.19)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
gitlab_chronic_duration (0.10.6.1)
numerizer (~> 0.1.1)
gitlab: 11.8.2 -> 11.9.0
2019-03-22 23:48:02 +00:00
gitlab_omniauth-ldap (2.1.1)
gitlab: 9.3.4 -> 9.4.3
2017-08-06 15:27:54 +01:00
net-ldap (~> 0.16)
omniauth (~> 1.3)
pyu-ruby-sasl (>= 0.0.3.3, < 0.1)
rubyntlm (~> 0.5)
gitlab-ce: 11.9.8 -> 11.9.11
2019-05-01 13:48:27 +01:00
globalid (0.4.2)
gitlab: 10.1.1 -> 10.3.3
2018-01-07 03:59:27 +00:00
activesupport (>= 4.2.0)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
gon (6.2.0)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
actionpack (>= 3.0)
multi_json
request_store (>= 1.0)
gitlab: 11.2.3 -> 11.3.0
2018-09-25 01:32:02 +01:00
google-api-client (0.23.4)
gitlab: 10.0.2 -> 10.1.1
2017-11-03 21:27:58 +00:00
addressable (~> 2.5, >= 2.5.1)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
googleauth (>= 0.5, < 0.7.0)
gitlab: 10.0.2 -> 10.1.1
2017-11-03 21:27:58 +00:00
httpclient (>= 2.8.1, < 3.0)
mime-types (~> 3.0)
representable (~> 3.0)
retriable (>= 2.0, < 4.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
google-protobuf (3.7.1)
googleapis-common-protos-types (1.0.4)
gitlab: 10.3.4 -> 10.5.4
2018-03-14 13:14:03 +00:00
google-protobuf (~> 3.0)
gitlab: 11.5.0 -> 11.5.1
2018-12-04 19:06:09 +00:00
googleauth (0.6.6)
gitlab: 10.0.2 -> 10.1.1
2017-11-03 21:27:58 +00:00
faraday (~> 0.12)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
jwt (>= 1.4, < 3.0)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
memoist (~> 0.12)
multi_json (~> 1.11)
gitlab: 11.5.0 -> 11.5.1
2018-12-04 19:06:09 +00:00
os (>= 0.9, < 2.0)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
signet (~> 0.7)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
gpgme (2.0.18)
mini_portile2 (~> 2.3)
gitlab: 11.3.4 -> 11.4.0
2018-10-23 11:24:11 +01:00
grape (1.1.0)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
activesupport
builder
gitlab: 9.4.5 -> 9.5.2
2017-09-03 14:38:28 +01:00
mustermann-grape (~> 1.0.0)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
rack (>= 1.3.0)
rack-accept
virtus (>= 1.0.0)
gitlab: 10.7.0 -> 10.8.0
2018-05-23 21:23:48 +01:00
grape-entity (0.7.1)
activesupport (>= 4.0)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
multi_json (>= 1.3.2)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
grape-path-helpers (1.1.0)
activesupport
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
grape (~> 1.0)
rake (~> 12)
gitlab: 9.5.5 -> 10.0.2
2017-09-28 19:09:31 +01:00
grape_logging (1.7.0)
grape
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
graphiql-rails (1.4.10)
railties
sprockets-rails
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
graphql (1.9.11)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
graphql-docs (1.6.0)
commonmarker (~> 0.16)
escape_utils (~> 1.2)
extended-markdown-filter (~> 0.4)
gemoji (~> 3.0)
graphql (~> 1.6)
html-pipeline (~> 2.8)
sass (~> 3.4)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
grpc (1.19.0)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
google-protobuf (~> 3.1)
gitlab: 10.3.4 -> 10.5.4
2018-03-14 13:14:03 +00:00
googleapis-common-protos-types (~> 1.0.0)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
gssapi (1.2.0)
ffi (>= 1.0.1)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
haml (5.0.4)
temple (>= 0.8.0)
gitlab: 8.11.2 -> 8.12.1
2016-09-27 14:49:21 +01:00
tilt
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
haml_lint (0.31.0)
gitlab: 9.4.5 -> 9.5.2
2017-09-03 14:38:28 +01:00
haml (>= 4.0, < 5.1)
rainbow
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
rake (>= 10, < 13)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
rubocop (>= 0.50.0)
gitlab: 8.11.2 -> 8.12.1
2016-09-27 14:49:21 +01:00
sysexits (~> 1.1)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
hamlit (2.8.8)
temple (>= 0.8.0)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
thor
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
tilt
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
hangouts-chat (0.0.5)
gitlab: 11.8.2 -> 11.9.0
2019-03-22 23:48:02 +00:00
hashdiff (0.3.8)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
hashie (3.5.7)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
hashie-forbidden_attributes (0.1.1)
hashie (>= 3.0)
health_check (2.6.0)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
rails (>= 4.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
heapy (0.1.4)
gitlab-ce: 11.9.1 -> 11.9.8
2019-04-22 22:40:40 +01:00
hipchat (1.5.2)
httparty
mimemagic
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
html-pipeline (2.8.4)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
activesupport (>= 2)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
nokogiri (>= 1.4)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
html2text (0.2.0)
nokogiri (~> 1.6)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
htmlentities (4.3.4)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
http (3.3.0)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
addressable (~> 2.3)
http-cookie (~> 1.0)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
http-form_data (~> 2.0)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
http_parser.rb (~> 0.6.0)
http-cookie (1.0.3)
domain_name (~> 0.5)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
http-form_data (2.1.1)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
http_parser.rb (0.6.0)
gitlab-ce: 11.9.11 -> 11.10.4
2019-05-03 19:21:55 +01:00
httparty (0.16.4)
mime-types (~> 3.0)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
multi_xml (>= 0.5.2)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
httpclient (2.8.3)
gitlab: 12.3.5 -> 12.4.0 - 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
2019-10-23 21:47:24 +01:00
i18n (1.7.0)
gitlab: 10.1.1 -> 10.3.3
2018-01-07 03:59:27 +00:00
concurrent-ruby (~> 1.0)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
i18n_data (0.8.0)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
icalendar (2.4.1)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
ice_nine (0.11.2)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
influxdb (0.2.3)
cause
json
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
invisible_captcha (0.12.1)
rails (>= 3.2.0)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
ipaddress (0.8.3)
gitlab: 11.7.5 -> 11.8.2
2019-03-16 23:52:22 +00:00
jaeger-client (0.10.0)
opentracing (~> 0.3)
thrift
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
jaro_winkler (1.5.3)
jira-ruby (1.7.1)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
activesupport
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
atlassian-jwt
gitlab: 9.5.5 -> 10.0.2
2017-09-28 19:09:31 +01:00
multipart-post
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
oauth (~> 0.5, >= 0.5.0)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
jmespath (1.3.1)
gitlab: 11.7.5 -> 11.8.2
2019-03-16 23:52:22 +00:00
js_regex (3.1.1)
character_set (~> 1.1)
regexp_parser (~> 1.1)
regexp_property_values (~> 0.3)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
json (1.8.6)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
json-jwt (1.9.4)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
activesupport
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
aes_key_wrap
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
bindata
gitlab: 10.0.2 -> 10.1.1
2017-11-03 21:27:58 +00:00
json-schema (2.8.0)
addressable (>= 2.4)
gitlab: 11.6.3 -> 11.7.4
2019-02-05 19:40:41 +00:00
jwt (2.1.0)
gitlab: 9.4.5 -> 9.5.2
2017-09-03 14:38:28 +01:00
kaminari (1.0.1)
activesupport (>= 4.1.0)
kaminari-actionview (= 1.0.1)
kaminari-activerecord (= 1.0.1)
kaminari-core (= 1.0.1)
kaminari-actionview (1.0.1)
actionview
kaminari-core (= 1.0.1)
kaminari-activerecord (1.0.1)
activerecord
kaminari-core (= 1.0.1)
kaminari-core (1.0.1)
gitlab: 11.8.2 -> 11.9.0
2019-03-22 23:48:02 +00:00
kgio (2.11.2)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
knapsack (1.17.0)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
rake
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
kramdown (2.1.0)
kramdown-parser-gfm (1.1.0)
kramdown (~> 2.0)
kubeclient (4.4.0)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
http (~> 3.0)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
recursive-open-struct (~> 1.0, >= 1.0.4)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
rest-client (~> 2.0)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
launchy (2.4.3)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
addressable (~> 2.3)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
letter_opener (1.7.0)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
launchy (~> 2.2)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
letter_opener_web (1.3.4)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
actionmailer (>= 3.2)
letter_opener (~> 1.0)
railties (>= 3.2)
gitlab: 11.2.3 -> 11.3.0
2018-09-25 01:32:02 +01:00
license_finder (5.4.0)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
bundler
rubyzip
thor
gitlab: 11.2.3 -> 11.3.0
2018-09-25 01:32:02 +01:00
toml (= 0.2.0)
with_env (= 1.1.0)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
xml-simple
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
licensee (8.9.2)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
rugged (~> 0.24)
locale (2.1.2)
gitlab: 10.7.0 -> 10.8.0
2018-05-23 21:23:48 +01:00
lograge (0.10.0)
actionpack (>= 4)
activesupport (>= 4)
railties (>= 4)
request_store (~> 1.0)
gitlab: 12.3.5 -> 12.4.0 - 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
2019-10-23 21:47:24 +01:00
loofah (2.3.0)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
crass (~> 1.0.2)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
nokogiri (>= 1.5.9)
gitlab: 11.6.3 -> 11.7.4
2019-02-05 19:40:41 +00:00
mail (2.7.1)
gitlab: 10.1.1 -> 10.3.3
2018-01-07 03:59:27 +00:00
mini_mime (>= 0.1.1)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
mail_room (0.9.1)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
marcel (0.3.3)
mimemagic (~> 0.3.2)
gitlab: 10.0.2 -> 10.1.1
2017-11-03 21:27:58 +00:00
memoist (0.16.0)
gitlab: 9.5.2 -> 9.5.5
2017-09-21 19:23:16 +01:00
memoizable (0.4.2)
thread_safe (~> 0.3, >= 0.3.1)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
memory_profiler (0.9.13)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
method_source (0.9.2)
mime-types (3.2.2)
gitlab: 10.0.2 -> 10.1.1
2017-11-03 21:27:58 +00:00
mime-types-data (~> 3.2015)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
mime-types-data (3.2019.0331)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
mimemagic (0.3.2)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
mini_magick (4.9.5)
gitlab: 11.3.4 -> 11.4.0
2018-10-23 11:24:11 +01:00
mini_mime (1.0.1)
gitlab: 11.7.5 -> 11.8.2
2019-03-16 23:52:22 +00:00
mini_portile2 (2.4.0)
gitlab: 11.6.3 -> 11.7.4
2019-02-05 19:40:41 +00:00
minitest (5.11.3)
gitlab: 12.3.5 -> 12.4.0 - 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
2019-10-23 21:47:24 +01:00
msgpack (1.3.1)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
multi_json (1.13.1)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
multi_xml (0.6.0)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
multipart-post (2.0.0)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
murmurhash3 (0.1.6)
gitlab: 11.3.4 -> 11.4.0
2018-10-23 11:24:11 +01:00
mustermann (1.0.3)
gitlab: 9.4.5 -> 9.5.2
2017-09-03 14:38:28 +01:00
mustermann-grape (1.0.0)
mustermann (~> 1.0.0)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
nakayoshi_fork (0.0.4)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
nap (1.1.0)
gitlab: 9.3.4 -> 9.4.3
2017-08-06 15:27:54 +01:00
net-ldap (0.16.0)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
net-ntp (2.1.3)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
net-ssh (5.2.0)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
netrc (0.11.0)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
nio4r (2.3.1)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
no_proxy_fix (0.1.2)
nokogiri (1.10.4)
gitlab: 11.7.5 -> 11.8.2
2019-03-16 23:52:22 +00:00
mini_portile2 (~> 2.4.0)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
nokogumbo (1.5.0)
nokogiri
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
numerizer (0.1.1)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
oauth (0.5.4)
gitlab: 11.6.3 -> 11.7.4
2019-02-05 19:40:41 +00:00
oauth2 (1.4.1)
faraday (>= 0.8, < 0.16.0)
jwt (>= 1.0, < 3.0)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
multi_json (~> 1.3)
multi_xml (~> 0.5)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
rack (>= 1.2, < 3)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
octokit (4.9.0)
gitlab: 8.15.4 -> 8.16.1
2017-01-24 20:28:13 +00:00
sawyer (~> 0.8.0, >= 0.5.3)
gitlab: 11.6.3 -> 11.7.4
2019-02-05 19:40:41 +00:00
omniauth (1.9.0)
hashie (>= 3.4.6, < 3.7.0)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
rack (>= 1.6.2, < 3)
gitlab: 10.5.4 -> 10.5.6
2018-03-22 01:08:49 +00:00
omniauth-auth0 (2.0.0)
omniauth-oauth2 (~> 1.4)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
omniauth-authentiq (0.3.3)
jwt (>= 1.5)
omniauth-oauth2 (>= 1.5)
gitlab: 11.6.3 -> 11.7.4
2019-02-05 19:40:41 +00:00
omniauth-azure-oauth2 (0.0.10)
jwt (>= 1.0, < 3.0)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
omniauth (~> 1.0)
gitlab: 10.0.2 -> 10.1.1
2017-11-03 21:27:58 +00:00
omniauth-oauth2 (~> 1.4)
gitlab: 9.5.2 -> 9.5.5
2017-09-21 19:23:16 +01:00
omniauth-cas3 (1.1.4)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
addressable (~> 2.3)
gitlab: 9.5.2 -> 9.5.5
2017-09-21 19:23:16 +01:00
nokogiri (~> 1.7, >= 1.7.1)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
omniauth (~> 1.2)
gitlab: 8.11.2 -> 8.12.1
2016-09-27 14:49:21 +01:00
omniauth-facebook (4.0.0)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
omniauth-oauth2 (~> 1.2)
gitlab: 10.7.0 -> 10.8.0
2018-05-23 21:23:48 +01:00
omniauth-github (1.3.0)
omniauth (~> 1.5)
omniauth-oauth2 (>= 1.4.0, < 2.0)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
omniauth-gitlab (1.0.3)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
omniauth (~> 1.0)
omniauth-oauth2 (~> 1.0)
gitlab: 11.6.3 -> 11.7.4
2019-02-05 19:40:41 +00:00
omniauth-google-oauth2 (0.6.0)
jwt (>= 2.0)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
omniauth (>= 1.1.1)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
omniauth-oauth2 (>= 1.5)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
omniauth-kerberos (0.3.0)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
omniauth-multipassword
timfel-krb5-auth (~> 0.8)
omniauth-multipassword (0.4.2)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
omniauth (~> 1.0)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
omniauth-oauth (1.1.0)
oauth
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
omniauth (~> 1.0)
gitlab: 11.6.3 -> 11.7.4
2019-02-05 19:40:41 +00:00
omniauth-oauth2 (1.6.0)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
oauth2 (~> 1.1)
gitlab: 11.6.3 -> 11.7.4
2019-02-05 19:40:41 +00:00
omniauth (~> 1.9)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
omniauth-oauth2-generic (0.2.2)
omniauth-oauth2 (~> 1.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
omniauth-salesforce (1.0.5)
omniauth (~> 1.0)
omniauth-oauth2 (~> 1.0)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
omniauth-saml (1.10.0)
omniauth (~> 1.3, >= 1.3.2)
ruby-saml (~> 1.7)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
omniauth-shibboleth (1.3.0)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
omniauth (>= 1.0.0)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
omniauth-twitter (1.4.0)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
omniauth-oauth (~> 1.1)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
rack
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
omniauth-ultraauth (0.0.2)
omniauth_openid_connect (~> 0.3.0)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
omniauth_crowd (2.2.3)
activesupport
nokogiri (>= 1.4.4)
omniauth (~> 1.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
omniauth_openid_connect (0.3.1)
addressable (~> 2.5)
omniauth (~> 1.3)
openid_connect (~> 1.1)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
open4 (1.3.4)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
openid_connect (1.1.6)
activemodel
attr_required (>= 1.0.0)
json-jwt (>= 1.5.0)
rack-oauth2 (>= 1.6.1)
swd (>= 1.0.0)
tzinfo
validate_email
validate_url
webfinger (>= 1.0.1)
opentracing (0.5.0)
gitlab: 11.7.5 -> 11.8.2
2019-03-16 23:52:22 +00:00
optimist (3.0.0)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
org-ruby (0.9.12)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
rubypants (~> 0.2)
orm_adapter (0.5.0)
gitlab: 11.5.0 -> 11.5.1
2018-12-04 19:06:09 +00:00
os (1.0.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
parallel (1.17.0)
parser (2.6.3.0)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
ast (~> 2.4.0)
gitlab: 11.2.3 -> 11.3.0
2018-09-25 01:32:02 +01:00
parslet (1.8.2)
gitlab-ce: 11.9.11 -> 11.10.4
2019-05-03 19:21:55 +01:00
pg (1.1.4)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
po_to_json (1.0.1)
json (>= 1.6.0)
premailer (1.10.4)
addressable
css_parser (>= 1.4.10)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
htmlentities (>= 4.0.0)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
premailer-rails (1.9.7)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
actionmailer (>= 3, < 6)
premailer (~> 1.7, >= 1.7.9)
gitlab: 9.5.2 -> 9.5.5
2017-09-21 19:23:16 +01:00
proc_to_ast (0.1.0)
coderay
parser
unparser
procto (0.0.3)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
prometheus-client-mmap (0.9.10)
gitlab: 11.2.3 -> 11.3.0
2018-09-25 01:32:02 +01:00
pry (0.11.3)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
coderay (~> 1.1.0)
gitlab: 11.2.3 -> 11.3.0
2018-09-25 01:32:02 +01:00
method_source (~> 0.9.0)
gitlab: 11.6.3 -> 11.7.4
2019-02-05 19:40:41 +00:00
pry-byebug (3.5.1)
byebug (~> 9.1)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
pry (~> 0.10)
gitlab: 11.3.4 -> 11.4.0
2018-10-23 11:24:11 +01:00
pry-rails (0.3.6)
pry (>= 0.10.4)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
public_suffix (3.1.0)
gitlab: 11.5.0 -> 11.5.1
2018-12-04 19:06:09 +00:00
puma (3.12.0)
puma_worker_killer (0.1.0)
get_process_mem (~> 0.2)
puma (>= 2.7, < 4)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
pyu-ruby-sasl (0.0.3.3)
gitlab: 11.7.5 -> 11.8.2
2019-03-16 23:52:22 +00:00
raabro (1.1.6)
gitlab-ce: 11.9.11 -> 11.10.4
2019-05-03 19:21:55 +01:00
rack (2.0.7)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
rack-accept (0.4.5)
rack (>= 0.4)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
rack-attack (4.4.1)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
rack
gitlab: 10.3.4 -> 10.5.4
2018-03-14 13:14:03 +00:00
rack-cors (1.0.2)
gitlab-ce: 11.9.11 -> 11.10.4
2019-05-03 19:21:55 +01:00
rack-oauth2 (1.9.3)
activesupport
attr_required
httpclient
json-jwt (>= 1.9.0)
rack
gitlab: 11.7.5 -> 11.8.2
2019-03-16 23:52:22 +00:00
rack-protection (2.0.5)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
rack
gitlab: 8.16.6 -> 8.17.4 for CVE-2017-0882
2017-03-02 03:18:19 +00:00
rack-proxy (0.6.0)
rack
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
rack-test (1.1.0)
rack (>= 1.0, < 3)
rack-timeout (0.5.1)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
rails (5.2.3)
actioncable (= 5.2.3)
actionmailer (= 5.2.3)
actionpack (= 5.2.3)
actionview (= 5.2.3)
activejob (= 5.2.3)
activemodel (= 5.2.3)
activerecord (= 5.2.3)
activestorage (= 5.2.3)
activesupport (= 5.2.3)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
bundler (>= 1.3.0)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
railties (= 5.2.3)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
sprockets-rails (>= 2.0.0)
rails-controller-testing (1.0.2)
actionpack (~> 5.x, >= 5.0.1)
actionview (~> 5.x, >= 5.0.1)
activesupport (~> 5.x)
rails-dom-testing (2.0.3)
activesupport (>= 4.2.0)
nokogiri (>= 1.6)
gitlab: 12.3.5 -> 12.4.0 - 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
2019-10-23 21:47:24 +01:00
rails-html-sanitizer (1.3.0)
loofah (~> 2.3)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
rails-i18n (5.1.1)
i18n (>= 0.7, < 2)
railties (>= 5.0, < 6)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
railties (5.2.3)
actionpack (= 5.2.3)
activesupport (= 5.2.3)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
method_source
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
rake (>= 0.8.7)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
thor (>= 0.19.0, < 2.0)
gitlab: 11.2.3 -> 11.3.0
2018-09-25 01:32:02 +01:00
rainbow (3.0.0)
gitlab: 11.8.2 -> 11.9.0
2019-03-22 23:48:02 +00:00
raindrops (0.19.0)
gitlab: 12.3.5 -> 12.4.0 - 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
2019-10-23 21:47:24 +01:00
rake (12.3.3)
gitlab: 10.3.4 -> 10.5.4
2018-03-14 13:14:03 +00:00
rb-fsevent (0.10.2)
rb-inotify (0.9.10)
ffi (>= 0.5.0, < 2)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
rblineprof (0.3.6)
debugger-ruby_core_source (~> 1.3)
gitlab: 11.7.5 -> 11.8.2
2019-03-16 23:52:22 +00:00
rbtrace (0.4.11)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
ffi (>= 1.0.6)
msgpack (>= 0.4.3)
gitlab: 11.7.5 -> 11.8.2
2019-03-16 23:52:22 +00:00
optimist (>= 3.0.0)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
rdoc (6.0.4)
gitlab: 9.4.5 -> 9.5.2
2017-09-03 14:38:28 +01:00
re2 (1.1.1)
gitlab-ce: 11.9.11 -> 11.10.4
2019-05-03 19:21:55 +01:00
recaptcha (4.13.1)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
json
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
recursive-open-struct (1.1.0)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
redis (4.1.2)
gitlab: 10.1.1 -> 10.3.3
2018-01-07 03:59:27 +00:00
redis-actionpack (5.0.2)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
actionpack (>= 4.0, < 6)
redis-rack (>= 1, < 3)
gitlab: 10.1.1 -> 10.3.3
2018-01-07 03:59:27 +00:00
redis-store (>= 1.1.0, < 2)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
redis-activesupport (5.0.7)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
activesupport (>= 3, < 6)
gitlab: 10.1.1 -> 10.3.3
2018-01-07 03:59:27 +00:00
redis-store (>= 1.3, < 2)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
redis-namespace (1.6.0)
redis (>= 3.0.4)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
redis-rack (2.0.5)
gitlab: 10.1.1 -> 10.3.3
2018-01-07 03:59:27 +00:00
rack (>= 1.5, < 3)
redis-store (>= 1.2, < 2)
redis-rails (5.0.2)
redis-actionpack (>= 5.0, < 6)
redis-activesupport (>= 5.0, < 6)
redis-store (>= 1.2, < 2)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
redis-store (1.6.0)
gitlab: 10.1.1 -> 10.3.3
2018-01-07 03:59:27 +00:00
redis (>= 2.2, < 5)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
regexp_parser (1.5.1)
gitlab: 11.7.5 -> 11.8.2
2019-03-16 23:52:22 +00:00
regexp_property_values (0.3.4)
gitlab: 10.0.2 -> 10.1.1
2017-11-03 21:27:58 +00:00
representable (3.0.4)
declarative (< 0.1.0)
declarative-option (< 0.2.0)
uber (< 0.2.0)
gitlab: 8.10.6 -> 8.11.2
2016-08-26 13:08:53 +01:00
request_store (1.3.1)
gitlab: 12.3.5 -> 12.4.0 - 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
2019-10-23 21:47:24 +01:00
responders (2.4.1)
actionpack (>= 4.2.0, < 6.0)
railties (>= 4.2.0, < 6.0)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
rest-client (2.0.2)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
http-cookie (>= 1.0.2, < 2.0)
mime-types (>= 1.16, < 4.0)
netrc (~> 0.8)
gitlab: 11.2.3 -> 11.3.0
2018-09-25 01:32:02 +01:00
retriable (3.1.2)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
rinku (2.0.0)
rotp (2.1.2)
gitlab: 12.3.5 -> 12.4.0 - 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
2019-10-23 21:47:24 +01:00
rouge (3.11.0)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
rqrcode (0.7.0)
chunky_png
rqrcode-rails3 (0.1.7)
rqrcode (>= 0.4.2)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
rspec (3.8.0)
rspec-core (~> 3.8.0)
rspec-expectations (~> 3.8.0)
rspec-mocks (~> 3.8.0)
rspec-core (3.8.2)
rspec-support (~> 3.8.0)
rspec-expectations (3.8.4)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
diff-lcs (>= 1.2.0, < 2.0)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
rspec-support (~> 3.8.0)
rspec-mocks (3.8.1)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
diff-lcs (>= 1.2.0, < 2.0)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
rspec-support (~> 3.8.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
rspec-parameterized (0.4.2)
binding_ninja (>= 0.2.3)
gitlab: 9.5.2 -> 9.5.5
2017-09-21 19:23:16 +01:00
parser
proc_to_ast
rspec (>= 2.13, < 4)
unparser
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
rspec-rails (3.8.2)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
actionpack (>= 3.0)
activesupport (>= 3.0)
railties (>= 3.0)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
rspec-core (~> 3.8.0)
rspec-expectations (~> 3.8.0)
rspec-mocks (~> 3.8.0)
rspec-support (~> 3.8.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
rspec-retry (0.6.1)
rspec-core (> 3.3)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
rspec-set (0.1.3)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
rspec-support (3.8.2)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
rspec_junit_formatter (0.4.1)
gitlab: 11.2.3 -> 11.3.0
2018-09-25 01:32:02 +01:00
rspec-core (>= 2, < 4, != 2.12.0)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
rspec_profiling (0.0.5)
gitlab: 8.16.6 -> 8.17.4 for CVE-2017-0882
2017-03-02 03:18:19 +00:00
activerecord
pg
rails
sqlite3
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
rubocop (0.69.0)
jaro_winkler (~> 1.5.1)
gitlab: 9.4.5 -> 9.5.2
2017-09-03 14:38:28 +01:00
parallel (~> 1.10)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
parser (>= 2.6)
gitlab: 10.3.4 -> 10.5.4
2018-03-14 13:14:03 +00:00
rainbow (>= 2.2.2, < 4.0)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
ruby-progressbar (~> 1.7)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
unicode-display_width (>= 1.4.0, < 1.7)
gitlab: 10.3.4 -> 10.5.4
2018-03-14 13:14:03 +00:00
rubocop-gitlab-security (0.1.1)
rubocop (>= 0.51)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
rubocop-performance (1.1.0)
rubocop (>= 0.67.0)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
rubocop-rspec (1.22.2)
gitlab: 10.3.4 -> 10.5.4
2018-03-14 13:14:03 +00:00
rubocop (>= 0.52.1)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
ruby-enum (0.7.2)
i18n
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
ruby-fogbugz (0.2.1)
crack (~> 0.4)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
ruby-prof (1.0.0)
ruby-progressbar (1.10.1)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
ruby-saml (1.7.2)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
nokogiri (>= 1.5.10)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
ruby_parser (3.13.1)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
sexp_processor (~> 4.9)
gitlab: 9.3.4 -> 9.4.3
2017-08-06 15:27:54 +01:00
rubyntlm (0.6.2)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
rubypants (0.2.0)
gitlab: 11.2.3 -> 11.3.0
2018-09-25 01:32:02 +01:00
rubyzip (1.2.2)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
rugged (0.28.3.1)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
safe_yaml (1.0.4)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
sanitize (4.6.6)
crass (~> 1.0.2)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
nokogiri (>= 1.4.4)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
nokogumbo (~> 1.4)
gitlab: 10.3.4 -> 10.5.4
2018-03-14 13:14:03 +00:00
sass (3.5.5)
sass-listen (~> 4.0.0)
sass-listen (4.0.0)
rb-fsevent (~> 0.9, >= 0.9.4)
rb-inotify (~> 0.9, >= 0.9.7)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
sassc (2.0.1)
ffi (~> 1.9)
rake
sassc-rails (2.1.0)
railties (>= 4.0.0)
sassc (>= 2.0)
sprockets (> 3.0)
sprockets-rails
tilt
gitlab: 8.15.4 -> 8.16.1
2017-01-24 20:28:13 +00:00
sawyer (0.8.1)
addressable (>= 2.3.5, < 2.6)
faraday (~> 0.8, < 1.0)
gitlab: 10.3.4 -> 10.5.4
2018-03-14 13:14:03 +00:00
scss_lint (0.56.0)
gitlab: 9.4.5 -> 9.5.2
2017-09-03 14:38:28 +01:00
rake (>= 0.9, < 13)
gitlab: 10.3.4 -> 10.5.4
2018-03-14 13:14:03 +00:00
sass (~> 3.5.3)
seed-fu (2.3.7)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
activerecord (>= 3.1)
activesupport (>= 3.1)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
selenium-webdriver (3.141.0)
gitlab: 10.1.1 -> 10.3.3
2018-01-07 03:59:27 +00:00
childprocess (~> 0.5)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
rubyzip (~> 1.2, >= 1.2.2)
gitlab-ce: 11.9.11 -> 11.10.4
2019-05-03 19:21:55 +01:00
sentry-raven (2.9.0)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
faraday (>= 0.7.6, < 1.0)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
settingslogic (2.0.9)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
sexp_processor (4.12.0)
shoulda-matchers (4.0.1)
activesupport (>= 4.2.0)
sidekiq (5.2.7)
gitlab: 11.3.4 -> 11.4.0
2018-10-23 11:24:11 +01:00
connection_pool (~> 2.2, >= 2.2.2)
gitlab: 11.7.5 -> 11.8.2
2019-03-16 23:52:22 +00:00
rack (>= 1.5.0)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
rack-protection (>= 1.5.0)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
redis (>= 3.3.5, < 5)
gitlab: 11.7.5 -> 11.8.2
2019-03-16 23:52:22 +00:00
sidekiq-cron (1.0.4)
fugit (~> 1.1)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
sidekiq (>= 4.2.1)
gitlab: 11.5.0 -> 11.5.1
2018-12-04 19:06:09 +00:00
signet (0.11.0)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
addressable (~> 2.3)
faraday (~> 0.9)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
jwt (>= 1.5, < 3.0)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
multi_json (~> 1.10)
gitlab: 9.5.5 -> 10.0.2
2017-09-28 19:09:31 +01:00
simple_po_parser (1.1.2)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
simplecov (0.16.1)
docile (~> 1.1)
gitlab: 8.10.6 -> 8.11.2
2016-08-26 13:08:53 +01:00
json (>= 1.8, < 3)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
simplecov-html (~> 0.10.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
simplecov-html (0.10.2)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
sixarm_ruby_unaccent (1.2.0)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
slack-notifier (1.5.1)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
snowplow-tracker (0.6.1)
contracts (~> 0.7, <= 0.11)
gitlab: 11.3.4 -> 11.4.0
2018-10-23 11:24:11 +01:00
spring (2.0.2)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
activesupport (>= 4.2)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
spring-commands-rspec (1.0.4)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
spring (>= 0.9.1)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
sprockets (3.7.2)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
concurrent-ruby (~> 1.0)
rack (> 1, < 3)
gitlab: 10.1.1 -> 10.3.3
2018-01-07 03:59:27 +00:00
sprockets-rails (3.2.1)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
actionpack (>= 4.0)
activesupport (>= 4.0)
sprockets (>= 3.0.0)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
sqlite3 (1.3.13)
gitlab: 11.8.2 -> 11.9.0
2019-03-22 23:48:02 +00:00
sshkey (2.0.0)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
stackprof (0.2.10)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
state_machines (0.5.0)
state_machines-activemodel (0.5.1)
activemodel (>= 4.1, < 6.0)
state_machines (>= 0.5.0)
state_machines-activerecord (0.5.1)
activerecord (>= 4.1, < 6.0)
state_machines-activemodel (>= 0.5.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
swd (1.1.2)
activesupport (>= 3)
attr_required (>= 0.0.5)
httpclient (>= 2.4)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
sys-filesystem (1.1.6)
ffi
gitlab: 8.11.2 -> 8.12.1
2016-09-27 14:49:21 +01:00
sysexits (1.2.0)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
temple (0.8.1)
terminal-table (1.8.0)
unicode-display_width (~> 1.1, >= 1.1.1)
gitlab: 12.3.5 -> 12.4.0 - 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
2019-10-23 21:47:24 +01:00
test-prof (0.10.0)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
text (1.3.1)
gitlab: 11.3.4 -> 11.4.0
2018-10-23 11:24:11 +01:00
thin (1.7.2)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
daemons (~> 1.0, >= 1.0.9)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
eventmachine (~> 1.0, >= 1.0.4)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
rack (>= 1, < 3)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
thor (0.19.4)
thread_safe (0.3.6)
gitlab: 11.7.5 -> 11.8.2
2019-03-16 23:52:22 +00:00
thrift (0.11.0.0)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
tilt (2.0.9)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
timecop (0.8.1)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
timfel-krb5-auth (0.8.3)
gitlab: 11.2.3 -> 11.3.0
2018-09-25 01:32:02 +01:00
toml (0.2.0)
parslet (~> 1.8.0)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
toml-rb (1.0.0)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
citrus (~> 3.0, > 3.0)
gitlab: 11.7.5 -> 11.8.2
2019-03-16 23:52:22 +00:00
truncato (0.7.11)
gitlab: 8.12.8 -> 8.13.5
2016-11-10 05:16:42 +00:00
htmlentities (~> 4.3.1)
gitlab: 11.7.5 -> 11.8.2
2019-03-16 23:52:22 +00:00
nokogiri (>= 1.7.0, <= 2.0)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
tzinfo (1.2.5)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
thread_safe (~> 0.1)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
u2f (0.2.1)
gitlab: 10.0.2 -> 10.1.1
2017-11-03 21:27:58 +00:00
uber (0.1.0)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
uglifier (2.7.2)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
execjs (>= 0.3.0)
json (>= 1.8.0)
unf (0.1.4)
unf_ext
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
unf_ext (0.0.7.5)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
unicode-display_width (1.6.0)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
unicode_utils (1.4.0)
gitlab: 11.8.2 -> 11.9.0
2019-03-22 23:48:02 +00:00
unicorn (5.4.1)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
kgio (~> 2.6)
raindrops (~> 0.7)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
unicorn-worker-killer (0.4.4)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
get_process_mem (~> 0)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
unicorn (>= 4, < 6)
gitlab: 8.10.6 -> 8.11.2
2016-08-26 13:08:53 +01:00
uniform_notifier (1.10.0)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
unleash (0.1.5)
murmurhash3 (~> 0.1.6)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
unparser (0.4.5)
gitlab: 9.5.2 -> 9.5.5
2017-09-21 19:23:16 +01:00
abstract_type (~> 0.0.7)
adamantium (~> 0.2.0)
concord (~> 0.1.5)
diff-lcs (~> 1.3)
equalizer (~> 0.0.9)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
parser (~> 2.6.3)
gitlab: 9.5.2 -> 9.5.5
2017-09-21 19:23:16 +01:00
procto (~> 0.0.2)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
validate_email (0.1.6)
activemodel (>= 3.0)
mail (>= 2.2.5)
validate_url (1.0.8)
activemodel (>= 3.0.0)
public_suffix
gitlab: 8.16.6 -> 8.17.4 for CVE-2017-0882
2017-03-02 03:18:19 +00:00
validates_hostname (1.0.6)
activerecord (>= 3.0)
activesupport (>= 3.0)
gitlab: 11.8.2 -> 11.9.0
2019-03-22 23:48:02 +00:00
version_sorter (2.2.4)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
virtus (1.0.5)
axiom-types (~> 0.1)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
coercible (~> 1.0)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
descendants_tracker (~> 0.0, >= 0.0.3)
equalizer (~> 0.0, >= 0.0.9)
gitlab: 8.15.4 -> 8.16.1
2017-01-24 20:28:13 +00:00
vmstat (2.3.0)
gitlab: 12.3.5 -> 12.4.0 - 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
2019-10-23 21:47:24 +01:00
warden (1.2.8)
rack (>= 2.0.6)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
webfinger (1.1.0)
activesupport
httpclient (>= 2.4)
gitlab: 11.8.2 -> 11.9.0
2019-03-22 23:48:02 +00:00
webmock (3.5.1)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
addressable (>= 2.3.6)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
crack (>= 0.3.2)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
hashdiff
gitlab: 11.3.4 -> 11.4.0
2018-10-23 11:24:11 +01:00
webpack-rails (0.9.11)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
railties (>= 3.2.0)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
websocket-driver (0.7.0)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
websocket-extensions (>= 0.1.0)
websocket-extensions (0.1.3)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
wikicloth (0.8.1)
builder
expression_parser
rinku
gitlab: 10.1.1 -> 10.3.3
2018-01-07 03:59:27 +00:00
with_env (1.1.0)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
xml-simple (1.1.5)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
xpath (3.2.0)
nokogiri (~> 1.8)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
PLATFORMS
ruby
DEPENDENCIES
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
RedCloth (~> 4.3.2)
gitlab: 8.10.6 -> 8.11.2
2016-08-26 13:08:53 +01:00
ace-rails-ap (~> 4.1.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
acme-client (~> 2.0.2)
activerecord-explain-analyze (~> 0.1)
gitlab-ce: 11.9.11 -> 11.10.4
2019-05-03 19:21:55 +01:00
acts-as-taggable-on (~> 6.0)
gitlab: 10.0.2 -> 10.1.1
2017-11-03 21:27:58 +00:00
addressable (~> 2.5.2)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
akismet (~> 2.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
apollo_upload_server (~> 2.0.0.beta3)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
asana (~> 0.8.1)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
asciidoctor (~> 2.0.10)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
asciidoctor-include-ext (~> 0.3.1)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
asciidoctor-plantuml (= 0.0.9)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
atlassian-jwt (~> 0.2.0)
gitlab: 10.7.0 -> 10.8.0
2018-05-23 21:23:48 +01:00
attr_encrypted (~> 3.1.0)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
awesome_print
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
aws-sdk
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
babosa (~> 1.0.2)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
base32 (~> 0.3.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
batch-loader (~> 1.4.0)
gitlab: 9.4.5 -> 9.5.2
2017-09-03 14:38:28 +01:00
bcrypt_pbkdf (~> 1.0)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
benchmark-ips (~> 2.3.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
benchmark-memory (~> 0.1)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
better_errors (~> 2.5.0)
binding_of_caller (~> 0.8.0)
gitlab: 11.8.2 -> 11.9.0
2019-03-22 23:48:02 +00:00
bootsnap (~> 1.4)
gitlab-ce: 11.9.11 -> 11.10.4
2019-05-03 19:21:55 +01:00
bootstrap_form (~> 4.2.0)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
brakeman (~> 4.2)
gitlab: 11.2.3 -> 11.3.0
2018-09-25 01:32:02 +01:00
browser (~> 2.5)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
bullet (~> 5.5.0)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
bundler-audit (~> 0.5.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
capybara (~> 3.22.0)
capybara-screenshot (~> 1.0.22)
gitlab: 11.6.3 -> 11.7.4
2019-02-05 19:40:41 +00:00
carrierwave (~> 1.3)
gitlab: 9.5.5 -> 10.0.2
2017-09-28 19:09:31 +01:00
charlock_holmes (~> 0.7.5)
gitlab: 8.10.6 -> 8.11.2
2016-08-26 13:08:53 +01:00
chronic (~> 0.10.2)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
commonmarker (~> 0.17)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
concurrent-ruby (~> 1.1)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
connection_pool (~> 2.0)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
countries (~> 3.0)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
creole (~> 0.5.0)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
danger (~> 6.0)
gitlab: 11.6.3 -> 11.7.4
2019-02-05 19:40:41 +00:00
database_cleaner (~> 1.7.0)
gitlab: 11.7.5 -> 11.8.2
2019-03-16 23:52:22 +00:00
deckar01-task_list (= 2.2.0)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
default_value_for (~> 3.2.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
derailed_benchmarks
gitlab: 10.7.0 -> 10.8.0
2018-05-23 21:23:48 +01:00
device_detector
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
devise (~> 4.6)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
devise-two-factor (~> 3.0.0)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
diffy (~> 3.1.0)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
discordrb-webhooks-blackst0ne (~> 3.3)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
doorkeeper (~> 4.3)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
doorkeeper-openid_connect (~> 1.5)
ed25519 (~> 1.2)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
elasticsearch-api (= 5.0.3)
elasticsearch-model (~> 0.1.9)
elasticsearch-rails (~> 0.1.9)
gitlab: 8.15.4 -> 8.16.1
2017-01-24 20:28:13 +00:00
email_reply_trimmer (~> 0.1)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
email_spec (~> 2.2.0)
gitlab: 11.5.0 -> 11.5.1
2018-12-04 19:06:09 +00:00
escape_utils (~> 1.1)
gitlab: 12.3.5 -> 12.4.0 - 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
2019-10-23 21:47:24 +01:00
factory_bot_rails (~> 5.1.0)
gitlab: 9.3.4 -> 9.4.3
2017-08-06 15:27:54 +01:00
faraday (~> 0.12)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
faraday_middleware-aws-signers-v4
gitlab: 10.3.4 -> 10.5.4
2018-03-14 13:14:03 +00:00
fast_blank
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
ffaker (~> 2.10)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
flipper (~> 0.13.0)
flipper-active_record (~> 0.13.0)
flipper-active_support_cache_store (~> 0.13.0)
gitlab: 11.5.0 -> 11.5.1
2018-12-04 19:06:09 +00:00
flowdock (~> 0.7)
gitlab: 11.8.2 -> 11.9.0
2019-03-22 23:48:02 +00:00
fog-aliyun (~> 0.3)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
fog-aws (~> 3.5)
gitlab: 11.8.2 -> 11.9.0
2019-03-22 23:48:02 +00:00
fog-core (= 2.1.0)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
fog-google (~> 1.9)
gitlab: 11.8.2 -> 11.9.0
2019-03-22 23:48:02 +00:00
fog-local (~> 0.6)
fog-openstack (~> 1.0)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
fog-rackspace (~> 0.1.1)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
font-awesome-rails (~> 4.7)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
foreman (~> 0.84.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
fugit (~> 1.2.1)
gitlab: 9.4.5 -> 9.5.2
2017-09-03 14:38:28 +01:00
fuubar (~> 2.2.0)
gitlab: 9.5.2 -> 9.5.5
2017-09-21 19:23:16 +01:00
gemojione (~> 3.3)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
gettext (~> 3.2.2)
gettext_i18n_rails (~> 1.8.0)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
gettext_i18n_rails_js (~> 1.3)
gitlab: 12.3.5 -> 12.4.0 - 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
2019-10-23 21:47:24 +01:00
gitaly (~> 1.65.0)
gitlab: 11.3.4 -> 11.4.0
2018-10-23 11:24:11 +01:00
github-markup (~> 1.7.0)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
gitlab-labkit (~> 0.5)
gitlab-license (~> 1.0)
gitlab-ce: 11.9.11 -> 11.10.4
2019-05-03 19:21:55 +01:00
gitlab-markup (~> 1.7.0)
gitlab: 12.3.5 -> 12.4.0 - 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
2019-10-23 21:47:24 +01:00
gitlab-net-dns (~> 0.9.1)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
gitlab-peek (~> 0.0.1)
gitlab-sidekiq-fetcher (= 0.5.2)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
gitlab-styles (~> 2.7)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
gitlab_chronic_duration (~> 0.10.6.1)
gitlab: 11.8.2 -> 11.9.0
2019-03-22 23:48:02 +00:00
gitlab_omniauth-ldap (~> 2.1.1)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
gon (~> 6.2)
gitlab: 11.2.3 -> 11.3.0
2018-09-25 01:32:02 +01:00
google-api-client (~> 0.23)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
google-protobuf (~> 3.7.1)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
gpgme (~> 2.0.18)
grape (~> 1.1.0)
gitlab: 10.7.0 -> 10.8.0
2018-05-23 21:23:48 +01:00
grape-entity (~> 0.7.1)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
grape-path-helpers (~> 1.1)
gitlab: 9.5.5 -> 10.0.2
2017-09-28 19:09:31 +01:00
grape_logging (~> 1.7)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
graphiql-rails (~> 1.4.10)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
graphql (~> 1.9.11)
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
graphql-docs (~> 1.6.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
grpc (~> 1.19.0)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
gssapi
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
haml_lint (~> 0.31.0)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
hamlit (~> 2.8.8)
hangouts-chat (~> 0.0.5)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
hashie-forbidden_attributes
health_check (~> 2.6.0)
gitlab-ce: 11.9.1 -> 11.9.8
2019-04-22 22:40:40 +01:00
hipchat (~> 1.5.0)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
html-pipeline (~> 2.8)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
html2text
gitlab-ce: 11.9.11 -> 11.10.4
2019-05-03 19:21:55 +01:00
httparty (~> 0.16.4)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
icalendar
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
influxdb (~> 0.2)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
invisible_captcha (~> 0.12.1)
jira-ruby (~> 1.7)
gitlab: 11.7.5 -> 11.8.2
2019-03-16 23:52:22 +00:00
js_regex (~> 3.1)
gitlab: 10.0.2 -> 10.1.1
2017-11-03 21:27:58 +00:00
json-schema (~> 2.8.0)
gitlab: 11.6.3 -> 11.7.4
2019-02-05 19:40:41 +00:00
jwt (~> 2.1.0)
gitlab: 9.4.5 -> 9.5.2
2017-09-03 14:38:28 +01:00
kaminari (~> 1.0)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
knapsack (~> 1.17)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
kubeclient (~> 4.4.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
letter_opener_web (~> 1.3.4)
gitlab: 11.2.3 -> 11.3.0
2018-09-25 01:32:02 +01:00
license_finder (~> 5.4)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
licensee (~> 8.9)
gitlab: 9.4.5 -> 9.5.2
2017-09-03 14:38:28 +01:00
lograge (~> 0.5)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
loofah (~> 2.2)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
mail_room (~> 0.9.1)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
memory_profiler (~> 0.9)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
method_source (~> 0.8)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
mimemagic (~> 0.3.2)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
mini_magick
gitlab: 11.6.3 -> 11.7.4
2019-02-05 19:40:41 +00:00
minitest (~> 5.11.0)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
nakayoshi_fork (~> 0.0.4)
gitlab: 9.3.4 -> 9.4.3
2017-08-06 15:27:54 +01:00
net-ldap
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
net-ntp
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
net-ssh (~> 5.2)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
nokogiri (~> 1.10.4)
gitlab: 9.3.4 -> 9.4.3
2017-08-06 15:27:54 +01:00
oauth2 (~> 1.4)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
octokit (~> 4.9)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
omniauth (~> 1.8)
gitlab: 10.5.4 -> 10.5.6
2018-03-22 01:08:49 +00:00
omniauth-auth0 (~> 2.0.0)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
omniauth-authentiq (~> 0.3.3)
gitlab: 10.0.2 -> 10.1.1
2017-11-03 21:27:58 +00:00
omniauth-azure-oauth2 (~> 0.0.9)
gitlab: 9.5.2 -> 9.5.5
2017-09-21 19:23:16 +01:00
omniauth-cas3 (~> 1.1.4)
gitlab: 8.11.2 -> 8.12.1
2016-09-27 14:49:21 +01:00
omniauth-facebook (~> 4.0.0)
gitlab: 10.7.0 -> 10.8.0
2018-05-23 21:23:48 +01:00
omniauth-github (~> 1.3)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
omniauth-gitlab (~> 1.0.2)
gitlab: 11.6.3 -> 11.7.4
2019-02-05 19:40:41 +00:00
omniauth-google-oauth2 (~> 0.6.0)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
omniauth-kerberos (~> 0.3.0)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
omniauth-oauth2-generic (~> 0.2.2)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
omniauth-salesforce (~> 1.0.5)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
omniauth-saml (~> 1.10)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
omniauth-shibboleth (~> 1.3.0)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
omniauth-twitter (~> 1.4)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
omniauth-ultraauth (~> 0.0.2)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
omniauth_crowd (~> 2.2.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
omniauth_openid_connect (~> 0.3.1)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
org-ruby (~> 0.9.12)
gitlab: 11.7.5 -> 11.8.2
2019-03-16 23:52:22 +00:00
pg (~> 1.1)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
premailer-rails (~> 1.9.7)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
prometheus-client-mmap (~> 0.9.10)
gitlab: 11.6.3 -> 11.7.4
2019-02-05 19:40:41 +00:00
pry-byebug (~> 3.5.1)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
pry-rails (~> 0.3.4)
gitlab: 11.5.0 -> 11.5.1
2018-12-04 19:06:09 +00:00
puma (~> 3.12)
puma_worker_killer
gitlab-ce: 11.9.11 -> 11.10.4
2019-05-03 19:21:55 +01:00
rack (~> 2.0.7)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
rack-attack (~> 4.4.1)
gitlab: 10.3.4 -> 10.5.4
2018-03-14 13:14:03 +00:00
rack-cors (~> 1.0.0)
gitlab-ce: 11.9.11 -> 11.10.4
2019-05-03 19:21:55 +01:00
rack-oauth2 (~> 1.9.3)
gitlab: 8.16.6 -> 8.17.4 for CVE-2017-0882
2017-03-02 03:18:19 +00:00
rack-proxy (~> 0.6.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
rack-timeout
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
rails (= 5.2.3)
gitlab-ce: 11.5.5 -> 11.6.0
2018-12-24 02:32:18 +00:00
rails-controller-testing
rails-i18n (~> 5.1)
gitlab: 11.2.3 -> 11.3.0
2018-09-25 01:32:02 +01:00
rainbow (~> 3.0)
gitlab: 9.3.4 -> 9.4.3
2017-08-06 15:27:54 +01:00
raindrops (~> 0.18)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
rblineprof (~> 0.3.6)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
rbtrace (~> 0.4)
rdoc (~> 6.0)
gitlab: 9.4.5 -> 9.5.2
2017-09-03 14:38:28 +01:00
re2 (~> 1.1.1)
gitlab-ce: 11.9.11 -> 11.10.4
2019-05-03 19:21:55 +01:00
recaptcha (~> 4.11)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
redis (~> 4.0)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
redis-namespace (~> 1.6.0)
gitlab: 10.1.1 -> 10.3.3
2018-01-07 03:59:27 +00:00
redis-rails (~> 5.0.2)
gitlab: 8.12.8 -> 8.13.5
2016-11-10 05:16:42 +00:00
request_store (~> 1.3)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
responders (~> 2.0)
gitlab: 12.3.5 -> 12.4.0 - 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
2019-10-23 21:47:24 +01:00
rouge (~> 3.11.0)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
rqrcode-rails3 (~> 0.1.7)
gitlab: 9.5.2 -> 9.5.5
2017-09-21 19:23:16 +01:00
rspec-parameterized
gitlab-ce: 12.0.3 -> 12.1.6
2019-08-14 13:51:00 +01:00
rspec-rails (~> 3.8.0)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
rspec-retry (~> 0.6.1)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
rspec-set (~> 0.1.3)
gitlab: 11.2.3 -> 11.3.0
2018-09-25 01:32:02 +01:00
rspec_junit_formatter
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
rspec_profiling (~> 0.0.5)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
rubocop (~> 0.69.0)
rubocop-performance (~> 1.1.0)
gitlab: 10.3.4 -> 10.5.4
2018-03-14 13:14:03 +00:00
rubocop-rspec (~> 1.22.1)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
ruby-fogbugz (~> 0.2.1)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
ruby-prof (~> 1.0.0)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
ruby-progressbar
gitlab: 9.3.4 -> 9.4.3
2017-08-06 15:27:54 +01:00
ruby_parser (~> 3.8)
gitlab: 11.6.3 -> 11.7.4
2019-02-05 19:40:41 +00:00
rubyzip (~> 1.2.2)
gitlab: 11.8.2 -> 11.9.0
2019-03-22 23:48:02 +00:00
rugged (~> 0.28)
gitlab: 10.8.0 -> 11.2.3
2018-09-21 08:37:51 +01:00
sanitize (~> 4.6)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
sassc-rails (~> 2.1.0)
gitlab: 10.3.4 -> 10.5.4
2018-03-14 13:14:03 +00:00
scss_lint (~> 0.56.0)
seed-fu (~> 2.3.7)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
selenium-webdriver (~> 3.141)
sentry-raven (~> 2.9)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
settingslogic (~> 2.0.9)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
shoulda-matchers (~> 4.0.1)
sidekiq (~> 5.2.7)
gitlab: 11.7.5 -> 11.8.2
2019-03-16 23:52:22 +00:00
sidekiq-cron (~> 1.0)
gitlab: 9.5.5 -> 10.0.2
2017-09-28 19:09:31 +01:00
simple_po_parser (~> 1.1.2)
gitlab: 11.10.8 -> 12.0.3 This is a major version bump but things were generally straightforward save two wrinkles: * it is necessary to ignore collisions in the gitlab bundler environment as both `omniauth_oauth2_generic` and `apollo_upload_server` provide a `console` executable. * grpc had to be patched since its build system expects the `AR` environment variable to contain not just the path to `ar` but also the `rpc` flags (see the discussion in nixpkgs #63056).
2019-07-10 01:09:15 +01:00
simplecov (~> 0.16.1)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
slack-notifier (~> 1.5.1)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
snowplow-tracker (~> 0.6.1)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
spring (~> 2.0.0)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
spring-commands-rspec (~> 1.0.4)
gitlab: 8.12.8 -> 8.13.5
2016-11-10 05:16:42 +00:00
sprockets (~> 3.7.0)
gitlab: 11.8.2 -> 11.9.0
2019-03-22 23:48:02 +00:00
sshkey (~> 2.0)
gitlab: 8.13.5 -> 8.15.4
2017-01-15 16:06:39 +00:00
stackprof (~> 0.2.10)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
state_machines-activerecord (~> 0.5.1)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
sys-filesystem (~> 1.1.6)
gitlab: 12.3.5 -> 12.4.0 - 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
2019-10-23 21:47:24 +01:00
test-prof (~> 0.10.0)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
thin (~> 1.7.0)
gitlab: 8.11.2 -> 8.12.1
2016-09-27 14:49:21 +01:00
timecop (~> 0.8.0)
gitlab: 10.5.6 -> 10.7.0
2018-04-25 18:57:10 +01:00
toml-rb (~> 1.0.0)
gitlab: 11.7.5 -> 11.8.2
2019-03-16 23:52:22 +00:00
truncato (~> 0.7.11)
gitlab: 8.5.12 -> 8.10.3, update module Fixes #14795.
2016-08-03 17:49:18 +01:00
u2f (~> 0.2.1)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
uglifier (~> 2.7.2)
gitlab: 7.4.2 -> 8.0.5
2015-10-21 18:48:56 +01:00
unf (~> 0.1.4)
gitlab: 11.8.2 -> 11.9.0
2019-03-22 23:48:02 +00:00
unicorn (~> 5.4.1)
gitlab: 8.12.8 -> 8.13.5
2016-11-10 05:16:42 +00:00
unicorn-worker-killer (~> 0.4.4)
gitlab: 12.1.6 -> 12.3.4 - Update GitLab to 12.3.4 - Update update.py to cope with the new upstream repository structure - Refactor gitlab-shell to use buildGoPackage and bundlerEnv for dependencies - Refactor gitlab-workhorse to use buildGoPackage for dependencies - Make update.py able to update gitlab-shell and gitlab-workhorse dependencies - Various fixes necessary for update to work
2019-10-01 14:38:22 +01:00
unleash (~> 0.1.5)
gitlab: 8.16.6 -> 8.17.4 for CVE-2017-0882
2017-03-02 03:18:19 +00:00
validates_hostname (~> 1.0.6)
gitlab: 11.8.2 -> 11.9.0
2019-03-22 23:48:02 +00:00
version_sorter (~> 2.2.4)
gitlab: 8.15.4 -> 8.16.1
2017-01-24 20:28:13 +00:00
vmstat (~> 2.3.0)
gitlab: 11.8.2 -> 11.9.0
2019-03-22 23:48:02 +00:00
webmock (~> 3.5.1)
gitlab: 8.17.6 -> 9.3.4
2017-07-05 22:53:31 +01:00
webpack-rails (~> 0.9.10)
nixos: Add gitlab and gitlab-shell I had to make several adjustments to make it work with nixos: * Replace relative config file lookups with ENV variable. * Modify gitlab-shell to not clear then environment when running pre-receive. * Modify gitlab-shell to write some environment variables into the .authorized_keys file to make sure gitlab-shell reads the correct config file. * Log unicorn output to syslog. I tried various ways of adding a syslog package but the bundler would not pick them up. Please fix in a better way if possible. * Gitlab-runner program wrapper. This is useful to run e.g. backups etc. with the correct environment set up.
2014-10-25 17:22:49 +01:00
wikicloth (= 0.8.1)
gitlab: 8.0.5 -> 8.5.0, service improvements Updates gitlab to the current stable version and fixes a lot of features that were broken, at least with the current version and our configuration. Quite a lot of sweat and tears has gone into testing nearly all features and reading/patching the Gitlab source as we're about to deploy gitlab for our whole company. Things to note: * The gitlab config is now written as a nix attribute set and will be converted to JSON. Gitlab uses YAML but JSON is a subset of YAML. The `extraConfig` opition is also an attribute set that will be merged with the default config. This way *all* Gitlab options are supported. * Some paths like uploads and configs are hardcoded in rails (at least after my study of the Gitlab source). This is why they are linked from the Gitlab root to /run/gitlab and then linked to the configurable `statePath`. * Backup & restore should work out of the box from another Gitlab instance. * gitlab-git-http-server has been replaced by gitlab-workhorse upstream. Push & pull over HTTPS works perfectly. Communication to gitlab is done over unix sockets. An HTTP server is required to proxy requests to gitlab-workhorse over another unix socket at `/run/gitlab/gitlab-workhorse.socket`. * The user & group running gitlab are now configurable. These can even be changed for live instances. * The initial email address & password of the root user can be configured. Fixes #8598.
2016-01-30 13:47:04 +00:00
BUNDLED WITH
gitlab: 11.6.3 -> 11.7.4
2019-02-05 19:40:41 +00:00
1.17.3
Reference in New Issue Copy Permalink