Changelog: changed

Make menu items in top nav translatable

See merge request gitlab-org/gitlab!77475

Adds project and corpus last

See merge request gitlab-org/gitlab!77228

Create agent-specific vulnerability list

See merge request gitlab-org/gitlab!76713

Add note explaining that nested arrays are OK

See merge request gitlab-org/gitlab!77554

Improve epic swimlanes loading performance for group issue board

See merge request gitlab-org/gitlab!75378

Allow tag deletion on broken tags

See merge request gitlab-org/gitlab!76971

- Remove tag validation in delete API
- Show delete button even when tag is broken

Remove foreign key ci_group_variables.group_id as we have loose fK

See merge request gitlab-org/gitlab!77494

Add COVFUZZ_PROJECT_PATH to Coverage-Fuzzing.gitlab-ci.yml.
Update corpus to use last package file instead of first package file.

Changelog: changed
EE: true

Fix deploying AWS Lambda function using GitLab CI/CD

See merge request gitlab-org/gitlab!77471

Improve reliable test report issue title and labels

See merge request gitlab-org/gitlab!77580

In https://gitlab.com/gitlab-org/gitlab/-/merge_requests/77322 we
already added a ["loose foreign key"](
https://docs.gitlab.com/ee/development/database/loose_foreign_keys.html)
to replace this foreign key. Now that this has been running fine in
production we should be OK to remove the foreign key altogether.

This was added in a post-deployment migration as we want to ensure that
they have the correct code running with the loose foreign key in place
before we remove the foreign key to ensure that there isn't any lost
deletes.

Changelog: other

Correct documentation on exporting member list

See merge request gitlab-org/gitlab!77597

Fix checkbox position in RTL lists

See merge request gitlab-org/gitlab!77072

Clarify post-deployment migration for loose foreign key process

See merge request gitlab-org/gitlab!77542

Update Gitaly version

See merge request gitlab-org/gitlab!77641

Resolve "Unitless number in CSS `calc()` causes the computation to fail"

See merge request gitlab-org/gitlab!77633

Fix migration for cases with empty strings

See merge request gitlab-org/gitlab!77506

Add exception to exclude here in link

See merge request gitlab-org/gitlab!77634

Deployment Approvals API

See merge request gitlab-org/gitlab!76689

Implement an Internal API to handle mailroom webhook

See merge request gitlab-org/gitlab!76724

Recently, JwtAuthenticatable supports multi-secret secret per inherited
class. This use case is not suitable for mailroom JWT flow, which
includes one secret per mailbox. JwtAuthenticatable hasn't supported iat
verification to control token age.

Do not show participants invisible to the user

See merge request gitlab-org/gitlab!77021

Here docs are a shell thing, and a valid use of
'here' in link text

It is called here documents

See merge request gitlab-org/gitlab!77599

Add solution section

See merge request gitlab-org/gitlab!77572

Externalize strings for translation in todos template

See merge request gitlab-org/gitlab!77402

Changelog: fixed

Geo: adapt verification timed out query to use state table

See merge request gitlab-org/gitlab!77364

Fix broken link in default ReadME

See merge request gitlab-org/gitlab!77026

Merge branch '341195-reschedule-pending-recalculatevulnerabilitiesoccurrencesuuid-jobs' into 'master'

Recalculate UUID for all Vulnerability::Finding records, attempt 2

See merge request gitlab-org/gitlab!75546

There are two major reasons for this:

1. We made a mistake in the algorithm when recalculating this for the
first time.
See: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/67578

2. The algorithm changed yet again to improve the tracking method
See: https://gitlab.com/gitlab-org/gitlab/-/issues/322044

Changes:

* Update background migration to use signatures

* Make previous reschedule a no-op so customers doing major version
  leaps will not schedule the same job multiple times

* Remove ALL jobs from `background_migration_jobs` table. Succeeded jobs
  should be removed anyway and pending jobs were not finished because we
  had records for which the recalculation yielded identical UUIDv5. The
  reason we had such records was due to mistake outlined in point 1.
  This situation was fixed by
  https://gitlab.com/gitlab-org/gitlab/-/merge_requests/74008

* Schedule `RecalculateVulnerabilitiesOccurrencesUuid` over entire
  `vulnerability_occurrences` table so we can leverage our new algorithm
  and finish the migration path from UUIDv4 to UUIDv5.

Changelog: added

Adding resolution to common error message

See merge request gitlab-org/gitlab!77390