Update the definitions to the correct spelling, so they'll stop
showing up for the Technical Writing team as spelling errors.

Change Core to Free in API and CI docs

See merge request gitlab-org/gitlab!52944

Log user approval/rejection in application logs

See merge request gitlab-org/gitlab!51768

Project access token API

See merge request gitlab-org/gitlab!52139

Not working yet

Even more exciting spelling corrections!

See merge request gitlab-org/gitlab!52940

Continuing to clean up spelling issues from our docsets!

Update dependency core-js to ^3.8.3

See merge request gitlab-org/gitlab!51585

Change Core to Free for admin docs

See merge request gitlab-org/gitlab!52936

Merge branch '254263-replace-bootstrap-modal-in-app-views-shared-notifications-_button-html-haml' into 'master'

Add Vue notifications dropdown component to project details

See merge request gitlab-org/gitlab!52068

Spelling changes, next round

See merge request gitlab-org/gitlab!52932

Populate description of vulnerability from finding if needed

See merge request gitlab-org/gitlab!52619

Remove LDAP "Edit Permissions" button for inherited group members [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!52847

Replace mountComponent with mount

See merge request gitlab-org/gitlab!52929

Smaller set of spelling fixes.

Explain Gitaly Cluster components

See merge request gitlab-org/gitlab!51946

Add front matter for 3 new pages

See merge request gitlab-org/gitlab!52930

These pages need to be tracked by the technical writing team.
Add front matter to do so.

Deal with spelling issues throughout docsets

See merge request gitlab-org/gitlab!52927

- Renders a Vue notification dropdown
component on the project overview page

Create the update form for compliance frameworks

See merge request gitlab-org/gitlab!52479

Deal with spelling issues in multiple ways. Add some words to the
spelling exceptions list. Fix misspellings. Turn off spellchecking on
things that shouldn't be in the exceptions list, but we also can't
remove.

Don't require a bucket if object storage is disabled for a type

See merge request gitlab-org/gitlab!52750

Extract Roadmap filtering to a mixin

See merge request gitlab-org/gitlab!52793

Hack `Prependable` class methods for `override`

See merge request gitlab-org/gitlab!52419

Add API for generating changelogs in GitLab

See merge request gitlab-org/gitlab!52116

Fix capitalization

See merge request gitlab-org/gitlab!52853

Migrate health status dropdown to use gitlab ui

See merge request gitlab-org/gitlab!52273

Previously if a user enabled consolidated settings then selectively
disabled some object storage types, they were still required to set a
bucket name for that object type. For example:

1. Enable consolidated object storage
(https://docs.gitlab.com/ee/administration/object_storage.html).

2. Configure the artifacts object storage with the below:

```
gitlab_rails['object_store']['objects']['artifacts']['enabled'] = false

gitlab_rails['artifacts_enabled'] = true
```

Reconfigure GitLab and you see this error:

```
Object storage for artifacts must have a bucket specified
```

Since the previous workaround would be to set a dummy bucket name, this
change skips assigning consolidated settings if object storage has been
disabled for a specific type.

Relates to https://gitlab.com/gitlab-org/gitlab/-/issues/233826

Merge branch '227349-package-registry-expand-the-filter-and-sort-functionality-on-the-package-registry-list-view' into 'master'

Redesign the search UI for the package list

See merge request gitlab-org/gitlab!52575

- source
- tests
- snapshots

Fix rename column concurrently

See merge request gitlab-org/gitlab!52032

Forbid git pushes to group wikis when repo is read only

See merge request gitlab-org/gitlab!52801

Fix tier for custom branch name for groups

See merge request gitlab-org/gitlab!52632