The endpoints configured via alert integrations have the ability to be 
rate-limited by project. For gitlab.com, the default values are now
being utilized.

Remove boolean from preview dropdown item

See merge request gitlab-org/gitlab!90930

Add clusterAgents field to Project/Group/Security Dashboard GraphQL API

See merge request gitlab-org/gitlab!89357

Changelog: added
EE: true

docs: GitLab 13 requires Redis 5.0 or higher

See merge request gitlab-org/gitlab!90685

Wait for dropdown to render list of items

See merge request gitlab-org/gitlab!90849

Add better disable 2FA reference

See merge request gitlab-org/gitlab!90747

Add operational_vulnerabilities_filters feature flag

See merge request gitlab-org/gitlab!90845

GET List project pipelines contract test

See merge request gitlab-org/gitlab!90549

Default on group_level_security_policies

See merge request gitlab-org/gitlab!90855

Determine ownership of appsec page

See merge request gitlab-org/gitlab!90139

This commit makes a tiny change, so I can start a merge request. I
don't have the real answer to what stage or group this work needs to
be assigned to, but by starting a merge request, I can assign it to
the people who DO know.

Add a toggle for opt-in JWT to project settings

See merge request gitlab-org/gitlab!90132

Remove SCSS utilities which moved to gitlab-ui in v42.1.0

See merge request gitlab-org/gitlab!90864

Add troubleshooting docs for when a job already exists

See merge request gitlab-org/gitlab!90906

Respect namespace_id for bitbucket server importer

See merge request gitlab-org/gitlab!90830

Remove clusters_integrations_elastic_stack metric from UsagePing

See merge request gitlab-org/gitlab!90699

Compress PNG images

See merge request gitlab-org/gitlab!90902

Update scan-execution-policies.md for agents

See merge request gitlab-org/gitlab!90661

Create issue templates for master broken triage

See merge request gitlab-org/gitlab!90550

Change the revoke button to type `tertiary`

See merge request gitlab-org/gitlab!90003

We decided this change was better than these two other proposals:

* [Draft: Change the revoke button type to `secondary`](
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/89504
)

* [Draft: Change the revoke button to 3 different types](
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/89507
)

In the AccessTokenTableApp component, users may not understand why
some access tokens have a primary revoke button (background red),
while other access tokens have a secondary (transparent background).

Originally, I believe the primary|secondary buttons were meant to
match the color of the text of the Expires column (3 colors: red for
expired token, orange for soon-to-be-expired, black for tokens without
expiration). However, the match for the button was not perfect:
primary button for tokens with expiration, secondary button for
tokens without expiration.

This MR changes the revoke buttons to be of type tertiary.

Changelog: changed

Create coverage report on root ancestor pipeline when the whole hierarchy has completed

See merge request gitlab-org/gitlab!89950

- default on feature flag

Changelog: changed

Geo: Update object storage replication documentation for GA

See merge request gitlab-org/gitlab!90760

See https://gitlab.com/groups/gitlab-org/-/epics/8056

Adding note about Certificate-based Kubernetes Deprecation

See merge request gitlab-org/gitlab!90074

Add schedule delay for RepositoryUpdateMirrorWorker

See merge request gitlab-org/gitlab!90749

Refactor CI rules entry to use composed value

See merge request gitlab-org/gitlab!90238

When we return a value from an entry, we always need to return the
composed version. In Rules, we return "config", which means the hash
version of what the YAML file has. I changed it to "super" because
it needs to have composed value of each sub entry.

With this, we also needed to change the
validate_against_warnings method. Since we haven't composed the nested
entries yet, we cannot use *_value attributes there.

These changes are behind a feature flag
ci_value_change_for_processable_and_rules_entry

Add consistency regarding wording for repository mirroring on branches, tags and commits

See merge request gitlab-org/gitlab!87866

Docs should be written in present tense.

Add docs for group-level security policies

See merge request gitlab-org/gitlab!89197

- add new screenshot