Add Projects Pipelines Controller Spec

See merge request gitlab-org/gitlab!26844

Comment implementation code and new spec

Render special references for release entities

See merge request gitlab-org/gitlab!26554

Migrate merge requests mentions to DB table

Closes #198338

See merge request gitlab-org/gitlab!25826

Resolve "code Snippets Description: Markdown is not rendered (it's just plain text)"

Closes #209995

See merge request gitlab-org/gitlab!27038

Use multiple values in list-type CI variable spec

See merge request gitlab-org/gitlab!27031

Fix create issue error by providing the missing param

Closes #209894

See merge request gitlab-org/gitlab!27075

Load derailed_benchmarks fork with Zeitwerk fix

See merge request gitlab-org/gitlab!27080

Fix two flaky specs that didn't wait for the MR widget to load

Closes #208123

See merge request gitlab-org/gitlab!27078

Expose user's plan and trial status via API

Closes #198391

See merge request gitlab-org/gitlab!25151

`plan` is hooked up to the models but trial is not yet.

Fix spec failures due to PG::LockNotAvailable errors

Closes #207088

See merge request gitlab-org/gitlab!27060

We were seeing a high number of transient failures in the migration jobs
because `with_lock_retries` leaked non-zero, short `lock_timeout` values
(e.g. 100 ms) when used inside a Rails `change` method. If the
PostgreSQL autovacuum process happened to be running, it would lock the
table that it was vacuuming. During the migration rollback, if the DDL
operation needed a lock on the table, the short `lock_timeout` would
encounter the existing table lock and fail.

Even though `SET LOCAL` was used to ensure `lock_timeout` didn't leak
outside of the current transaction, the parent transaction would still
retain that value.

To avoid this issue, we should define separate `up` and `down` methods
so that we don't rely on the Rails magic to reverse a migration. This
ensures lock retries are used properly in both directions and prevents
`lock_timeout` from leaking during a migration rollback.

Closes https://gitlab.com/gitlab-org/gitlab/-/issues/207088

Resolve "Status Page MVC: JSON format and endpoints"

Closes #207935

See merge request gitlab-org/gitlab!26979

Remove gitlab-shell indirection for authorized_keys changes

See merge request gitlab-org/gitlab!26913

Fix the way derailed_benchmarks patches require so that it works
with Zeitwerk and Bootsnap

Migrate mentions that appear in merge request title or description
to its respective merge_request_user_mentions db table

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

API endpoint for deleting project deploy tokens

See merge request gitlab-org/gitlab!25220

Add outdated security report section

See merge request gitlab-org/gitlab!26362

Update doc/user/application_security/img/outdated_report_pipeline_v12_9.png, doc/user/application_security/img/outdated_report_branch_v12_9.png files

Track transition error on concurrent bridge update

See merge request gitlab-org/gitlab!26566

Updating Code Quality Versions to 0.85.9

See merge request gitlab-org/gitlab!26712

Update Code-Quality.gitlab-ci.yml so it's always the latest version deployed in the security products.

Fix logic to determine export status

Closes #32203

See merge request gitlab-org/gitlab!23664

204774 Quick actions executed in multiline inline code, when placed on it's own line

Closes #204774

See merge request gitlab-org/gitlab!24933

Migrate blob_file_dropzone to jest

See merge request gitlab-org/gitlab!26776

Migrate ee/spec/javascripts/prometheus_metrics/ to Jest

Closes #194301

See merge request gitlab-org/gitlab!27012

Improve NPM api tests execution time

See merge request gitlab-org/gitlab!26810

Design view: better resizing support for zoomed-in designs

See merge request gitlab-org/gitlab!25406

Consider flags enabled when generating GraphQL schema

See merge request gitlab-org/gitlab!26939

Add organization transition to Jenkins doc

See merge request gitlab-org/gitlab!26897

Update pipeline copy on dependency & license compliance pages

See merge request gitlab-org/gitlab!26864

Currently, lock files are used to determine the state of a
project export. However, the lock files are not stored in a shared
volume, causing the export states to be reported incorrectly.

In order to fix this, we now store the export states in database
as a more reliable mechanism. The table used is project_export_jobs.
It stores the project_id, job_id and the current state.

In addition to existing states, also added are two new states
queued and regeneration_in_progress states. They are used to indicate
a job that's waiting to be started and the case when a project export
operation has been requested to be re-generated.

Failed jobs are re-tried 3 times, after which the state is updated
to failed.

To account for jobs that get stuck, a cron job runs every hour
to set the stuck jobs to failed state.

Closes https://gitlab.com/gitlab-org/gitlab/issues/32203

Remove reference to subject label

See merge request gitlab-org/gitlab!26928

- Subject labels look to have been renamed previously to feature labels.
- I also noticed that Blue is widely used across all different types of
labels so I removed that requirement from this workflow as well.