Remove ignore rules from Component

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/153701



Merged-by: Allison Browne <abrowne@gitlab.com>
Approved-by: Tyler Amos <tamos@gitlab.com>
Approved-by: Pavel Shutsin <pshutsin@gitlab.com>
Approved-by: Allison Browne <abrowne@gitlab.com>
Co-authored-by: Avielle Wolfe <awolfe@gitlab.com>

Refactor runner wait time component

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/153732



Merged-by: Michael Lunøe <michael.lunoe@gmail.com>
Approved-by: Briley Sandlin <bsandlin@gitlab.com>
Approved-by: Michael Lunøe <michael.lunoe@gmail.com>
Reviewed-by: Michael Lunøe <michael.lunoe@gmail.com>
Co-authored-by: Miguel Rincon <mrincon@gitlab.com>

Merge branch 'backfill-desired-sharding-key-small-table-design_management_repositories' into 'master' 

Add and backfill namespace_id for design_management_repositories

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/153150



Merged-by: Adam Hegyi <ahegyi@gitlab.com>
Approved-by: Manoj M J <mmj@gitlab.com>
Approved-by: Adam Hegyi <ahegyi@gitlab.com>
Reviewed-by: Huzaifa Iftikhar <hiftikhar@gitlab.com>
Co-authored-by: Abhilash Kotte <akotte@gitlab.com>

Disable sticky writes in the PAT last used service

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/153707



Merged-by: James Fargher <jfargher@gitlab.com>
Approved-by: Imre Farkas <ifarkas@gitlab.com>
Approved-by: James Fargher <jfargher@gitlab.com>
Co-authored-by: David Fernandez <dfernandez@gitlab.com>

When updating the last_used_at column, disable the sticky writes so that if the current session is on the replicas, we don't suddenly go for the primary.

This change is behind a feature flag.

Add sharding key tracking issues for secrets_management

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/152810



Merged-by: Omar Qunsul <oqunsul@gitlab.com>
Approved-by: Scott Hampton <shampton@gitlab.com>
Approved-by: Omar Qunsul <oqunsul@gitlab.com>
Co-authored-by: Maxime Orefice <morefice@gitlab.com>
Co-authored-by: Manoj M J <mmj@gitlab.com>

Add sharding key tracking issues for feature category `secrets_management`.

## Background

These tables were unable to be classified automatically, and will require manual input. Eventually all tables will
need to be correctly classified, but we understand that this will be complex for some tables and completing these
will take time. Instead, our goal for this task is to ensure all remaining tables are tracked in an issue, and to
classify any straightforward cases that our automation may have missed (options 1 and 2 below).

We have assigned a random backend engineer from ~"group::pipeline security" as the initial DRI for this task, as well as an
engineering manager for visibility. Please note that we are not requesting a large time commitment, creating one
issue and linking it for all tables is perfectly acceptable.

When you are finished, please assign to the ~database reviewer/maintainer suggested by Danger.

If you have any questions or concerns, reach out to `#g_tenant-scale`.

## Task

For each table, please select one of the following options:

### Option 1: Add a sharding key tracking issue

This option is best suited to tables whose sharding behaviour is unknown, or will require additional work before
a sharding key can be defined.

Replace the `TODO` in the dictionary file with a link to an issue in the gitlab-org/gitlab project.

```diff
- sharding_key_issue_url: TODO
+ sharding_key_issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/1234
```

