RFC: https://gitlab.com/gitlab-org/frontend/rfcs/-/issues/47

Backport unit tests changes from Apollo migration MR

See merge request gitlab-org/gitlab!77990

Added `waitForPromises` to unit tests to work with modified helper

Merge branch '350286-experiment-cleanup-redirect-in-app-trial-users-to-the-feature-that-they-requested-the-trial' into 'master'

Redirect in-app trial users to the feature

See merge request gitlab-org/gitlab!78917

Changelog: added
EE: true

Added GitLab Runner to steps

See merge request gitlab-org/gitlab!78752

Replace deprecated usage of find/findAll in ee/spec/frontend/security_dashboard

See merge request gitlab-org/gitlab!78633

* migrate to proper use of findComponent/findAllComponents

Cache CI expire_in parsing

See merge request gitlab-org/gitlab!78953

Fix CI instance variable cache misses

See merge request gitlab-org/gitlab!78944

Applied .container-fluid .container-limited classes

See merge request gitlab-org/gitlab!78676

Resolves https://gitlab.com/gitlab-org/gitlab/-/issues/350469

Add breaking change values to removals

See merge request gitlab-org/gitlab!78943

When a removal is in the 14_0 directory, assume it was a breaking change

Based on this comment: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/78716\#note_817172127
Decided to update this phrase because it makes more sense this way

Remove PagesUpdateConfigurationWorker logic

See merge request gitlab-org/gitlab!78449

Previously the CI processor spent a surprising amount of time
validating the `expire_in` field for each build in the pipeline. It
turns out `ChronicDuration.parse` can be expensive because it uses
regular expressions and ActiveSupport numeric conversions.

We observe that builds often use a small set of `expire_in` values, so
we can cache the result of a previous validation.

For a pipeline like `gitlab-org/gitlab` that has 200 builds with 8
different `expire_in` values, we see a 28x improvement:

```
Calculating -------------------------------------
                 old     1.000  i/100ms
                 new    14.000  i/100ms
-------------------------------------------------
                 old      5.275  (± 0.0%) i/s -     27.000
                 new    149.409  (± 5.4%) i/s -    756.000

Comparison:
                 new:      149.4 i/s
                 old:        5.3 i/s - 28.32x slower
```

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

Changelog: performance

Add BulkImports Project Members Migration & Refactor Group Members Migration

See merge request gitlab-org/gitlab!78455

Adding 14.6 removals to Docs

See merge request gitlab-org/gitlab!78731

GraphQL: Add projects property to CiRunner type

See merge request gitlab-org/gitlab!78547

Extend documentation about db:check-migrations

See merge request gitlab-org/gitlab!78700

Update CODEOWNERS to include TW assignments for files

See merge request gitlab-org/gitlab!77606

Remove blank lines

Doc Consistency: user/project/clusters - monitor

See merge request gitlab-org/gitlab!76798

Improve OmniAuth sign in description

See merge request gitlab-org/gitlab!72438

Changelog: changed

This page belongs to the development directory and does not require
the same level of polish as user documentation. Quick word and style
cleanups for tone and style.

Add missing issue due date filters

See merge request gitlab-org/gitlab!78460

Adds `any`, `today`, and `tomorrow` issue due_date filters
to API.

Changelog: added

Merge branch 'Alexand-clarify-db-check-migrations' of gitlab.com:gitlab-org/gitlab into Alexand-clarify-db-check-migrations

Start from the top, layering in revisions for tone, wording usage,
and style.

Speed up project exports by moving the archive to the cache dir

See merge request gitlab-org/gitlab!78986

Add scan_result_policy into user docs

See merge request gitlab-org/gitlab!76984

EE: true

Convert badge_list_row badge to GlBadge

See merge request gitlab-org/gitlab!78914

We briefly mentioned the existence of this job, but gave no details
as where to find it or what it does. This commit adds some explanation
as well as some troubleshooting tips.

Fix edition for Handling Stale Reads

See merge request gitlab-org/gitlab!78356