This will include fix for noisy warnings visible when running the app
with Ruby 3.

Changelog: other

Fix eslint issues related to no-sequences

See merge request gitlab-org/gitlab!68960

Check for FOR UPDATE queries

See merge request gitlab-org/gitlab!68863

Add param to allow scoped caching of Repo#merge_to_ref

See merge request gitlab-org/gitlab!68790

Previously, the `nextTick` wasn't awaited, which meant that the on-call
schedules list wasn't rendered anyway.

This also makes sure the previous wrapper is destroyed before creating
a new one for this test.

Fix Rubocop Graphql/Description offenses

See merge request gitlab-org/gitlab!68819

Update the FF Rollout Template

See merge request gitlab-org/gitlab!68484

Downgrade grpc from 1.38.0 to 1.30.2

See merge request gitlab-org/gitlab!68865

Add 13.8.3 as an intermediate stop for upgrade paths

See merge request gitlab-org/gitlab!68874

A first draft for emacs configuration instructions

See merge request gitlab-org/gitlab!68093

Update GitLabUI to 32.2.3

See merge request gitlab-org/gitlab!68651

Cache content_sha256 field for Files API

See merge request gitlab-org/gitlab!67280

E2E: Autoload QA classes with zeitwerk

See merge request gitlab-org/gitlab!68478

Add Gitaly feature flag definition

See merge request gitlab-org/gitlab!68879

Changelog: performance

More edits to the needs details

See merge request gitlab-org/gitlab!68934

Add DAST profiles components README

See merge request gitlab-org/gitlab!68768

Add note about android not supported dependency scanning

See merge request gitlab-org/gitlab!68802

Status Page: Track incident issue without subtransaction

See merge request gitlab-org/gitlab!68776

Update Gitaly version

See merge request gitlab-org/gitlab!68945

Adds a new ready to merge widget state component

See merge request gitlab-org/gitlab!68565

Define group runners attributes helper

See merge request gitlab-org/gitlab!68864

Never fetch more than 101 commits when processing a git push

See merge request gitlab-org/gitlab!67491

`StatusPage::PublishedIncident#track` used `safe_find_or_create_by` to
circumvent a potential race condition in case of a duplicate published
issue.  This, however, uses subtransactions under the hood which is
problematic in nested transactions.

See https://gitlab.com/groups/gitlab-org/-/epics/6540 for more context.

In the rare event of `ActiveRecord::RecordNotUnique` users end up seeing
a meaningful error message. This behaviour is acceptable and that's why
switched to unsafe method `find_or_create_by`.

Remove upsert_issue_metrics feature flag

See merge request gitlab-org/gitlab!68829

Update Gitaly version

See merge request gitlab-org/gitlab!68937

Always run full migration specs on DB change

See merge request gitlab-org/gitlab!68840

checks: Always enable batched computation of commits

See merge request gitlab-org/gitlab!68747

Remove column from project_settings

See merge request gitlab-org/gitlab!68854