You can create a new issue or link an existing one, and multiple entries can refer to the same issue. These issues will
be used to track the work remaining on the [progress dashboard](https://cells-progress-tracker-gitlab-org-tenant-scale-g-f4ad96bf01d25f.gitlab.io/sharding_keys).

If you are creating a new issue, you can copy over the following contents to the issue description:

<details><summary>Click to expand</summary>

  Issue Title: Set sharding keys for tables in 'group::pipeline security'

  Issue Description:

  Sharding keys need to be set for the tables: ci_instance_variables, ci_job_variables, ci_pipeline_variables

  This involves choosing one of the following, based on the intended behaviour of the table:
  - **The table is not cell-local**
    - Set `gitlab_schema` to `gitlab_main_clusterwide`.
  - **The table is cell-local and requires a sharding key**
    - Set `gitlab_schema` to `gitlab_main_cell`
    - Add a `sharding_key` or `desired_sharding_key` configuration. If the configuration is known but the chosen key
      doesn't yet meet not-null and foreign key requirements, you can add an exception to
      `allowed_to_be_missing_not_null` or `allowed_to_be_missing_foreign_key` to get the pipeline passing. Please
      link to a follow-up issue in a code comment next to the exception.
    - You may also need to set `allow_cross_joins`, `allow_cross_transactions` and `allow_cross_foreign_keys` if changing
      the schema causes pipeline failures. See [`db/docs/epics.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/docs/epics.yml?ref_type=heads#L12-17)
      for an example.
  - **The table is cell-local and does not require a sharding key**
    - Set `gitlab_schema` to `gitlab_main_cell` and
    - Set `exempt_from_sharding` to `true`.

  ### Documentation

  - [Choosing either the gitlab_main_cell or gitlab_main_clusterwide schema](https://docs.gitlab.com/ee/development/database/multiple_databases.html#choose-either-the-gitlab_main_cell-or-gitlab_main_clusterwide-schema)
  - [Defining a sharding key for all cell-local tables](https://docs.gitlab.com/ee/development/database/multiple_databases.html#defining-a-sharding-key-for-all-cell-local-tables)
  - [Defining a desired_sharding_key to automatically backfill a sharding_key](https://docs.gitlab.com/ee/development/database/multiple_databases.html#define-a-desired_sharding_key-to-automatically-backfill-a-sharding_key)

</details>

### Option 2: Add sharding key configuration

This option is best suited to tables with an easily identifiable sharding key that will require minimal work to
define.

Remove `sharding_key_issue_url` from the dictionary file and instead complete the classification for the table.
This involves choosing one of the following, based on the intended behaviour of the table:
- **The table is not cell-local**
  - Set `gitlab_schema` to `gitlab_main_clusterwide`.
- **The table is cell-local and requires a sharding key**
  - Set `gitlab_schema` to `gitlab_main_cell`
  - Add a `sharding_key` or `desired_sharding_key` configuration. If the configuration is known but the chosen key
    doesn't yet meet not-null and foreign key requirements, you can add an exception to
    `allowed_to_be_missing_not_null` or `allowed_to_be_missing_foreign_key` to get the pipeline passing. Please
    link to a follow-up issue in a code comment next to the exception.
  - You may also need to set `allow_cross_joins`, `allow_cross_transactions` and `allow_cross_foreign_keys` if changing
    the schema causes pipeline failures. See [`db/docs/epics.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/docs/epics.yml?ref_type=heads#L12-17)
    for an example.
- **The table is cell-local and does not require a sharding key**
  - Set `gitlab_schema` to `gitlab_main_cell` and
  - Set `exempt_from_sharding` to `true`.

### Documentation

- [Choosing either the gitlab_main_cell or gitlab_main_clusterwide schema](https://docs.gitlab.com/ee/development/database/multiple_databases.html#choose-either-the-gitlab_main_cell-or-gitlab_main_clusterwide-schema)
- [Defining a sharding key for all cell-local tables](https://docs.gitlab.com/ee/development/database/multiple_databases.html#defining-a-sharding-key-for-all-cell-local-tables)
- [Defining a desired_sharding_key to automatically backfill a sharding_key](https://docs.gitlab.com/ee/development/database/multiple_databases.html#define-a-desired_sharding_key-to-automatically-backfill-a-sharding_key)

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

This change was generated by
[gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
using the Keeps::AddShardingKeyTrackingIssues keep.

To provide feedback on your experience with `gitlab-housekeeper` please comment in
<https://gitlab.com/gitlab-org/gitlab/-/issues/442003>.

Changelog: other

Fix duplicating of work items in child widget

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/153937



Merged-by: Natalia Tepluhina <ntepluhina@gitlab.com>
Approved-by: Himanshu Kapoor <info@fleon.org>
Approved-by: Natalia Tepluhina <ntepluhina@gitlab.com>
Co-authored-by: Rajan Mistry <rmistry@gitlab.com>

Add validation for fallback_behavior

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/154024



Merged-by: Alexander Turinske <aturinske@gitlab.com>
Approved-by: Sharmad Nachnolkar <snachnolkar@gitlab.com>
Approved-by: Deepika Guliani <dguliani@gitlab.com>
Reviewed-by: Deepika Guliani <dguliani@gitlab.com>

Regenerate OpenAPI documentation of REST API

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/154043



Merged-by: Hunter Stewart <hustewart@gitlab.com>
Approved-by: Ashraf Khamis <akhamis@gitlab.com>
Approved-by: James Nutt <jnutt@gitlab.com>
Approved-by: Hunter Stewart <hustewart@gitlab.com>
Co-authored-by: Luke Duncalfe <lduncalfe@eml.cc>

Fix jQuery Endless Scroll in Vite

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/154129



Merged-by: Lukas 'ai-pi' Eipert <leipert@gitlab.com>
Approved-by: Lukas 'ai-pi' Eipert <leipert@gitlab.com>
Co-authored-by: Stanislav Lashmanov <slashmanov@gitlab.com>

Edit Branch Rules: UI for Branch protection toggles

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/153281



Merged-by: Jacques Erasmus <jerasmus@gitlab.com>
Approved-by: Michael Le <mle@gitlab.com>
Approved-by: James Rushford <jrushford@gitlab.com>
Approved-by: Marcin Sedlak-Jakubowski <msedlakjakubowski@gitlab.com>
Approved-by: Jacques Erasmus <jerasmus@gitlab.com>
Reviewed-by: Jacques Erasmus <jerasmus@gitlab.com>
Reviewed-by: Marcin Sedlak-Jakubowski <msedlakjakubowski@gitlab.com>
Reviewed-by: James Rushford <jrushford@gitlab.com>
Co-authored-by: psjakubowska <psedlak-jakubowska@gitlab.com>

Displays a toggle for anyone who can manage certain protection
and icon for users who do not have edit rights.

EE: true

Add endpoint to call verified namespace service

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/152641



Merged-by: Laura Montemayor <lmontemayor@gitlab.com>
Approved-by: Avielle Wolfe <awolfe@gitlab.com>
Approved-by: Laura Montemayor <lmontemayor@gitlab.com>
Co-authored-by: Kasia Misirli <kmisirli@gitlab.com>

Remove beta status from AI impact analytics dashboard

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/153729



Merged-by: Bojan Marjanovic <bmarjanovic@gitlab.com>
Approved-by: Roy Liu <rliu@gitlab.com>
Approved-by: Libor Vanc <5022246-lvanc@users.noreply.gitlab.com>
Approved-by: Bojan Marjanovic <bmarjanovic@gitlab.com>
Co-authored-by: Rudy Crespo <rcrespo@gitlab.com>

Resolve Layout/ArgumentAlignment offenses 58

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/151255



Merged-by: George Koltsov <gkoltsov@gitlab.com>
Approved-by: George Koltsov <gkoltsov@gitlab.com>
Co-authored-by: gaurav.marwal <gauravmarwal@gmail.com>

Set height: auto on images

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/154122



Merged-by: Lukas 'ai-pi' Eipert <leipert@gitlab.com>
Approved-by: Lukas 'ai-pi' Eipert <leipert@gitlab.com>
Co-authored-by: Himanshu Kapoor <hkapoor@gitlab.com>

Set imported_from value for project export import

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/153462



Merged-by: George Koltsov <gkoltsov@gitlab.com>
Approved-by: Evan Read <eread@gitlab.com>
Approved-by: George Koltsov <gkoltsov@gitlab.com>
Reviewed-by: George Koltsov <gkoltsov@gitlab.com>
Reviewed-by: Evan Read <eread@gitlab.com>
Reviewed-by: Luke Duncalfe <lduncalfe@gitlab.com>
Co-authored-by: carlad-gl <cdrago@gitlab.com>

Adds gitlab_project to the imported_from column for
relevant relations during project export import.

Changelog: fixed

Add a help text for some form fields when setting up a cluster UI

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/153513



Merged-by: Anna Vovchenko <avovchenko@gitlab.com>
Approved-by: Phillip Wells <pwells@gitlab.com>
Approved-by: Rudy Crespo <rcrespo@gitlab.com>
Approved-by: Anna Vovchenko <avovchenko@gitlab.com>
Approved-by: Emily Bauman <ebauman@gitlab.com>
Reviewed-by: Rudy Crespo <rcrespo@gitlab.com>
Co-authored-by: Anton Kalmykov <anton.kalmykov@proton.me>

Add a description text for the Kubernetes namespace
and Flux resource fields when setting up a cluster UI

Update pot file
Update corresponding spec files
Closes: https://gitlab.com/gitlab-org/gitlab/-/issues/424493
Changelog: added

Use Duo icon and language for AI actions in editor

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/153321



Merged-by: Justin Ho Tuan Duong <hduong@gitlab.com>
Approved-by: Suzanne Selhorn <sselhorn@gitlab.com>
Approved-by: Justin Ho Tuan Duong <hduong@gitlab.com>
Approved-by: Katie Macoy <kmacoy@gitlab.com>
Reviewed-by: Nick Leonard <nleonard@gitlab.com>
Co-authored-by: Nick Leonard <nleonard@gitlab.com>

Updates the AI actions button to
align with Duo messaging

Changelog: changed
EE: true

Delete outdated statement in troubleshooting docs

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/154121



Merged-by: Jon Glassman <jglassman@gitlab.com>
Approved-by: Jon Glassman <jglassman@gitlab.com>
Co-authored-by: Ashraf Khamis <akhamis@gitlab.com>

Excludes pre-release versions from `~latest` tag and shorthand fetching

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/152771



Merged-by: Avielle Wolfe <awolfe@gitlab.com>
Approved-by: Rajendra Kadam <rkadam@gitlab.com>
Approved-by: Avielle Wolfe <awolfe@gitlab.com>
Reviewed-by: Rajendra Kadam <rkadam@gitlab.com>
Co-authored-by: Laura Montemayor <lmontemayor@gitlab.com>

Remove inline disable from background_migration_helpers

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/153960



Merged-by: David Dieulivol <ddieulivol@gitlab.com>
Approved-by: Alper Akgun <aakgun@gitlab.com>
Approved-by: David Dieulivol <ddieulivol@gitlab.com>
Co-authored-by: Peter Leitzen <pleitzen@gitlab.com>

A11y fix: make sure "+" button can be focused in wiki sidebar

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/154015



Merged-by: Michael Lunøe <michael.lunoe@gmail.com>
Approved-by: Sascha Eggenberger <seggenberger@gitlab.com>
Approved-by: Michael Lunøe <michael.lunoe@gmail.com>
Reviewed-by: Sascha Eggenberger <seggenberger@gitlab.com>
Co-authored-by: Chad Lavimoniere <clavimoniere@gitlab.com>

Include headers in LfsDownloadObject

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/153840



Merged-by: James Nutt <jnutt@gitlab.com>
Approved-by: James Nutt <jnutt@gitlab.com>
Co-authored-by: carlad-gl <cdrago@gitlab.com>

Adds the headers included in the github response so that
the authorization token can be passed in the request for
the file.

Changelog: fixed

Add and backfill namespace_id for design_management_repositories.

This table has a
[desired sharding key](https://docs.gitlab.com/ee/development/database/multiple_databases.html#define-a-desired_sharding_key-to-automatically-backfill-a-sharding_key)
configured ([view configuration](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/docs/design_management_repositories.yml)).

This merge request is the first step towards transforming the desired sharding key into a
[sharding key](https://docs.gitlab.com/ee/development/database/multiple_databases.html#defining-a-sharding-key-for-all-cell-local-tables).

This involves three changes:

- Adding a new column that will serve as the sharding key (along with the relevant index and foreign key).
- Populating the sharding key when new records are created by adding a database function and trigger.
- Scheduling a [batched background migration](https://docs.gitlab.com/ee/development/database/batched_background_migrations.html)
  to set the sharding key for existing records.

Once the background migration has completed, a second merge request will be created to finalize the background
migration and validate the not null constraint.

We have assigned a random backend engineer from ~"group::product planning" to review these changes. Please review this merge
request from a ~backend perspective. The main thing we are looking to verify is that the added column and association
match the values specified by the [desired sharding key](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/docs/design_management_repositories.yml)
configuration and that backfilling the column from this other table makes sense in the context of this feature.

When you are finished, please:

1. Trigger the [database testing pipeline](https://docs.gitlab.com/ee/development/database/database_migration_pipeline.html)
   as instructed by Danger.
1. Request a review from the ~backend maintainer and ~database reviewer suggested by Danger.

If you have any questions or concerns, reach out to @tigerwnz or @manojmj.

This merge request was generated by a once off keep implemented in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/143774

This change was generated by
[gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
using the Keeps::BackfillDesiredShardingKeySmallTable keep.

To provide feedback on your experience with `gitlab-housekeeper` please comment in
<https://gitlab.com/gitlab-org/gitlab/-/issues/442003>.

Changelog: other

Add database migration in preparation to add advanced scope tokens

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/153482



Merged-by: Adam Hegyi <ahegyi@gitlab.com>
Approved-by: Adam Hegyi <ahegyi@gitlab.com>
Co-authored-by: unset <fveillette@gitlab.com>

Skip groups query in @ autocomplete if not needed

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/153919



Merged-by: Pavel Shutsin <pshutsin@gitlab.com>
Approved-by: Pavel Shutsin <pshutsin@gitlab.com>
Co-authored-by: Heinrich Lee Yu <heinrich@gitlab.com>

Add and backfill namespace_id for design_management_designs

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/153149



Merged-by: Manoj M J <mmj@gitlab.com>
Approved-by: Manoj M J <mmj@gitlab.com>
Approved-by: Pavel Shutsin <pshutsin@gitlab.com>
Co-authored-by: Abhilash Kotte <akotte@gitlab.com>

Add and backfill namespace_id for design_management_designs.

This table has a
[desired sharding key](https://docs.gitlab.com/ee/development/database/multiple_databases.html#define-a-desired_sharding_key-to-automatically-backfill-a-sharding_key)
configured ([view configuration](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/docs/design_management_designs.yml)).

This merge request is the first step towards transforming the desired sharding key into a
[sharding key](https://docs.gitlab.com/ee/development/database/multiple_databases.html#defining-a-sharding-key-for-all-cell-local-tables).

This involves three changes:

- Adding a new column that will serve as the sharding key (along with the relevant index and foreign key).
- Populating the sharding key when new records are created by adding a database function and trigger.
- Scheduling a [batched background migration](https://docs.gitlab.com/ee/development/database/batched_background_migrations.html)
  to set the sharding key for existing records.

Once the background migration has completed, a second merge request will be created to finalize the background
migration and validate the not null constraint.

We have assigned a random backend engineer from ~"group::product planning" to review these changes. Please review this merge
request from a ~backend perspective. The main thing we are looking to verify is that the added column and association
match the values specified by the [desired sharding key](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/docs/design_management_designs.yml)
configuration and that backfilling the column from this other table makes sense in the context of this feature.

When you are finished, please:

1. Trigger the [database testing pipeline](https://docs.gitlab.com/ee/development/database/database_migration_pipeline.html)
   as instructed by Danger.
1. Request a review from the ~backend maintainer and ~database reviewer suggested by Danger.

If you have any questions or concerns, reach out to @tigerwnz or @manojmj.

This merge request was generated by a once off keep implemented in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/143774

This change was generated by
[gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
using the Keeps::BackfillDesiredShardingKeySmallTable keep.

To provide feedback on your experience with `gitlab-housekeeper` please comment in
<https://gitlab.com/gitlab-org/gitlab/-/issues/442003>.

Changelog: other

Remove gitops Deprecation Alert

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/154013



Merged-by: Anna Vovchenko <avovchenko@gitlab.com>
Approved-by: Anna Vovchenko <avovchenko@gitlab.com>
Reviewed-by: Anna Vovchenko <avovchenko@gitlab.com>
Co-authored-by: Andrew Fontaine <afontaine@gitlab.com>

As the deprecation has been completed, and the functionality turned off,
we can remove the alert.

Changelog: removed

Update dependency @gitlab/ui to v80.13.1

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/153872



Merged-by: Tomas Bulva <tbulva@gitlab.com>
Approved-by: Tomas Bulva <tbulva@gitlab.com>
Co-authored-by: GitLab Renovate Bot <gitlab-bot@gitlab.com>