Uses token values for background
to better support dark mode in
all contexts.

Changelog: fixed

Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/517491

Changelog: added

Adds a visual scroll indicator (shadow) to indicate there is
more content available

Changelog: changed

The attribute `minimum_access_level_for_delete` that was introduced
in the MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/179739 .

This commit includes the attribute `minimum_access_level_for_delete`
in the GRAPHQL API and also updates the documentation.

Changelog: added

Changelog: changed

Adds the `usage_count` data source to query for a single Value Streams
Dashboard count metric and
return data fit for `SingleStat` visualization. Also creates
visualization templates for each metric.

Changelog: added
EE: true

When LFS files are locked, we create a PathLock, similarly, when a path
is locked which is an LFS file, we create an LfsFileLock.

Previously this logic was duplicated in the PathLock controller and the
GraphQL mutation.

This change moves the syncing logic into the services where it belongs.

It also updates the LFS locking and unlocking services to ensure we
don't have circular logic. When a path lock service calls an lfs
service, we tell the lfs service not to create/destroy the path lock
after creating/destroying the lfs file lock. Similarly, the lfs services
do the same in the opposite direction.

Related to https://gitlab.com/gitlab-org/gitlab/-/issues/512677

This reverts merge request !183259

Using the same create service for both REST API and GraphQL improves
the consistency and DRY.

Given that configurable statuses functionality
should only be available for Premium and Ultimate
users, we need to ensure the status widget is
EE-only.

This commit moves the status widget-related classes
under the EE namespace to achieve that.

In order to display entire days in the CI/CD
analytics chart, this change removes the time of
day and timezone from the dates sent to request
pipelines' information.

Changelog: added

This adds `diff_files_metadata` endpoint for each resource that
we support in rapid diffs (e.g. `MergeRequest`, `Commit` and
`Compare`).

This is behind `rapid_diffs` FF.

Fixes overflow and invalid
rounded class on work items
labels dropdown items.

Changelog: changed

This adds internal event tracking to several events
in placeholder reassignment.

Changelog: other

Changelog: other

Changelog: changed

- sometimes getModel returns nul and the ui errors
- add a check for this
- update tests

Changelog: fixed

Remove only create validation of
validate_only_one_sharding_key_present
and validate_imported_entity_type

Changelog: other

- Ensure Add link has accessible description
- Ensure TH cells have accessible text

Changelog: fixed

Add a callback to backfill project with pipeline variables table on new records
Address all the comments
Skip id primary key in favor of project_id
Add a trigger function instead of model callback
Add a trigger migration
Allow projects_with_pipeline_variables cross database

Changelog: added

So we can delete top level groups without reloading the page

In GitLab 17.6, the package protection feature was made generally
available. But, this realease did not include
the deletion package protection,
see https://gitlab.com/gitlab-org/gitlab/-/issues/472655 .

The attribute `minimum_access_level_for_delete` that was introduced
in the MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/179739 .

This attribute is integrated in this MR in order to prevent the deletion
of delete protected packages.

At the moment, the attribute `minimum_access_level_for_delete` cannot be
updated via UI, REST nor GraphQL API. This possibility will be added in
a future iteration.

Changelog: added

Changelog: fixed

Changelog: fixed
EE: true

- Behind feature flag `vscode_extension_marketplace_settings`
- https://gitlab.com/gitlab-org/gitlab/-/issues/508977

Changelog: changed

Unify the provide data names.

This table stores the CI pipeline inputs values configured when creating
a pipeline schedule. It belongs to a pipeline schedule, ensures that the
input keys are unique, and encrypts the input values. It is on the
gitlab_ci database schema because pipeline schedules are also stored on
the CI schema.

Changelog: added
Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/519960

Changelog: fixed

When the merge request source branch was ambiguous in the source
project, detached merge request pipelines would pick commit SHA
associated with the tag instead of the merge request's branch.

We fix that by using `source_branch_ref` instead of `source_branch` in
the places deciding the commit used by detached merge request pipelines.

Changelog: fixed

Ensures the frontend link so the docs