In dev environments, Sidekiq was encountering the message:

Circular dependency detected while autoloading constant Gitlab::Profiler

This saves some overhead during normal usage.

Update requirements wording in docs

See merge request gitlab-org/gitlab-ce!31428

Merge branch '50130-cluster-cluster-details-update-automatically-after-cluster-is-created' into 'master'

Resolve "Cluster > Cluster details > Update automatically after cluster is created"

Closes #65151 and #50130

See merge request gitlab-org/gitlab-ce!27189

Only display the details of the cluster page when the cluster
exists. If it is in "creating" state, show a message and a spinner

All Kubectl command should return array by default

See merge request gitlab-org/gitlab-ce!31305

Don't run danger on stable branches

See merge request gitlab-org/gitlab-ce!31430

Update dependency @gitlab/ui to ^5.12

See merge request gitlab-org/gitlab-ce!31242

- Also, include pikaday styles through gitlab-ui

Uninstall Helm/Tiller

See merge request gitlab-org/gitlab-ce!27359

Also creates specs

Only allow Helm to be uninstalled if it's the only app

- Remove Tiller leftovers after reser command
- Fixes specs and offenses

Adds changelog file

Fix reset_command specs

Documentation - Services slack

See merge request gitlab-org/gitlab-ce!31004

Make `needs:` to require a strong reference

Closes #65512

See merge request gitlab-org/gitlab-ce!31419

Add md files to .prettierignore

See merge request gitlab-org/gitlab-ce!31426

This is to prevent prettier from auto formatting doc files.

I'm adding some wording to our hardware requirements to explain that needs vary
by workload. I also included some examples of factors that may influence the
workload.

Removes update_statistics_namespace feature flag

See merge request gitlab-org/gitlab-ce!31392

This changes `needs:` from weak reference
to have a strong reference.

This means that job will not be created
unless all needs are present as part of
a pipeline.

Resolve "Breakage in displaying SVG in the same repository"

See merge request gitlab-org/gitlab-ce!31352

Support X_if_ee methods for QA tests

See merge request gitlab-org/gitlab-ce!31379

Update HA resource descriptions

Closes #61192 and #27833

See merge request gitlab-org/gitlab-ce!31064

Respect needs on artifacts

Closes #65466

See merge request gitlab-org/gitlab-ce!31413

Improve job log rendering performance

See merge request gitlab-org/gitlab-ce!31262

Currently we write out empty CSS classes (`class=""`) every time we
create a new tag. This adds 9 unnecessary bytes per span element. In a
recent trace, I have counted 11950 span elements. So we transported 105
unnecessary kilobytes!

After measuring the impact of the namespace storage on
https://gitlab.com/gitlab-org/gitlab-ce/issues/64092. It was decided
that it's performant enough. So we can freely remove the feature flag

Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/64092

Resolve docker in docker problems

See merge request gitlab-org/gitlab-ce!31417

Syncs the vue test utils helpers

See merge request gitlab-org/gitlab-ce!31349

See https://gitlab.com/gitlab-com/gl-infra/production/issues/1023

This also has been suggested by Tomasz in the MR

Fix performance bar warnings when Rugged is disabled

Closes #65491

See merge request gitlab-org/gitlab-ce!31395

Improve test for .with_needs

See merge request gitlab-org/gitlab-ce!31411

Update end-to-end style guide doc with new guideline

See merge request gitlab-org/gitlab-ce!31342

When `needs:` is defined, the value of it is
not respected when returning a list of artifacts
to the runner from the job.

Clean up job_app_spec

See merge request gitlab-org/gitlab-ce!31400

Fix GC::Profiler metrics fetching

See merge request gitlab-org/gitlab-ce!31331

Previously, both InfluxSampler and RubySampler were relying on the
`GC::Profiler.total_time` data which is the sum over the list
of captured GC events. Also, both samplers asynchronously called
`GC::Profiler.clear` which led to incorrect metric data because
each sampler has the wrong assumption it is the only object who calls
`GC::Profiler.clear` and thus could rely on the gathered results between
such calls.

We should ensure that `GC::Profiler.total_time` is called only in one
place making it possible to rely on accumulated data between such wipes.

Also, we need to track the amount of profiler reports we lost.

Make `bin/web_puma` consider RAILS_ENV

See merge request gitlab-org/gitlab-ce!31378