DNS Rebind SSRF in Kubernetes Integration

See merge request gitlab/gitlabhq!3345

Send TODOs for comments on commits correctly

See merge request gitlab/gitlabhq!3361

Gitaly: ignore git redirects

See merge request gitlab/gitlabhq!3373

[ci skip]

[ci skip]

[ci skip]

Update dependency @gitlab/svgs to ^1.70.0

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

Bump ruby-prof to 1.0.0

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

Install Unleash Client Gem

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

Backport expired job artifact trait

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

Add helpers to exactly undo cleanup_concurrent_column_rename

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

- Also add helper to undo rename_column_concurrently.

This is significant improvement over the previous releases:
https://github.com/ruby-prof/ruby-prof/blob/master/CHANGES

Preload tags when loading Ci::Pipeline

Closes #60925

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

Fix Serverless entry page layout

Closes #64764

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

Enable line charts in dashbaord panels and embedded charts

Closes #66073

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

Delete rename trigger before creating to prevent error

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

- When renaming a column concurrently, drop any existing trigger before
attempting to create a new one.

When running migration specs multiple times (as it happens during
local development), the down method of previous migrations are called.
If any of the called methods contains a call to
rename_column_concurrently, a trigger will be created and not removed.
So, the next time a migration spec is run, if the same down method is
executed again, it will cause an error when attempting to create the
trigger (since it already exists). Dropping the trigger if it already
exists will prevent this problem.

Add migration to execute SelfMonitoring::Project::CreateService

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

Add to the service and migration both.

Fix issuable sidebar icon of notification disabled

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

Fix link to issue template

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

Adds cop to enforce string limits on migrations

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

This cop will analyze migrations that add columns with string, and
report an offense if the string has no limit enforced

Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/64505

Merge branch '55999-misleading-pipeline-tooltip-messages-and-misleading-ci-status-icons-on-simple-commits' into 'master'

Change misleading pipeline status tooltip

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

Some pipeline status icon tooltips were showing
"Commit: ..." which customers found to be
misleading since it was not the commit that was
failing but the pipeline.

We are changing all status icon tooltips to say
"Pipeline: ..." instead of "Commit: ..." now.

Resolve "Use Visual Review Tools NPM package"

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

Read pipelines from public projects though API

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

Allow users to read pipelines for public projects
with public builds enabled without providing an access token.

Return correct user for manual deployments

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

New cycle analytics backend stage events

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

- Introducting StageEvents to define the available events
- Define the event pairing rules, since some events are not compatible
- Express default Cycle Analytics stages with the event structure

Remove the visual review toolbar code
in favor of using the NPM package.

Adding gitaly feature flag for go implementation of get all lfs pointers

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

by adding the proper notification icon

Remove redundant index

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