Add a new script that can be run in CI to verify that migrations added
in a merge request cleanly rollback to the previous known database state
on the target branch.

Namespace CI Pipeline Mutations

See merge request gitlab-org/gitlab!50292

AWS install cost fixes and changes

See merge request gitlab-org/gitlab!50663

Fixes a typo and some future tense.

Allow custom rate limiting response text

See merge request gitlab-org/gitlab!50693

Send `finding_uuid` to backend while creating feedback

See merge request gitlab-org/gitlab!50628

Add support LaTeX in jupyter notebooks

See merge request gitlab-org/gitlab!49497

Add MathJax package as well

Remove lfs_chunked_encoding feature flag

See merge request gitlab-org/gitlab!50557

Fix identicon text color in dark mode

See merge request gitlab-org/gitlab!49785

Remove direct mod of Vue instance

See merge request gitlab-org/gitlab!50629

Remove centos6 and link to supported os docs

See merge request gitlab-org/gitlab!50659

Incorporate single bullet list into paragraph

See merge request gitlab-org/gitlab!50662

Fix colon typo in install page

See merge request gitlab-org/gitlab!50661

Artifact Download in MR widget

See merge request gitlab-org/gitlab!49780

* Create generic component
* Add API Fuzzing constants

Working artifact dropdown for json assets

Add archive, metadata, trace download support

* Add support to download additional artifact types to
artifact download button

Add unit tests

- Unit tests for artifact download component

Update unit tests

* Update group security report specs
* Update mr widget specs

Apply code review feedback

* Refactor util function
* Refactor eslint rule exceptions

Update artifact download vue props

* Mark targetFullPath and mr id props as required

Apply review feedback

* Require props
* Update unit tests
* Prettier/Linter and Changelog

Fix details_page/details_header_spec time dependent spec

See merge request gitlab-org/gitlab!50739

Auto-assign merge request author when creating from issue

See merge request gitlab-org/gitlab!50263

Merge branch '296504-broken-master-spec-controllers-dashboard-projects_controller_spec-rb-39' into 'master'

Fix: spec/controllers/dashboard/projects_controller_spec.rb:39

See merge request gitlab-org/gitlab!50742

Add `DAST_AUTH_VALIDATION_URL` docs

See merge request gitlab-org/gitlab!50716

Quarantine export file download spec in staging only and update issue link

See merge request gitlab-org/gitlab!50706

Unified auth for NuGet package manager

See merge request gitlab-org/gitlab!38627

When a request exceeds a rate limit configured in the admin panel, we
default to returning a 429 response with a plain-text body of 'Retry
later'. This change allows the response body to be customised - although
it must still be plain text - which allows, for example, GitLab.com to
provide a link to GitLab.com-specific rate limiting documentation.

Update WEBrick to v1.6.1

See merge request gitlab-org/gitlab!50720

- Add an auth builder system to improve API auth
- Use new system for NuGet
- NuGet now requires usernames to be valid when authenticating with a
  PAT or deploy token

Add `dismissal_reason` argument to the `VulnerabilityDismiss` mutation

See merge request gitlab-org/gitlab!50688

Ruby ships with WEBrick v1.6.0, but v1.6.1 contains a fix for a CVE:
https://bugs.ruby-lang.org/issues/17201

We only use WEBrick for Sidekiq exporter to serve internal metrics, so
this CVE shouldn't be a user-facing issue.

Relates to https://gitlab.com/gitlab-org/gitlab/-/issues/296224

Experiment user  context column to get merged rather than overridden

See merge request gitlab-org/gitlab!50684

The current behavior is being overridden

Add link to issue in issue due email

See merge request gitlab-org/gitlab!50642

Update feature categories for 2020-12-31

See merge request gitlab-org/gitlab!50709

- plus a test.

https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/70219
reorganised some of these categories. Most of the items that were under
`collection` can go to `usage_ping`, but the historical usage export
probably belongs under `provision` (as it's to do with license usage),
and the survey response are - tangentially - under `navigation`.

Quarantines flaky Usage Data Specs

See merge request gitlab-org/gitlab!50708

See tracking issue https://gitlab.com/gitlab-org/gitlab/-/issues/296169