These are data columns that store runtime configuration
of build needed to execute it on runner and within pipeline.

The definition of this data is that once used, and when no longer
needed (due to retry capability) they can be freely removed.

They use `jsonb` on PostgreSQL, and `text` on MySQL (due to lacking
support for json datatype on old enough version).

Don't ingore the `gitlab.pot` in ee_compat_check

See merge request gitlab-org/gitlab-ce!24151

Guarantee visually correct order of runners on the "Admin Area > Runners" page

Closes #49791

See merge request gitlab-org/gitlab-ce!21627

Documentation for Release page MVC

Closes #41766

See merge request gitlab-org/gitlab-ce!23901

If there are new strings in CE, they need to be added to EE
manually. As the `locale/gitlab.pot` file can't be merged
automatically during the upstream merge.

Support asset links creation in `POST /projects/:id/release`

See merge request gitlab-org/gitlab-ce!24056

Mark references to openshift template as deprecated

See merge request gitlab-org/gitlab-ce!24092

Update @gitlab/svgs to latest version

See merge request gitlab-org/gitlab-ce!24148

Fix coding style

Improve coding style

Decouple UPDATE and DELETE operations of asset links

Rename links_attributes to assets:links

Rename exposed param and updated spec

Fix spec for mysql unique validation failure

Releases::Source and Releases::Link are covered by tests

- Add Releases::Links model
- Expose it in release API
- Add integration tests

Deprecate Auto Deploy's quick start guide

Closes #55853

See merge request gitlab-org/gitlab-ce!24096

Green pipeline for feature freeze PROCESS

See merge request gitlab-org/gitlab-ce!23809

Specific CI indexes to avoid statement timeout.

Closes #50763

See merge request gitlab-org/gitlab-ce!23188

Create shared gl-modal-vuex component and module

See merge request gitlab-org/gitlab-ce!24140

Resolve "Add "Submit feedback" in-product feedback link"

Closes #43623

See merge request gitlab-org/gitlab-ce!23547

Make RBAC enabled by default for new clusters

Closes #53696

See merge request gitlab-org/gitlab-ce!24119

Made user_popovers_spec more stable

See merge request gitlab-org/gitlab-ce!24145

Bring back reverted Gold Trial MR (CE backport)

See merge request gitlab-org/gitlab-ce!23621

Use cheap operation for `Ci::Pipeline#all_merge_requests`

Closes #54907

See merge request gitlab-org/gitlab-ce!24115

Add a comment on `Ci::Pipeline#git_ref` about merge request ref

Closes #54908

See merge request gitlab-org/gitlab-ce!24114

Many changes were also made to tests that expected this to default to
false.

Only validate project visibility when it has changed

Closes #55881

See merge request gitlab-org/gitlab-ce!24142

Merge branch '49056-configure-auto-devops-deployed-applications-with-secrets-that-aren-t-committed-to-the-repo' into 'master'

Configure Auto DevOps deployed applications with secrets from prefixed CI variables

See merge request gitlab-org/gitlab-ce!23719

Installation/Update guides for 11.7

See merge request gitlab-org/gitlab-ce!24109

Remove redundant counts in snippets search

Closes #44353

See merge request gitlab-org/gitlab-ce!23952

Support new issue creation by email without subaddressing

Closes #29951

See merge request gitlab-org/gitlab-ce!23523

[CE] Don't run checks for changed refs when specific changes are unknown

See merge request gitlab-org/gitlab-ce!23990

On GitLab.com, there are hundreds of projects that have visibility
levels that are inconsistent with the fork or group settings. Most
likely, this happened during a GitLab project import because the
validation was bypassed.  Attempting to migrate these projects to hashed
storage fails even though the migration doesn't touch the visibility
settings. Skipping the visibility validation allows the migration to go
through.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/55881