If this is applied the supported lenguages for Code Quality will be listed in the Code Quality Documentation Page

Resolve "Migrate spec/javascripts/projects/ to Jest"

See merge request gitlab-org/gitlab!26730

https://gitlab.com/gitlab-org/gitlab/-/merge_requests/26730

Change iid argument to ID_TYPE for graphQL queries

Closes #208394

See merge request gitlab-org/gitlab!26171

Geo Replicable - Generalize Mutations

See merge request gitlab-org/gitlab!26697

Remove analytics navbar feature flags

Closes #202094

See merge request gitlab-org/gitlab!26786

Quarantine a flaky spec

Closes #209999

See merge request gitlab-org/gitlab!27099

Introduce database table for user highest roles

See merge request gitlab-org/gitlab!26987

Resolve "Avatar Content type does not match file extension"

Closes #200107

See merge request gitlab-org/gitlab!25401

Rename some queue urgencies

See merge request gitlab-org/gitlab!26908

Add attachment attribute to a test case

See merge request gitlab-org/gitlab!26922

This MR makes it possible to parse an attachment tag on a JUnit report.
It creates a new attachment attribute on a test case object.

Fix lookup of namespace by pages host

See merge request gitlab-org/gitlab!27081

Remove a TODO for UpdateMergeRequestsWorker logging

See merge request gitlab-org/gitlab!27105

This renames the default queue urgency from `default` to `low` and the
latency without SLOs from `none` to `throttled`.

Fix doc linting issue with HA documentation

Closes #210362

See merge request gitlab-org/gitlab!27111

Un-swallow error message in Sentry issue sync worker

See merge request gitlab-org/gitlab!26945

Don't recalculate approval metrics on approval remove

Closes #210301

See merge request gitlab-org/gitlab!27071

The table stores the highest role for each User they have in a Group
or a Project. If a User has an open invite or pending access request or
no membership the highest role will be set to nil.

- analytics_pages_under_project_analytics_sidebar
- analytics_pages_under_group_analytics_sidebar
- group_level_productivity_analytics

Merge branch '210248-move-maturity-model-from-solutions-to-technical-high-availability-docs' into 'master'

Docs: Move "maturity" model from solutions to technical high availability docs

Closes #210248

See merge request gitlab-org/gitlab!27046

Split cluster info page into tabs

See merge request gitlab-org/gitlab!25940

Fix analytics max date range

See merge request gitlab-org/gitlab!26968

Enable issue summary on Releases page

See merge request gitlab-org/gitlab!27032

Fix snippet update error message

See merge request gitlab-org/gitlab!27082

Fix inconsistent inflection of Ldap module

See merge request gitlab-org/gitlab!26630

Update deprecated link in documentation

See merge request gitlab-org/gitlab!27091

We now have structured logging that tells us this information in a
better way.

Support async loading & search of projects

See merge request gitlab-org/gitlab!26661

Fix evidence SHA clipboard hover text

Closes #209002

See merge request gitlab-org/gitlab!26608

Match Monaco's white theme closely with the Pygments theme

See merge request gitlab-org/gitlab!25966

Delete unused CI helper functions

See merge request gitlab-org/gitlab!26999

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

Deduplicate state properties

See merge request gitlab-org/gitlab!26117

The following state properties have been deduplicated in the
vulnerabilities and security_reports store modules:

- isCreatingNewIssue/isCreatingIssue
- isDismissingVulnerability
- isCreatingMergeRequest

They will now only be set in the root state and not in the modal's
state

Run QA frontend jobs when dependencies are updated

See merge request gitlab-org/gitlab!26837

The QA jobs purpose is to catch if we utilize JavaScript that cannot be
executed on one of the node LTS versions we support for from-source
builds.

Currently we execute the QA jobs on master.

1. This means that they are executed unnecessarily, e.g. on docs only
   branches.
2. The thing which breaks the QA jobs are likely dependency updates, as
   we just test the webpack compilation and dependencies and
   subdependencies are usually requiring newer node versions. So we
   should be executing these checks on branches that update
   dependencies.

Recently we had a red master, because one dependency update required a
newer node version and the pipeline was green [0], [1].

Therefore I am proposing that we run the QA frontend jobs in merge
requests which are changing our package.json or yarn.lock file, as we
want to know if a dependency update would fail our build _before_ a red
master happens.

[0]: https://gitlab.com/gitlab-org/gitlab/-/issues/202187
[1]: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/24413