fix #56369

chore(changelog): Added changelog entry

chore(prettier): Formated with prettier

test(JumpToNextDiscussionButton): Added test for new component

test(Refactored tests to use vue test-utils):

chore(translations): Added newly generated locales

Update spec/javascripts/notes/components/discussion_jump_to_next_button_spec.js
chore(prettier): Formated with prettier

test(JumpToNextDiscussionButton): Updated tests to use a local vue instance

test(JumpToNextDiscussionButton): Running tests in async to prevent maximum stack overflow

Resolve "Remove `error_tracking` feature flag"

Closes #56213

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

Remove unwanted margin above suggested changes.

Closes #56389

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

Improvements for spec migration readme

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

Update vuex.md - swap PUT/POST methods

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

Fix Resource attribute bug

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

Update reference to ~Monitoring to be ~Monitor

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

Correct minimum yarn version in 11.6 -> 11.7 upgrade doc

Closes #56254

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

Cleanup stale +deleted repo paths on project removal (adjusts project removal bug)

Closes #46146

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

View epic permissions

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

Return the maximum group access level in the projects API

Closes #43684

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

1. When removing projects, we can end-up leaving the +deleted
repo path dirty and not successfully removing the non-deleted
namespace (mv process is not atomic and can be killed without
fully moving the path).

2. In order to solve that, we're adding a clean-up phase on
ensure which will schedule possible staled +deleted path deletion.
Note that we don't check the current state (if there is or not a
repo) in order to schedule the deletion. That's intentional
in order to leverage Gitlab::GitalyClient::NamespaceService#remove
idempotency and ensure consistency.

Add documentation for new NGINX Ingress metrics

Closes #56473

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

[EE Backport] Add notes filters for epics

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

Add flat-square badge style

Closes #30120

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

Use MR IID in Review Apps slug and domain

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

Merge branch '56328-frequent-items-initialisations-can-be-optimised-and-deferred-in-idlecallback' into 'master'

Resolve "Frequent Items Initialisations can be optimised and deferred in idleCallback"

Closes #56328

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

Avoid overwriting default jaeger values with nil

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

Fix runner eternal loop when update job result

Closes #56518

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

Collapses directory structure in merge request tree

Closes #53069

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

During the review process for adding opentracing factories, a bug was
introduced which caused Jaeger to initialize an invalid tracer. The
bug was due to use sending nil through as a kwarg when the Jaeger
initializer used a non-nil default value.

This is fairly insidious as, the tracer looks like a tracer, but, when
methods are invoked, it throws `NoMethodError` errors. To ensure that
this issue does not happen in future, the tests have been changed to
ensure that the tracer works as expected. This could avoid problems
in future when upgrading to newer versions of Jaeger.

Add spec

Add changelog

Bump rbtrace version to 0.4.11

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

Port generic Helm upgrade functionality to CE

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

Export default in vuex_shared/modal/actions

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

Handle emptyText in user_avatar_list

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

- #update_errored? method def is redundant, already defined from state
machine
- #update_in_progress? moved to ApplicationStatus
- #ready_status becomes a constant. Previously it was extended in ee/ so
maybe that was why it's a instance method

Use CI variables in CI docker build examples

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

This change renames a dependency and fixes a minor bug, but this upgrade
is happening because Gitaly will be receiving rbtrace as a dependency.

The document is now split in two sections:
- Testing an ActiveRecord migration
- Testing an non-ActiveRecord migration

Both sections have an example