Age | Commit message (Collapse) | Author |
|
Fix failing static-analysis pipeline
Closes #46859
See merge request gitlab-org/gitlab-ce!19174
|
|
Bump rugged to 0.27.1 for security fixes
See merge request gitlab-org/gitlab-ce!19222
|
|
|
|
Bump prometheus-client-mmap to 0.9.3 to fix nil exception error
See merge request gitlab-org/gitlab-ce!19085
|
|
|
|
Update grape-entity 0.6.0 -> 0.7.1
See merge request gitlab-org/gitlab-ce!18720
|
|
|
|
|
|
|
|
|
|
|
|
Ports omniauth-jwt gem onto GitLab OmniAuth Strategies suite
See merge request gitlab-org/gitlab-ce!18580
|
|
|
|
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
Bump lograge to 0.10.0 and remove monkey patch
See merge request gitlab-org/gitlab-ce!18551
|
|
lograge 0.10.0 contains the `Location` query string fix in
https://github.com/roidrage/lograge/pull/241 among other minor changes:
https://github.com/roidrage/lograge/blob/master/CHANGELOG.md
|
|
https://gitlab.com/gitlab-org/gitlab-ce/issues/45433
and
https://github.com/doorkeeper-gem/doorkeeper/issues/1065
|
|
|
|
Revert the addition of goldiloader
See merge request gitlab-org/gitlab-ce!18458
|
|
|
|
This reverts the addition of the "goldiloader" Gem and all use of it.
While this Gem is very promising it's causing a variety of problems on
GitLab.com due to it eager-loading too much data in places where we
don't expect/can handle this. At least for the time being this means we
have to go back to manually fixing N+1 query problems, but at least
those should not cause a negative impact on availability.
|
|
This reverts merge request !18399
|
|
|
|
Fix a case with empty secret CI/CD variables
Closes #31929
See merge request gitlab-org/gitlab-ce!18400
|
|
Update faraday_middleware to 0.12.2
Closes #45397
See merge request gitlab-org/gitlab-ce!18397
|
|
|
|
|
|
|
|
|
|
Goldiloader (https://github.com/salsify/goldiloader) can eager load
associations automatically. This removes the need for adding "includes"
calls in a variety of different places. This also comes with the added
benefit of not having to eager load data if it's not used.
|
|
1. Synchronize used version of `parser` gem for both versions of rails: 4 and 5.
2. Fix broken CI pipelines for rails5 branches.
The 2.5.0.4 version is removed from rubygems, so it's skipped.
https://github.com/whitequark/parser/issues/478
|
|
git 2.16 will fail badly if there are stale worktrees.
Closes #44115
|
|
Update brakeman to 4.2.1
Closes #44878
See merge request gitlab-org/gitlab-ce!18122
|
|
|
|
|
|
Update charlock_holmes to 0.76
See merge request gitlab-org/gitlab-ce!18103
|
|
Didn't compile against newer icu4c versions and was fixed upstream in
https://github.com/brianmario/charlock_holmes/pull/129, which was
releaed in the versions its now locked to.
|
|
Release notes: https://github.com/libgit2/libgit2/releases/tag/v0.27.0
This version solves a significant performance issue with generating
large diffs: https://github.com/libgit2/libgit2/issues/4460
|
|
|
|
Test if remote repository exists before cloning
Closes #43929 and gitaly#1084
See merge request gitlab-org/gitlab-ce!18017
|
|
Update asciidoctor to 1.5.6.2 and asciidoctor-plantuml to 0.0.8
Closes #44712
See merge request gitlab-org/gitlab-ce!18022
|
|
LFS direct upload port to CE
Closes #44548
See merge request gitlab-org/gitlab-ce!17752
|
|
|
|
|
|
When a repository does not exist on a remote, Gitaly won't be able to
clone it. This is correct behaviour, but from the clients perspective a
change in behaviour.
This change implements the client side changes that allows Gitaly to
execute a `git ls-remote <remote-url> HEAD`. This way the client has no
need to shell out to Git.
In the situation where multiple Gitalies are available, one is chosen at
random.
This commit closes https://gitlab.com/gitlab-org/gitlab-ce/issues/43929,
while its also a part of https://gitlab.com/gitlab-org/gitaly/issues/1084
|
|
Resolve "Add support for omniauth-jwt provider"
Closes #43512
See merge request gitlab-org/gitlab-ce!17774
|
|
|
|
Update omniauth-twitter 1.2.0 -> 1.4
See merge request gitlab-org/gitlab-ce!17876
|
|
|
|
|