- for use in notifying users about invite failures

Changelog: added

Fix bugs when splitting batched migration jobs

See merge request gitlab-org/gitlab!65838

Remove configure_dependency_scanning invalid query

See merge request gitlab-org/gitlab!66041

Add plan limits for Premium and Ultimate

See merge request gitlab-org/gitlab!65600

Clean up temporary code

See merge request gitlab-org/gitlab!65769

Enable runner_detailed_view_vue_ui by default

See merge request gitlab-org/gitlab!65948

Enable runner_list_view_vue_ui by default

See merge request gitlab-org/gitlab!65901

Create branch from Jira issue MVC 1: add supporting Vue components

See merge request gitlab-org/gitlab!66034

Denormalize shared runners to CI::PendingBuild

See merge request gitlab-org/gitlab!64644

Partition manager identifies partitions to detach

See merge request gitlab-org/gitlab!65093

Release the Helm charts registry

See merge request gitlab-org/gitlab!65768

- Remove the helm_charts feature flag
- Update helm related documentation

Changelog: added

Fix GET requests from graphql client when using relative url

See merge request gitlab-org/gitlab!66053

Add information about The Art Of PostgreSQL training

See merge request gitlab-org/gitlab!65272

Improve inline error message for elapsed time field in policy model

See merge request gitlab-org/gitlab!65775

Docs for recording and assignment tracking shared example

See merge request gitlab-org/gitlab!66011

Update Gitaly version

See merge request gitlab-org/gitlab!66068

Migrate the deprecated "urlParamsToObject" to "queryToObject"

See merge request gitlab-org/gitlab!65898

By creating and detaching partitions using the same lease, we can
easily skip the partition sync code if another node is currently
executing it. This is safe because we have six months of headroom for
future partitions and the job to sync partitions runs every six hours

Adds the partition_pruning_dry_run feature flag.

Even though the partition manager does not actually detach any
partitions yet, putting the logic for determining the set of partitions
to detach behind a flag makes rolling out this code safer, because the
logic changed touches the logic for creating new partitions.

Feature flag issue: https://gitlab.com/gitlab-org/gitlab/-/issues/335315

The previous code was using try_obtain once and two seperate locks,
so concurrent code would skip the critical section.

Switching to using in_lock and a single lock ensures that all concurrent
runners get to execute the code, and that partition creation and
partition detaching do not interfere with each other.

This worker runs `PartitionManager.detach_partitions` on a schedule to
trigger the detach logic for old database partitions that are no longer
needed

Enumerate the partitions that are outside of the retention period, and
for each one log a message that we are planning to detach it.

This way we can run this code in production for a while
and be sure that the choices of partitions to detach are correct.

This is the first step in providing support for detaching and dropping
old partitions of time-series database tables.

This identifies the set of partitions that should be detached by
calculating the set of desired partitions, and removing partitions that
are entirely before the retain_for cutoff date.

Only renders notes tab when viewing discussions

See merge request gitlab-org/gitlab!65824

Resolve "Show warning if no .git in the URL when importing Repo by URL"

See merge request gitlab-org/gitlab!65739

Enhance image extension to support image uploads

See merge request gitlab-org/gitlab!65763

Clean up review app by namespace

See merge request gitlab-org/gitlab!63292

Prevent Transfering a Group with a Subscription

See merge request gitlab-org/gitlab!65689