Age | Commit message (Collapse) | Author |
|
Update fugit which fixes a potential infinite loop
Closes #59273
See merge request gitlab-org/gitlab-ce!26579
|
|
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.
|
|
Bump Rugged to 0.28.1
See merge request gitlab-org/gitlab-ce!26595
|
|
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
|
|
Bump httparty to version 1.16.4
Closes #44342
See merge request gitlab-org/gitlab-ce!25893
|
|
Send schema cache to Sentry on MissingAttributeError
See merge request gitlab-org/gitlab-ce!26331
|
|
Signed-off-by: Dmitriy 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: Rémy Coutable <remy@rymai.me>
|
|
Update recaptcha gem from 3.x to 4.11
See merge request gitlab-org/gitlab-ce!25921
|
|
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.
|
|
Allow raw `tls_options` to be passed in LDAP configuration
Closes #46391
See merge request gitlab-org/gitlab-ce!20678
|
|
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.
|
|
Bump version_sorter to version 2.2.4
See merge request gitlab-org/gitlab-ce!25487
|
|
Signed-off-by: Dmitriy 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
|
|
|
|
Send project name with Gitaly repository requests
Closes gitaly#1394
See merge request gitlab-org/gitlab-ce!23373
|
|
Upgrade gitaly-proto to 1.10.0 to have this field.
|
|
update js_regex 2.2.1 -> 3.1
See merge request gitlab-org/gitlab-ce!24433
|
|
This engine was replaced with CommonMarker in 11.4, it was deprecated
since then.
|
|
'19745-forms-with-task-lists-can-be-overwritten-when-editing-simultaneously' into 'master'
Forms with task lists can be overwritten when editing simultaneously
See merge request gitlab-org/gitlab-ce!23938
|
|
RubyZip allows us to perform strong validation of
expanded paths where we do extract file.
We introduce the following additional checks
to extract routines:
1. None of path components can be symlinked,
2. We drop privileges support for directories,
3. Symlink source needs to point within the target directory,
like `public/`,
4. The symlink source needs to exist ahead of time.
|
|
v2.1.0 was published wrongly by the package author.
|
|
|
|
|
|
This reduces duplication caused by gitlab-monitor already shipping
Sidekiq 5.2.5. The only changes appear to be minor:
https://github.com/mperham/sidekiq/blob/master/Changes.md
|
|
http_max_redirects was introduced in 4.2.2, so upgrade kubeclient.
The monkey-patch was global so we will have to check that all instances
of Kubeclient::Client are handled.
Spec all methods of KubeClient
This should provide better confidence that we are indeed disallowing
redirection in all cases
|
|
This change renames a dependency and fixes a minor bug, but this upgrade
is happening because Gitaly will be receiving rbtrace as a dependency.
|
|
Markdown footnotes not working
Closes #26375
See merge request gitlab-org/gitlab-ce!24168
|
|
|
|
This change will instantiate an OpenTracing tracer and configure it
as the global tracer when the GITLAB_TRACING environment variable is
configured. GITLAB_TRACING takes a "connection string"-like value,
encapsulating the driver (eg jaeger, etc) and options for the driver.
Since each service, whether it's written in Ruby or Golang, uses the
same connection-string, it should be very easy to configure all
services in a cluster, or even a single development machine to be
setup to use tracing.
Note that this change does not include instrumentation or propagation
changes as this is a way of breaking a previous larger change into
components. The instrumentation and propagation changes will follow
in separate changes.
|