Add latest changes from gitlab-org/gitlab@master

Author: GitLab Bot

app/graphql/types/mutation_type.rb

@@ -192,7 +192,10 @@ class MutationType < BaseObject
     mount_mutation Mutations::Ci::Runner::Create, experiment: { milestone: '15.10' }
     mount_mutation Mutations::Ci::Runner::Delete
     mount_mutation Mutations::Ci::Runner::Update
-    mount_mutation Mutations::Ci::RunnersRegistrationToken::Reset
+    mount_mutation Mutations::Ci::RunnersRegistrationToken::Reset, deprecated: {
+      reason: 'Underlying feature was deprecated in 15.6 and will be removed in 18.0',
+      milestone: '17.7'
+    }
     mount_mutation Mutations::Namespace::PackageSettings::Update
     mount_mutation Mutations::Groups::Update
     mount_mutation Mutations::UserCallouts::Create

data/deprecations/14-8-graphql-runner-active.yml

@@ -7,6 +7,7 @@
   # The stage and GitLab username of the person reporting the change,
   # and a link to the deprecation issue
   reporter: pedropombeiro
+  window: "3"
   stage: Verify
   issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/351109
   impact: low

data/deprecations/16-11-GITLAB_SHARED_RUNNERS_REGISTRATION_TOKEN.yml

@@ -7,6 +7,7 @@
   # The stage and GitLab username of the person reporting the change,
   # and a link to the deprecation issue
   reporter: pedropombeiro
+  window: "2"
   stage: Verify
   issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/453949
   impact: medium

data/deprecations/17-7-RunnersRegistrationTokenReset-mutation.yml

