These upgrades are necessary to support Ruby 2.6.

This matches the Gitaly MR:
https://gitlab.com/gitlab-org/gitaly/merge_requests/1066

This pulls in a fix for libxslt that addresses CVE-2019-11068:
https://github.com/sparklemotion/nokogiri/releases

This change is a fairly straightforward refactor to extract the tracing
and correlation-id code from the gitlab rails codebase into the new
LabKit-Ruby project.

The corresponding import into LabKit-Ruby was in
https://gitlab.com/gitlab-org/labkit-ruby/merge_requests/1

The code itself remains very similar for now.

Extracting it allows us to reuse it in other projects, such as
Gitaly-Ruby. This will give us the advantages of correlation-ids and
distributed tracing in that project too.

Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Signed-off-by: NRémy Coutable <remy@rymai.me>

This reverts commit a5378665.

This update has two important fixes:

1. It reverts the monkey patch introduced in
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/23385 since
https://github.com/rack/rack/pull/1201 is now part of the release.

2. Preserve forwarded IP address for trusted proxy chains
(https://github.com/rack/rack/pull/1343).

This fixes a number of issues as described in
https://weblog.rubyonrails.org/releases/.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/58963

Add `GetArchiveRequest` to git-archive params.

Modifies `Git::Repository#archive_metadata` to append `path`
to `ArchivePrefix` so it'll not hit the cache of repository archive
when it already exists.

The new version requires `python3` to be available. In omnibus
installation this is already a reality as we are currently pathing
previous `gitlab-markup` version to use `python3` instead of `python2`.

We are now requiring `python3` with the gem without having to patch it.

As a consequence to also make it easy to use it in development, we've
introduced a `Pipfile` and `Pipfile.lock`, working similarly to
`Gemfile` and `Gemfile.lock`, and added documentation on how to use
them.

This resolves a minor link issue in libgit2 with deprecated functions:
https://github.com/libgit2/libgit2/releases

This coincides with the Gitaly bump:
https://gitlab.com/gitlab-org/gitaly/merge_requests/1154

- Also remove boostrap 4 migration adapter

This keeps the version used by gitlab-monitor and GitLab CE
consistent. This release also adds Ruby 2.6 support and PostgreSQL 11
error codes:

https://github.com/ged/ruby-pg/blob/master/History.rdoc

Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

We don't know why this happens, so this is an attempt to debug the
issue by sending a full list of all columns ActiveRecord knows about
when the error is raised.

This version bump makes things consistent between Gitaly and
fixes a significant number of bugs:
https://github.com/libgit2/libgit2/releases

This also decreases disk space of Omnibus builds by ~30 MB.

There is also a workaround for
https://github.com/libgit2/rugged/issues/785. If Gitaly or another
process changes .gitconfig while Rugged has the file loaded,
Rugged::Repository#each_key will report stale values unless a lookup is
done first.

This bug only manifests in a spec because we are using both Gitaly and
Rugged at the same time there, and we normally don't use Rugged in the
CE/EE code in this way.

Signed-off-by: NRémy Coutable <remy@rymai.me>

Remove references to the vendored copies of At.js and jquery.carat
as well as the legacy rails wrapper gem.

In recaptcha 4.0.0 there was an API change:

 - `public_key` -> `site_key`
 - `private_key` -> secret_key

See:
https://github.com/ambethia/recaptcha/blob/master/CHANGELOG.md

This reverts merge request !17871

When `force` is set to `true` and `start_branch` is set, the
branch will be ovewritten with the new commit based on the
`HEAD` of the `start_branch`.

This commit includes changes to update the `gitaly-proto` gem.

We've previously exposed ca_file and ssl_version but there are many
possible options that can be used inside tls_options. Instead of
exposing individual ones, simply expose the entire hash so it can
be passed in and we won't have to add things in the future.

1.4.1 contains a number of bug fixes and performance improvements:
https://github.com/Shopify/bootsnap/blob/master/CHANGELOG.md

Fixes issue with AWS V4 signatures not working with Ceph S3:
https://github.com/fog/fog-aws/issues/462

Adds the ground work for writing into
the merge ref refs/merge-requests/:iid/merge the
merge result between source and target branches of
a MR, without further side-effects such as
mailing, MR updates and target branch changes.

Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Webmock 3.5.0 brings Ruby 2.6 support.

Unicorn 5.3.1 fixes a GC issue that causes a crash, and Unicorn 5.4.1
quiets some warnings for Ruby 2.6. More details:

https://github.com/defunkt/unicorn/releases

This release fixes a bug in handling certain ed25519 keys. For more
details, see this GitHub issue:

https://github.com/bensie/sshkey/issues/34