Leverage repository checksums when moving a repository

See merge request gitlab-org/gitlab!26334

Allow to disable defaults

See merge request gitlab-org/gitlab!25690

Dynamically generate child pipeline from artifact

See merge request gitlab-org/gitlab!23790

* allow `trigger:artifact` to point to a job artifact
* document new feature
* Remove FF ci_limit_yaml_expansion

[ci skip]

[ci skip]

Add pipeline history to exported project content documentation

See merge request gitlab-org/gitlab!26644

Upgrade Pages to 1.17.0

See merge request gitlab-org/gitlab!26478

Incorporate 12.8.3 changelog updates from dev to gitlab.com

See merge request gitlab-org/gitlab!26654

Update documentation for danger's behaviour based on the current implementation

See merge request gitlab-org/gitlab!26642

This introduces job/bridge option `inherit:`
that disables inheritance of variables and defined
defaults.

Implement subscription triggering mechanism

Closes #9045

See merge request gitlab-org/gitlab!20063

Use less expensive index_options

Closes #28085

See merge request gitlab-org/gitlab!25992

Handles user preference theme in the Editor Lite

See merge request gitlab-org/gitlab!26606

Improve loading UX in the License Management list

See merge request gitlab-org/gitlab!25620

- Submit button to add a policy now uses the success variant
- When adding a new policy, the cancel button is disabled and the
loading icon is shown in the button itself, rather than replacing
the whole list while it is being updated
- When updating or removing a policy, the loading icon is shown next to
the policy's dropdown

BulkIndexer change _routing -> routing to support ES 7

See merge request gitlab-org/gitlab!26639

Refactor container repository api

See merge request gitlab-org/gitlab!26538

Support Rails 6 `insert_all!`

Closes #209036

See merge request gitlab-org/gitlab!26595

This fixes Load Balancing implementation
to support and test `insert_all!`

Variables handling is generic for Job and Bridge
it is better to keep it's behaviour in a single place

Merge branch '208678-packages-project-and-group-api-will-return-processing-nuget-packages' into 'master'

Prevent NuGet processing packages being returned by the API

See merge request gitlab-org/gitlab!26270

Project packages API does not include processing packages
Same for group packages API
Package by id will no longer include processing
Package files will no longer include processing
Updated tests

Ensure RepositoryLinkFilter handles Gitaly failures gracefully

See merge request gitlab-org/gitlab!26531

Geo - Replace Browser Confirm with Modal

Closes #202125

See merge request gitlab-org/gitlab!24808

Merge branch '196650-replace-underscore-with-lodash-for-app-assets-javascripts-filtered_search' into 'master'

Replace underscore with lodash for ./app/assets/javascripts/filtered_search

Closes #196650

See merge request gitlab-org/gitlab!26629

Update managed cert-manager chart to 0.10.1

See merge request gitlab-org/gitlab!26345

Reorganize the Container Scanning sections

See merge request gitlab-org/gitlab!20449

Fix image alignment in lists

Closes #209226

See merge request gitlab-org/gitlab!26631

Adding SSH max connection details

See merge request gitlab-org/gitlab!26535

In ES 6.x onwards _routing is deprecated in the bulk API but in 7.x it
was removed completely. While this is sadly not clearly documented it's
referenced in a few places like
https://discuss.elastic.co/t/deprecated-field-routing-used-expected-routing-instead/115951
and we also learnt this when fixing the Go indexer at
https://gitlab.com/gitlab-org/gitlab-elasticsearch-indexer/-/merge_requests/34

I have tested this version works for 6.5.1 , 6.8.1 and 7.5.1 .
Additionally since this is the same way that our
Go gitlab-elasticsearch-indexer is behaving this should be a safe
change.

See https://gitlab.com/gitlab-org/gitlab/-/issues/208717#note_300201720

Fix k8s namespace resolution for new deployments

See merge request gitlab-org/gitlab!25853

The namespace shown on the job show page was sometimes incorrect for
deployments to non-managed clusters when
environment:kubernetes:namespace was specified in the CI YAML. This was
due to the last successful deployment being used to resolve the CI YAML
namespace, instead of the CI YAML for the deployment being constructed.

Note that the correct namespace was still being used for the actual
deployment.

Separate SCIM Identities from SAML

See merge request gitlab-org/gitlab!26124