Don't allow Ruby 3 build to fail

See merge request !93

Relax redis gem version to allow for v5

See merge request gitlab-org/labkit-ruby!92

The newly-released v5 gem contains a much more efficient Ruby
implementation (gitlab-org/gitlab#367857 (comment 1058650756)),
as well as a solid hiredis implementation.

Changelog: changed

Support ActionPack and ActiveSupport 7.x

See merge request gitlab-org/labkit-ruby!91

This is needed for Rails 7 compatibility

Add tools for checking and enabling FIPS mode

See merge request gitlab-org/labkit-ruby!90

The code needed for checking whether FIPS is enabled and to use
OpenSSL's implementation of hash algorithms instead of Ruby's will be
needed by any Ruby GitLab project. This code was extracted from the
main GitLab Rails app.

Relates to https://gitlab.com/gitlab-org/gitlab/-/issues/360174

Update gitlab-dangerfiles to 2.11.0

See merge request gitlab-org/labkit-ruby!89

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

Don't enforce logged keys to be known by Labkit

See merge request gitlab-org/labkit-ruby!88

It would be handy if all projects used the same keys to log data,
which is why I initially added this list, but having to modify all of
the projects each time would become cumbersome to keep it in sync will
become cumbersome.

So this changes that all keys are allowed: when passing them in
through Labkit, a meta. prefix is added (for logs). These will be
propagated by Labkit when found in Sidekiq jobs.

Now we need to pay attention in the other projects that will push into
a context that they use the same format. But having duplicate
information logged in different fields is likely better than losing
information.

Update gitlab-dangerfiles to 2.6

See merge request gitlab-org/labkit-ruby!86

Pin jaeger-client to 1.1.x

See merge request gitlab-org/labkit-ruby!87

Require grpc 1.37 or newer

See merge request gitlab-org/labkit-ruby!85

This changes the version pin on grpc to merely
require the last known version we know to work
well.

This fix in c7d5d95d
did not have the desired effect since ~>1.30 resolves
to ~>1.30.+ which still does not allow us to go
to version 1.4x.x.

This change should address that problem.

Relax Sidekiq version

See merge request gitlab-org/labkit-ruby!84

We now use Sidekiq 6 in production, but Sidekiq 5 is fine.

This allows us to ship only one version in Omnibus.

Add Danger, add myself to CODEOWNERS

See merge request gitlab-org/labkit-ruby!83

Adding CONTRIBUTING.md after license audit review

See merge request gitlab-org/labkit-ruby!80

Relax grpc version pin to 1.3x

See merge request gitlab-org/labkit-ruby!82

Pinning this at the patch level make it impossible
to experiment with grpc upgrades in repositories that
depend on labkit.

Update Ruby to 2.7.4

See merge request gitlab-org/labkit-ruby!79

Downgrade grpc + tools to 1.30.2

See merge request gitlab-org/labkit-ruby!81

Matthias Käppler authored 3 years ago and Bob Van Landuyt committed 3 years ago

It was causing problems on older CPU architectures due to
new instructions being used in the shared library.

See gitlab-org/gitlab#339138

Recent audit of project licenses determined that CONTRIBUTING.md was missing for this project and should be applied as one of the correct licenses needed.  

Update grpc + tools to 1.38

See merge request gitlab-org/labkit-ruby!77

Add Ruby 3.0 build to CI

Closes #24

See merge request gitlab-org/labkit-ruby!68

Takuya Noguchi authored 3 years ago and Matthias Käppler committed 3 years ago

Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>

Add explicit dependency on webrick

See merge request gitlab-org/labkit-ruby!75

Add missing requires in context.rb

See merge request gitlab-org/labkit-ruby!76

This also makes 1.7.x the minimum version, which
addressed deprecation warnings under Ruby 3.

Switch back to pg_query

See merge request gitlab-org/labkit-ruby!74