@@ -0,0 +1,35 @@
+- title: "RunnersRegistrationTokenReset GraphQL mutation is deprecated"
+  # The milestones for the deprecation announcement, and the removal.
+  removal_milestone: "18.0"
+  announcement_milestone: "17.7"
+  breaking_change: true
+  window: "2"
+  reporter: pedropombeiro
+  stage: Verify
+  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/505703
+  # Use the impact calculator https://gitlab-com.gitlab.io/gl-infra/breaking-change-impact-calculator/?
+  impact: high
+  scope: instance, group, project
+  resolution_role: Admin
+  manual_task: true
+  body: |  # (required) Don't change this line.
+    The support for runner registration tokens is deprecated. Consequently, the support for resetting a registration token has also been deprecated
+    and will be removed in GitLab 18.0.
+
+    A new method to bind runners to a GitLab instance has been implemented
+    as part of the new [GitLab Runner token architecture](https://docs.gitlab.com/ee/ci/runners/new_creation_workflow.html).
+    For details, see [epic 7633](https://gitlab.com/groups/gitlab-org/-/epics/7633).
+    This new architecture introduces a new method for registering runners and eliminates the legacy
+    [runner registration token](https://docs.gitlab.com/ee/security/token_overview.html#runner-registration-tokens).
+    In GitLab 18.0, only the runner registration methods implemented in the new GitLab Runner token architecture will be supported.
+#
+  # When support for this feature ends, in XX.YY milestone format.
+  end_of_support_milestone:
+  # Array of tiers the feature is currently available to,
+  # like [Free, Silver, Gold, Core, Premium, Ultimate]
+  tiers:
+  # Links to documentation and thumbnail image
+  documentation_url: https://docs.gitlab.com/ee/api/runners.html#register-a-new-runner  # (optional) This is a link to the current documentation page
+  image_url:
+  # Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
+  video_url:

doc/administration/dedicated/img/high_level_architecture_diagram_v18_0.png

@@ -8376,8 +8376,10 @@ Input type: `ProjectSecretCreateInput`
 
 | Name | Type | Description |
 | ---- | ---- | ----------- |
+| <a id="mutationprojectsecretcreatebranch"></a>`branch` | [`String!`](#string) | Branches that can access the secret. |
 | <a id="mutationprojectsecretcreateclientmutationid"></a>`clientMutationId` | [`String`](#string) | A unique identifier for the client performing the mutation. |
 | <a id="mutationprojectsecretcreatedescription"></a>`description` | [`String`](#string) | Description of the project secret. |
+| <a id="mutationprojectsecretcreateenvironment"></a>`environment` | [`String!`](#string) | Environments that can access the secret. |
 | <a id="mutationprojectsecretcreatename"></a>`name` | [`String!`](#string) | Name of the project secret. |
 | <a id="mutationprojectsecretcreateprojectpath"></a>`projectPath` | [`ID!`](#id) | Project of the secret. |
 | <a id="mutationprojectsecretcreatevalue"></a>`value` | [`String!`](#string) | Value of the project secret. |
@@ -9150,6 +9152,10 @@ Input type: `RunnersExportUsageInput`
 
 ### `Mutation.runnersRegistrationTokenReset`
 
+DETAILS:
+**Deprecated** in GitLab 17.7.
+Underlying feature was deprecated in 15.6 and will be removed in 18.0.
+
 Input type: `RunnersRegistrationTokenResetInput`
 
 #### Arguments
@@ -33339,7 +33345,9 @@ Representation of a project secret.
 
 | Name | Type | Description |
 | ---- | ---- | ----------- |
+| <a id="projectsecretbranch"></a>`branch` | [`String!`](#string) | Branches that can access the secret. |
 | <a id="projectsecretdescription"></a>`description` | [`String!`](#string) | Description of the project secret. |
+| <a id="projectsecretenvironment"></a>`environment` | [`String!`](#string) | Environments that can access the secret. |
 | <a id="projectsecretname"></a>`name` | [`String!`](#string) | Name of the project secret. |
 | <a id="projectsecretproject"></a>`project` | [`Project!`](#project) | Project the secret belong to. |
 

doc/administration/maintenance_mode/img/maintenance_mode_error_message_v17.6.png

@@ -0,0 +1,69 @@
+---
+stage: Data Access
+group: Database Frameworks
+info: Any user with at least the Maintainer role can merge updates to this content.
+---
+
+# Large tables limitations
+
+GitLab implements some limitations on large database tables to improve manageability for both GitLab and its customers. The list of tables subject to these limitations is defined in [`rubocop/rubocop-migrations.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/rubocop/rubocop-migrations.yml).
+
+## Table size restrictions
+
+The following limitations apply to table modifications on GitLab.com:
+
+| Action | Maximum size (including indexes) |
+| ------ | ------------------------------- |
+| Add an index | 50 GB |
+| Add a column with foreign key | 50 GB |
+| Add a new column | 100 GB |
+
+These limitations align with our goal to maintain [all tables under 100 GB](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/database_size_limits/) for improved [stability and performance](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/database_size_limits/#motivation-gitlabcom-stability-and-performance).
+
+## Exceptions
+
+Exceptions to these size limitations should only granted for the following cases:
+
+- Migrate a table's columns from `int4` to `int8`
+- Add a sharding key to support cells
+- Modify a table to assist in partitioning or data retention efforts
+- Replace an existing index to provide better query performance
+
+## Alternatives to table modifications
+
+Consider these alternatives when working with large tables:
+
+1. Creates a separate table for new columns, especially if the column is not present in all rows. The new table references the original table through a foreign key.
+1. Work with the Global Search team to add your data to Elasticsearch for enhanced filter/search functionality.
+1. Simplify filtering/sorting options (for example, use `id` instead of `created_at` for sorting).
+
+## Benefits of table size limitations
+
+Table size limitations provide several advantages:
+
+- Enable separate vacuum operations with different frequencies
+- Generate less Write-Ahead Log (WAL) data for column updates
+- Prevent unnecessary data copying during row updates
+
+For more information about data model trade-offs, see the [database documentation](layout_and_access_patterns.md#data-model-trade-offs).
+
+## Using `has_one` relationships
+
+When a table becomes too large for new columns, create a new table with a `has_one` relation. For example, in [merge request !170371](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/170371), we track the total weight count of an issue in a separate table.
+
+Benefits of this approach:
+
+1. Keeps the main table narrower, reducing data load from PostgreSQL
+1. Creates an efficient narrow table for specific queries
+1. Allows selective population of the new table as needed
+
+This approach is particularly effective when:
+
+- The new column applies to a subset of the main table
+- Only specific queries need the new data
+
+## Related links
+
+- [Database size limits](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/database_size_limits/#solutions)
+- [Adding database indexes](adding_database_indexes.md)
+- [Database layout and access patterns](layout_and_access_patterns.md#data-model-trade-offs)

doc/administration/settings/img/continuous_integration_instance_runner_details_v17_6.png

@@ -156,8 +156,8 @@ For features introduced behind feature flags, add details about the feature flag
 Remove history items and inline text that refer to unsupported versions.
 
 GitLab supports the current major version and two previous major versions.
-For example, if 16.0 is the current major version, all major and minor releases of
-GitLab 16.0, 15.0, and 14.0 are supported.
+For example, if 17.0 is the current major version, all major and minor releases of
+GitLab 17.0, 16.0, and 15.0 are supported.
 
 For the list of current supported versions, see [Version support](https://about.gitlab.com/support/statement-of-support/#version-support).
 

doc/api/graphql/reference/index.md

@@ -112,6 +112,10 @@ includes the timing information for migrations.
 | Post-deployment migrations | `<= 10 minutes` | A valid exception are schema changes, since they must not happen in background migrations. |
 | Background migrations | `> 10 minutes` | Since these are suitable for larger tables, it's not possible to set a precise timing guideline, however, any single query must stay below [`1 second` execution time](database/query_performance.md#timing-guidelines-for-queries) with cold caches. |
 
+## Large Tables Limitations
+
+For tables exceeding size thresholds, read our [large tables limitations](database/large_tables_limitations.md) before adding new columns or indexes.
+
 ## Decide which database to target
 
 GitLab connects to two different Postgres databases: `main` and `ci`. This split can affect migrations

doc/ci/img/get_started_cicd_v16_11.png

@@ -901,6 +901,30 @@ Occurrences of the `active` identifier in the GitLab GraphQL API endpoints will
 
 <div class="deprecation breaking-change" data-milestone="18.0">
 
+### RunnersRegistrationTokenReset GraphQL mutation is deprecated
+
+<div class="deprecation-notes">
+
+- Announced in GitLab <span class="milestone">17.7</span>
+- Removal in GitLab <span class="milestone">18.0</span> ([breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change))
+- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/505703).
+
+</div>
+
+The support for runner registration tokens is deprecated. Consequently, the support for resetting a registration token has also been deprecated
+and will be removed in GitLab 18.0.
+
+A new method to bind runners to a GitLab instance has been implemented
+as part of the new [GitLab Runner token architecture](https://docs.gitlab.com/ee/ci/runners/new_creation_workflow.html).
+For details, see [epic 7633](https://gitlab.com/groups/gitlab-org/-/epics/7633).
+This new architecture introduces a new method for registering runners and eliminates the legacy
+[runner registration token](https://docs.gitlab.com/ee/security/token_overview.html#runner-registration-tokens).
+In GitLab 18.0, only the runner registration methods implemented in the new GitLab Runner token architecture will be supported.
+
+</div>
+
+<div class="deprecation breaking-change" data-milestone="18.0">
+
 ### Slack notifications integration
 
 <div class="deprecation-notes">