Use the allowed find_by_id method instead of find_by(id: 1).

Shift the user's contribution calendar based on their timezone setting

See merge request gitlab-org/gitlab!72938

Add & update security considerations for PATs

See merge request gitlab-org/gitlab!73696

Reset GitlabSubscription seats when starting a new term

See merge request gitlab-org/gitlab!73078

Add IaC scanning to Security Configuration page

See merge request gitlab-org/gitlab!73155

feat: Set PersonalAccessToken default prefix

See merge request gitlab-org/gitlab!73314

Fix fake connection leaking for Ci::ApplicationRecord

See merge request gitlab-org/gitlab!74032

Add another error message to SAML troubleshooting section

See merge request gitlab-org/gitlab!73157

Add UX reviewer/maintainer to Danger bot

See merge request gitlab-org/gitlab!51127

Fix merge requests not importing for older projects

See merge request gitlab-org/gitlab!74031

This restores the merge request commit user fields in import_export.yml
for the import case.

https://gitlab.com/gitlab-org/gitlab/-/merge_requests/73307 dropped
these YAML fields because supposedly the import would fail if the
database columns didn't exist, but I haven't found that to be the
case. I tested with an import with:

1. Project generated in v13.12 that had these columns.
2. Project generated with the latest nightly build.

The import works in either case because we call
`MergeRequestDiffCommit.new` with the sanitized attributes in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/73307.

Based on the discussion in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/72219, these
attributes are needed for **import** but excluded for **export**. I
think Yorick might have assumed that since the code in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/73307 manually
removed these fields, we wouldn't need them anymore. However, without
these attributes, imports were failing to import with an older GitLab
version (e.g. v13.12) because the attributes were sanitized before the
importer got a chance to use them.

Changelog: fixed

Changelog: changed

After the example has run, the
Ci::ApplicationRecord#connection_specification_name remained stuck as
"Ci::ApplicationRecord" instead of reverting back to
"ActiveRecord::Base".

We call model.remove_connection to fix this.

Also, there is no need to setup a (fake) ci connection, if we already
have one

Update gitlab-dangerfiles to 2.5.0

See merge request gitlab-org/gitlab!73971

Updated release:name to standards

See merge request gitlab-org/gitlab!74029

Update pipelines api docs

See merge request gitlab-org/gitlab!73795

Fix issue rebalance banner

See merge request gitlab-org/gitlab!73608

Change the copy and empty state illustrations in the Kubernetes section

See merge request gitlab-org/gitlab!73586

Show blocked icon on epic blocked issues

See merge request gitlab-org/gitlab!72229

Add parsed YAML is too big section

See merge request gitlab-org/gitlab!73768

Clarify loss of DAG behavior with `needs:pipeline`

See merge request gitlab-org/gitlab!73622

Added comment to clarify that none of the items are used in the docs

See merge request gitlab-org/gitlab!74020

Related to: https://gitlab.com/gitlab-org/gitlab/-/issues/343854

Restore the BackgroundMigration.remaining method

See merge request gitlab-org/gitlab!74015

Refactor fetching board scope to GraphQL [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!73604

Changelog: changed
EE: true

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