Using `unknown` instead of `anonymous` to avoid confusion with an
unauthenticated user when an operation name was not
provided. Unrecognized operation names remain the same.

Added severity to issues REST API

See merge request gitlab-org/gitlab!82696

Previously this field was only available in GraphQL, this change adds it
to the REST API (display only)

Changelog: changed
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/82696Signed-off-by: Raimund Hook <raimund.hook@exfo.com>

Support 303 redirects when downloading via CommandLineUtil

See merge request gitlab-org/gitlab!83066

Update RSpec config to enable test filter shorthand alias of :focus

See merge request gitlab-org/gitlab!83181

It's an attempt to make Gitlab::HTTP redirection following behaviour
the same as OpenURI which we were using before.

Update saml response alert

See merge request gitlab-org/gitlab!83226

Upgrade rack-proxy to v0.7.2

See merge request gitlab-org/gitlab!83241

Rate limit user_email_lookup_limit removal

See merge request gitlab-org/gitlab!83155

Add `Migration[2.0]` that enforces `restrict_gitlab_migration`

See merge request gitlab-org/gitlab!82505

Fix backups not working when feature_flags table does not exist

See merge request gitlab-org/gitlab!83101

Fix NoMethodError for CommitController

See merge request gitlab-org/gitlab!83123

Don't trigger a sentry error for Gitaly exceptions

See merge request gitlab-org/gitlab!83084

Rename namespace `Oauth::Jira` to `Oauth::JiraDvcs`

See merge request gitlab-org/gitlab!82903

Enqueuer job: set deduplication until executed

See merge request gitlab-org/gitlab!83091

This implements a new migration version and validates if correct
migration version is used depending on a cutoff points.

This allows to enforce a usage of a new `restrict_gitlab_migration`.

Changelog: added

**Problem**

We add a Sentry error for cases when Gitaly is not available. We
already handle this exception, so Sentry tracking is not necessary.

We return a 200 response when the Gitaly is not available. It is
confusing and makes it difficult to track unsuccessful requests.

**Solution**

* Respond with 503 error
* Don't log exceptions in Sentry

Changelog: changed

To point out that it's only used for DVCS

Remove :reliable tag from smoke tests

See merge request gitlab-org/gitlab!83158

Explain delete permission on multi-project runners

See merge request gitlab-org/gitlab!82805

This change adds a tooltip explaining to group owners why they can't
delete a runner that has been already added to multiple projects.

Add recommendations for webhook receivers

See merge request gitlab-org/gitlab!83112

Moves the new section below 'Configure a Webhook'

Redirected old file

See merge request gitlab-org/gitlab!83126

This file is not in the nav and has
not been for 9 months. It gets
fewer than 50 views per day
Related to: https://gitlab.com/gitlab-org/gitlab/-/issues/332102

This fixes a bug that manifested with the `webpack-dev-server` and the
`thin` Web server.

When a chunked transfer is proxied from rack-proxy, the proxied HTTP
response would contain the original `Transfer-Encoding: chunked` HTTP
header. However, the body would be stripped of the chunked encoding
headers. As a result, Workhorse would fail to parse the body with the
error:

```
httputil: ReverseProxy read error during body copy: invalid byte in
chunk length
```

This occurred because the Golang chunked decoder expected to parse a
length represented as an ASCII number followed by a `\r\n`. Instead,
the first byte was a binary character from the gzipped data.

This does not occur with Puma because Puma initiates a request with an
HTTP/1.0 header and explicitly disables chunked transfers.

https://github.com/ncr/rack-proxy/pull/59 fixes this problem by
dropping the `Transfer-Encoding: chunked` header so that Workhorse
won't handle the HTTP response as a chunked transfer.

See https://gitlab.com/gitlab-org/gitlab-development-kit/-/issues/1443
for more details.

Changelog: fixed

Merge branch '356137-bug-selecting-a-compliance-violation-with-the-same-mr-should-keep-the-drawer-open' into 'master'

Fix compliance report drawer closing incorrectly

See merge request gitlab-org/gitlab!83097

The compliance report drawer now stays open when a new violation
is selected with the same merge request.

Add ability to sort by escalation status to issues GraphQL query

See merge request gitlab-org/gitlab!82160

Adds ESCALATION_STATUS_ASC and ESCALATION_STATUS_DESC
options to issues query in GraphQL.

Create the add videos to continuous onboarding experiment

See merge request gitlab-org/gitlab!82274

- Create video_tutorials_continuous_onboarding experiment feature flag
- Publish experiment in LearnGitlabController
- Add a button top open videos in a new tab from learn_gitlab
- Track click to video in candidate flow of experiment
- Make learn_gitlab_section_card responsive
- Update snaphost & unit tests for learn_gitlab

Add feature flag info to incident escalation docs

See merge request gitlab-org/gitlab!83122

It was expected that this feature would be enabled earlier, but that 
didn't ultimately happen. This updates the documentation to reflect the 
current state and expected functionality.

Quarantining pipeline creation test

See merge request gitlab-org/gitlab!83219

Alias user_email_lookup_limit to search_rate_limit

See merge request gitlab-org/gitlab!83213

Changelog: changed