Security releases happen after the main monthly release, so the first
"backport" will actually be for the most recent release.

This frequently causes confusion and authors end up creating an
unnecessary backport for an older release, instead of the latest one.

This is explained in the [security workflow documentation][1], but we
should also clarify this in the security issue and merge request
templates.

We don't really need a milestone on the MR merging into `master`, so
we also change the Danger rules to not require one.

[1]: https://gitlab.com/gitlab-org/release/docs/blob/master/general/security/developer.md#security-merge-requests

Added deploy board to word list

See merge request gitlab-org/gitlab!68608

Made all instances of deploy board lowercase

See merge request gitlab-org/gitlab!68610

Normalize reportType filter for graphql query

See merge request gitlab-org/gitlab!68546

De-normalize tags used to retrieve builds queue

See merge request gitlab-org/gitlab!65648

Remove `board_new_list` feature flag [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!59826

Changelog: other

Enable `assumeImmutableResults` in group productivity-analytics

See merge request gitlab-org/gitlab!68631

Bump minimum Node version to 12.22.1

See merge request gitlab-org/gitlab!68430

Reduce the spacing of list items for Content Editor

See merge request gitlab-org/gitlab!68612

Prevents pipeline creation for builds with more than 50 tags

See merge request gitlab-org/gitlab!68380

Remove `track_unique_visits` feature flag

See merge request gitlab-org/gitlab!68569

Do not truncate vulnerability report filter dropdown items

See merge request gitlab-org/gitlab!68453

Refactor handling of commit sha in pipeline editor

See merge request gitlab-org/gitlab!67542

Introduce `ActiveRecord::Base.gitlab_schema` indicator

See merge request gitlab-org/gitlab!68160

Usage metrics update for Manage

See merge request gitlab-org/gitlab!68280

Enable the FF ci_new_artifact_file_reader by default

See merge request gitlab-org/gitlab!68293

Remove callbacks that obscure validations and rely instead on validations for user secondary emails

See merge request gitlab-org/gitlab!68048

Update Gitaly version

See merge request gitlab-org/gitlab!68632

It's enabled on GitLabcom

Changelog: fixed

Remove the `between_uses_list_commits` feature flag

See merge request gitlab-org/gitlab!68470

Prepare indexes on events for bigint column conversions

See merge request gitlab-org/gitlab!68426

Remove redundant and confusing checks on secondary emails,
rely on validations. On email update, reset secondary emails
if they were set to primary one

Changelog: fixed

This commit solves https://gitlab.com/gitlab-org/gitlab/-/issues/338450
It enables `assumeImmutableResults` in the group productivity-analytics.

Reproducible Builds: Use SOURCE_DATE_EPOCH for build time if present

See merge request gitlab-org/gitlab!68464

Add contacts table and model

See merge request gitlab-org/gitlab!67985

Extract static analysis jobs

See merge request gitlab-org/gitlab!68517

Add migration to create indexes asynchronously for the `events` table.
Creating the indexes asynchronously will preventing the column swap
migration from running for an excessive length of time.

Changelog: other

Add dsn to error tracking client key

See merge request gitlab-org/gitlab!68487

[ci skip]

`static-analysis` is not rails specific and
performs various kinds of static analyses:
rubocop, haml, jest, markdown, etc.

[ci skip]

Integration docs, substitution fixes

See merge request gitlab-org/gitlab!68382