Rescue elasticsearch server error in pod logs

See merge request gitlab-org/gitlab!25367

Add context to background migrations

See merge request gitlab-org/gitlab!25008

This will add the `caller_id` to the context for every job that might
be scheduled from a background migration. So if a background migration
reschedules itself or another migration, this will now be visible in
the metadata.

Remove jira_connect_app feature flag

See merge request gitlab-org/gitlab!24818

Removing the :jira_connect_app
feature flag from controllers, services
and specs

Fixes 'tags' support in 'default'

See merge request gitlab-org/gitlab!24741

Fix feature flag check on container registry explorer

Closes #23315

See merge request gitlab-org/gitlab!25511

Chore: replace underscore with lodash for in /app/assets/javascripts/blob

See merge request gitlab-org/gitlab!25113

Consider flags disabled when generating GraphQL schema

See merge request gitlab-org/gitlab!25172

Use sentinel value for truncated param logging

See merge request gitlab-org/gitlab!25518

Remove ignore_column :storage_version

Closes #205196

See merge request gitlab-org/gitlab!25515

Add http status cop to some subdir request specs

See merge request gitlab-org/gitlab!25166

285 files inspected, 21 offenses detected, 21 offenses corrected

Our Elasticsearch mapping on GitLab.com requires params to be an array
of hashes, each hash with a `key` and `value` key. This does not apply
to our Sidekiq arguments logging, as Sidekiq arguments can be of
different types anyway, and do not have keys.

Being collecting blob size metrics

See merge request gitlab-org/gitlab!25462

Use gitlab-workhorse v8.22.0

See merge request gitlab-org/gitlab!25425

Resolve "Migrate '.fa-spinner' to '.spinner' for 'app/assets/javascripts/blob/template_selector.js'"

See merge request gitlab-org/gitlab!25045

Resolve "Migrate '.fa-spinner' to '.spinner' for 'app/assets/javascripts/blob/template_selector.js'"

Allow enabling/disabling modsecurity from UI

See merge request gitlab-org/gitlab!24747

This is a change on the front-end on clusters
applications page. Similar to what has been
done by other cluster apps, it makes
modsecurity settings editable by the user.

Separate pipelines query from vuln findings query

See merge request gitlab-org/gitlab!24757

* Refactor VulnerabilityFindingsFinder to take pipeline IDs and use
    them in the query for vulnerability findings
* Move query for pipelines to the controller actions and the caching
    classes
* Removes Vulnerable. We are no longer using the methods included in it

https://gitlab.com/gitlab-org/gitlab/issues/202183

Skip SPDX deprecated licenses

See merge request gitlab-org/gitlab!25278

Use a path instead of URL for badge API endpoints

See merge request gitlab-org/gitlab!25493

Define hit/miss counters for diff caching

Closes #207005

See merge request gitlab-org/gitlab!25382

Add project and group into feature flag check
Check that explorer is active in js first

Correctly render GFM in README files

See merge request gitlab-org/gitlab!25445

Resolve "Migrate '.fa-spinner' to '.spinner' for 'app/assets/javascripts/create_merge_request_dropdown.js'"

See merge request gitlab-org/gitlab!24917

Resolve "Migrate '.fa-spinner' to '.spinner' for 'app/assets/javascripts/create_merge_request_dropdown.js'"

Correctly renders GFM in README files in the repository listing

Underscore has been replaced with Lodash in app/assets/javascripts/blob.

Addresses #196694

Only load usage ping cron schedule for Sidekiq

See merge request gitlab-org/gitlab!25325

Previously the initializer always loaded the `application_settings`
table in the initializer, even for Rake tasks (e.g. `rake
db:setup). This was done because the usage ping worker needed to load
the UUID of theins instance from the database to calculate the usage
ping schedule. However, cron schedules are only needed by Sidekiq, so we
can defer the calculation of this value in the Sidekiq initializer.

When loading application settings from the database, this should make it
possible for us to raise errors when the connection is not present since
this appears to be the only setting that is actually needed at init
time.

This came out of a discussion in
https://gitlab.com/gitlab-org/gitlab/issues/205640.

Add more detailed logging of errors in Jira service

See merge request gitlab-org/gitlab!25007

Add internal doc for AuditEventService

See merge request gitlab-org/gitlab!25428

Aid developer in future work with this mega class.

Migrate '.fa-spinner' to '.spinner' for 'app/assets/javascripts/vue_shared/components/markdown/toolbar.vue'

Closes #202274

See merge request gitlab-org/gitlab!25057

Migrate '.fa-spinner' to '.spinner' for 'app/assets/javascripts/vue_shared/components/markdown/toolbar.vue'

Move environments_app_spec to jest testing

See merge request gitlab-org/gitlab!25363