diff options
42 files changed, 729 insertions, 545 deletions
diff --git a/.gitlab/issue_templates/Geo Replicate a new Git repository type.md b/.gitlab/issue_templates/Geo Replicate a new Git repository type.md index c63a5cb0032..ae5c6a054c0 100644 --- a/.gitlab/issue_templates/Geo Replicate a new Git repository type.md +++ b/.gitlab/issue_templates/Geo Replicate a new Git repository type.md @@ -391,7 +391,7 @@ That's all of the required database changes. - [ ] Make sure a Geo secondary site can request and download Cool Widgets on the Geo primary site. You may need to make some changes to `Gitlab::GitAccessCoolWidget`. For example, see [this change for Group-level Wikis](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/54914/diffs?commit_id=0f2b36f66697b4addbc69bd377ee2818f648dd33). -- [ ] Make sure a Geo secondary site can replicate Cool Widgets where repository does not exist on the Geo primary site. The only way to know about this is to parse the error text. You may need to make some changes to `Gitlab::CoolWidgetReplicator.no_repo_message` to return the proper error message. For example, see [this change for Group-level Wikis](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/74133). +- [ ] Make sure a Geo secondary site marks Cool Widgets as missing on primary when a repository does not exist on the Geo primary site. The only way to know about this is to parse the error text. You may need to make some changes to `Gitlab::CoolWidgetReplicator.no_repo_message` to return the proper error message. For example, see [this change for Group-level Wikis](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/74133). Alternatively, if a repository should *always* exist on the primary, then a Geo-specific workaround is to create an empty repository when verifying on primary. See examples for [project wikis](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/123869) and [design repositories](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/123917). - [ ] Generate the feature flag definition files by running the feature flag commands and following the command prompts: diff --git a/.rubocop_todo/layout/line_length.yml b/.rubocop_todo/layout/line_length.yml index 8c283bdf6ce..1deedbfc96e 100644 --- a/.rubocop_todo/layout/line_length.yml +++ b/.rubocop_todo/layout/line_length.yml @@ -3506,7 +3506,6 @@ Layout/LineLength: - 'spec/features/projects/settings/access_tokens_spec.rb' - 'spec/features/projects/settings/project_settings_spec.rb' - 'spec/features/projects/settings/registry_settings_spec.rb' - - 'spec/features/projects/settings/service_desk_setting_spec.rb' - 'spec/features/projects/settings/user_manages_merge_requests_settings_spec.rb' - 'spec/features/projects/settings/user_renames_a_project_spec.rb' - 'spec/features/projects/settings/visibility_settings_spec.rb' diff --git a/.rubocop_todo/rspec/any_instance_of.yml b/.rubocop_todo/rspec/any_instance_of.yml index e8cc0e77ca9..18c225fb9ec 100644 --- a/.rubocop_todo/rspec/any_instance_of.yml +++ b/.rubocop_todo/rspec/any_instance_of.yml @@ -112,7 +112,6 @@ RSpec/AnyInstanceOf: - 'spec/features/projects/container_registry_spec.rb' - 'spec/features/projects/files/user_browses_lfs_files_spec.rb' - 'spec/features/projects/jobs_spec.rb' - - 'spec/features/projects/settings/service_desk_setting_spec.rb' - 'spec/features/projects/show/user_sees_setup_shortcut_buttons_spec.rb' - 'spec/features/snippets/embedded_snippet_spec.rb' - 'spec/features/usage_stats_consent_spec.rb' diff --git a/.rubocop_todo/rspec/context_wording.yml b/.rubocop_todo/rspec/context_wording.yml index d32abc64f94..bc557ecf4c5 100644 --- a/.rubocop_todo/rspec/context_wording.yml +++ b/.rubocop_todo/rspec/context_wording.yml @@ -1281,7 +1281,6 @@ RSpec/ContextWording: - 'spec/features/projects/settings/project_settings_spec.rb' - 'spec/features/projects/settings/repository_settings_spec.rb' - 'spec/features/projects/settings/secure_files_spec.rb' - - 'spec/features/projects/settings/service_desk_setting_spec.rb' - 'spec/features/projects/settings/user_interacts_with_deploy_keys_spec.rb' - 'spec/features/projects/settings/visibility_settings_spec.rb' - 'spec/features/projects/settings/webhooks_settings_spec.rb' diff --git a/.rubocop_todo/rspec/return_from_stub.yml b/.rubocop_todo/rspec/return_from_stub.yml index 20e4112da62..e56d48037c4 100644 --- a/.rubocop_todo/rspec/return_from_stub.yml +++ b/.rubocop_todo/rspec/return_from_stub.yml @@ -101,7 +101,6 @@ RSpec/ReturnFromStub: - 'spec/features/projects/container_registry_spec.rb' - 'spec/features/projects/environments/environment_spec.rb' - 'spec/features/projects/pages/user_edits_lets_encrypt_settings_spec.rb' - - 'spec/features/projects/settings/service_desk_setting_spec.rb' - 'spec/finders/events_finder_spec.rb' - 'spec/finders/projects/groups_finder_spec.rb' - 'spec/finders/snippets_finder_spec.rb' diff --git a/app/assets/javascripts/analytics/usage_trends/components/users_chart.vue b/app/assets/javascripts/analytics/usage_trends/components/users_chart.vue index dfe94aeb884..06b83c87985 100644 --- a/app/assets/javascripts/analytics/usage_trends/components/users_chart.vue +++ b/app/assets/javascripts/analytics/usage_trends/components/users_chart.vue @@ -49,11 +49,13 @@ export default { return data.users?.nodes || []; }, result({ data }) { - const { - users: { pageInfo }, - } = data; - this.pageInfo = pageInfo; - this.fetchNextPage(); + if (data) { + const { + users: { pageInfo }, + } = data; + this.pageInfo = pageInfo; + this.fetchNextPage(); + } }, error(error) { this.handleError(error); diff --git a/app/assets/javascripts/diffs/components/settings_dropdown.vue b/app/assets/javascripts/diffs/components/settings_dropdown.vue index 2d9ac76b3e4..a705f29ff65 100644 --- a/app/assets/javascripts/diffs/components/settings_dropdown.vue +++ b/app/assets/javascripts/diffs/components/settings_dropdown.vue @@ -2,23 +2,22 @@ import { GlButtonGroup, GlButton, - GlDropdown, + GlDisclosureDropdown, GlFormCheckbox, - GlTooltipDirective, + GlTooltip, } from '@gitlab/ui'; import { mapActions, mapGetters, mapState } from 'vuex'; import { SETTINGS_DROPDOWN } from '../i18n'; export default { i18n: SETTINGS_DROPDOWN, - directives: { - GlTooltip: GlTooltipDirective, - }, + toggleId: 'js-show-diff-settings', components: { GlButtonGroup, GlButton, - GlDropdown, + GlDisclosureDropdown, GlFormCheckbox, + GlTooltip, }, computed: { ...mapGetters('diffs', ['isInlineView', 'isParallelView']), @@ -43,74 +42,87 @@ export default { </script> <template> - <gl-dropdown - v-gl-tooltip - icon="settings" - :title="$options.i18n.preferences" - :text="$options.i18n.preferences" - :text-sr-only="true" - :aria-label="$options.i18n.preferences" - :header-text="$options.i18n.preferences" - toggle-class="js-show-diff-settings" - right - > - <div class="gl-px-3"> - <span class="gl-font-weight-bold gl-display-block gl-mb-2">{{ __('File browser') }}</span> - <gl-button-group class="gl-display-flex"> - <gl-button - :class="{ selected: !renderTreeList }" - class="gl-w-half js-list-view" - @click="setRenderTreeList({ renderTreeList: false })" - > - {{ __('List view') }} - </gl-button> - <gl-button - :class="{ selected: renderTreeList }" - class="gl-w-half js-tree-view" - @click="setRenderTreeList({ renderTreeList: true })" - > - {{ __('Tree view') }} - </gl-button> - </gl-button-group> - </div> - <div class="gl-mt-3 gl-px-3"> - <span class="gl-font-weight-bold gl-display-block gl-mb-2">{{ __('Compare changes') }}</span> - <gl-button-group class="gl-display-flex js-diff-view-buttons"> - <gl-button - id="inline-diff-btn" - :class="{ selected: isInlineView }" - class="gl-w-half js-inline-diff-button" - data-view-type="inline" - @click="setInlineDiffViewType" - > - {{ __('Inline') }} - </gl-button> - <gl-button - id="parallel-diff-btn" - :class="{ selected: isParallelView }" - class="gl-w-half js-parallel-diff-button" - data-view-type="parallel" - @click="setParallelDiffViewType" - > - {{ __('Side-by-side') }} - </gl-button> - </gl-button-group> - </div> - <gl-form-checkbox - data-testid="show-whitespace" - class="gl-mt-3 gl-ml-3" - :checked="showWhitespace" - @input="toggleWhitespace" - > - {{ $options.i18n.whitespace }} - </gl-form-checkbox> - <gl-form-checkbox - data-testid="file-by-file" - class="gl-ml-3 gl-mb-0" - :checked="viewDiffsFileByFile" - @input="toggleFileByFile" + <div> + <gl-disclosure-dropdown + :toggle-class="$options.toggleId" + :toggle-id="$options.toggleId" + icon="settings" + :text="$options.i18n.preferences" + text-sr-only + :aria-label="$options.i18n.preferences" + placement="right" + :auto-close="false" > - {{ $options.i18n.fileByFile }} - </gl-form-checkbox> - </gl-dropdown> + <slot name="header"> + <span + class="gl-font-weight-bold gl-display-block gl-mb-3 gl-pb-2 gl-text-center gl-border-b" + >{{ $options.i18n.preferences }}</span + > + </slot> + <div class="gl-px-3"> + <span class="gl-font-weight-bold gl-display-block gl-mb-2">{{ __('File browser') }}</span> + <gl-button-group class="gl-display-flex"> + <gl-button + :class="{ selected: !renderTreeList }" + class="gl-w-half js-list-view" + @click="setRenderTreeList({ renderTreeList: false })" + > + {{ __('List view') }} + </gl-button> + <gl-button + :class="{ selected: renderTreeList }" + class="gl-w-half js-tree-view" + @click="setRenderTreeList({ renderTreeList: true })" + > + {{ __('Tree view') }} + </gl-button> + </gl-button-group> + </div> + <div class="gl-mt-3 gl-px-3"> + <span class="gl-font-weight-bold gl-display-block gl-mb-2">{{ + __('Compare changes') + }}</span> + <gl-button-group class="gl-display-flex js-diff-view-buttons"> + <gl-button + id="inline-diff-btn" + :class="{ selected: isInlineView }" + class="gl-w-half js-inline-diff-button" + data-view-type="inline" + @click="setInlineDiffViewType" + > + {{ __('Inline') }} + </gl-button> + <gl-button + id="parallel-diff-btn" + :class="{ selected: isParallelView }" + class="gl-w-half js-parallel-diff-button" + data-view-type="parallel" + @click="setParallelDiffViewType" + > + {{ __('Side-by-side') }} + </gl-button> + </gl-button-group> + </div> + <gl-form-checkbox + data-testid="show-whitespace" + class="gl-mt-3 gl-ml-3" + :checked="showWhitespace" + @input="toggleWhitespace" + > + {{ $options.i18n.whitespace }} + </gl-form-checkbox> + <gl-form-checkbox + data-testid="file-by-file" + class="gl-ml-3 gl-mb-0" + :checked="viewDiffsFileByFile" + @input="toggleFileByFile" + > + {{ $options.i18n.fileByFile }} + </gl-form-checkbox> + </gl-disclosure-dropdown> + + <gl-tooltip :target="$options.toggleId" triggers="hover">{{ + $options.i18n.preferences + }}</gl-tooltip> + </div> </template> diff --git a/app/assets/javascripts/sidebar/components/assignees/uncollapsed_assignee_list.vue b/app/assets/javascripts/sidebar/components/assignees/uncollapsed_assignee_list.vue index b424d9074d0..2240f8e1869 100644 --- a/app/assets/javascripts/sidebar/components/assignees/uncollapsed_assignee_list.vue +++ b/app/assets/javascripts/sidebar/components/assignees/uncollapsed_assignee_list.vue @@ -77,7 +77,7 @@ export default { v-for="(user, index) in uncollapsedUsers" :key="user.id" :class="{ - 'gl-mb-3': index !== users.length - 1, + 'gl-mb-3': index !== users.length - 1 || users.length > 5, }" class="assignee-grid gl-display-grid gl-align-items-center gl-w-full" > diff --git a/app/controllers/projects_controller.rb b/app/controllers/projects_controller.rb index 81f205a6457..71a34a40bd0 100644 --- a/app/controllers/projects_controller.rb +++ b/app/controllers/projects_controller.rb @@ -41,6 +41,7 @@ class ProjectsController < Projects::ApplicationController push_frontend_feature_flag(:remove_monitor_metrics, @project) push_frontend_feature_flag(:explain_code_chat, current_user) push_frontend_feature_flag(:ci_namespace_catalog_experimental, @project) + push_frontend_feature_flag(:service_desk_custom_email, @project) push_licensed_feature(:file_locks) if @project.present? && @project.licensed_feature_available?(:file_locks) push_licensed_feature(:security_orchestration_policies) if @project.present? && @project.licensed_feature_available?(:security_orchestration_policies) push_force_frontend_feature_flag(:work_items, @project&.work_items_feature_flag_enabled?) diff --git a/config/events/g_project_management_issue_created.yml b/config/events/g_project_management_issue_created.yml new file mode 100644 index 00000000000..0fe5dd5f82e --- /dev/null +++ b/config/events/g_project_management_issue_created.yml @@ -0,0 +1,24 @@ +--- +description: An issue has been created +category: InternalEventTracking +action: g_project_management_issue_created +label_description: +property_description: +value_description: +extra_properties: +identifiers: + - namespace + - project + - user +product_section: dev +product_stage: plan +product_group: project_management +milestone: "16.1" +introduced_by_url: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/123184 +distributions: + - ce + - ee +tiers: + - free + - premium + - ultimate diff --git a/data/deprecations/templates/_deprecation_template.md.erb b/data/deprecations/templates/_deprecation_template.md.erb index 1817942eac5..3735e43a96f 100644 --- a/data/deprecations/templates/_deprecation_template.md.erb +++ b/data/deprecations/templates/_deprecation_template.md.erb @@ -59,7 +59,7 @@ For deprecation reviewers (Technical Writers only): - End of Support: GitLab <span class="milestone"><%= deprecation["end_of_support_milestone"]%></span> <% end -%> <% if deprecation["breaking_change"] -%> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). <%- end -%> <% if deprecation["issue_url"] -%> - To discuss this change or learn more, see the [deprecation issue](<%= deprecation["issue_url"]%>). diff --git a/data/removals/16_1/.gitkeep b/data/removals/16_1/.gitkeep deleted file mode 100644 index e69de29bb2d..00000000000 --- a/data/removals/16_1/.gitkeep +++ /dev/null diff --git a/data/removals/templates/_removal_template.md.erb b/data/removals/templates/_removal_template.md.erb index aa2ae993f45..c3d7bc499d0 100644 --- a/data/removals/templates/_removal_template.md.erb +++ b/data/removals/templates/_removal_template.md.erb @@ -44,7 +44,7 @@ For removal reviewers (Technical Writers only): <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"><%= removal["announcement_milestone"]%></span> <% if removal["breaking_change"] -%> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. <%- end -%> <% if removal["issue_url"] -%> - To discuss this change or learn more, see the [deprecation issue](<%= removal["issue_url"]%>). diff --git a/db/post_migrate/20230622073752_ensure_backfill_ci_pipelines_bigint_id_is_completed.rb b/db/post_migrate/20230622073752_ensure_backfill_ci_pipelines_bigint_id_is_completed.rb new file mode 100644 index 00000000000..56aeafc0a66 --- /dev/null +++ b/db/post_migrate/20230622073752_ensure_backfill_ci_pipelines_bigint_id_is_completed.rb @@ -0,0 +1,23 @@ +# frozen_string_literal: true + +class EnsureBackfillCiPipelinesBigintIdIsCompleted < Gitlab::Database::Migration[2.1] + include Gitlab::Database::MigrationHelpers::ConvertToBigint + + restrict_gitlab_migration gitlab_schema: :gitlab_ci + disable_ddl_transaction! + + TABLE_NAME = :ci_pipelines + + def up + ensure_batched_background_migration_is_finished( + job_class_name: 'CopyColumnUsingBackgroundMigrationJob', + table_name: TABLE_NAME, + column_name: 'id', + job_arguments: [['id'], ['id_convert_to_bigint']] + ) + end + + def down + # no-op + end +end diff --git a/db/post_migrate/20230623073906_prepare_async_index_for_ci_pipelines_bigint_id.rb b/db/post_migrate/20230623073906_prepare_async_index_for_ci_pipelines_bigint_id.rb new file mode 100644 index 00000000000..57d4e37ca7c --- /dev/null +++ b/db/post_migrate/20230623073906_prepare_async_index_for_ci_pipelines_bigint_id.rb @@ -0,0 +1,15 @@ +# frozen_string_literal: true + +class PrepareAsyncIndexForCiPipelinesBigintId < Gitlab::Database::Migration[2.1] + TABLE_NAME = :ci_pipelines + INDEX_NAME = "index_#{TABLE_NAME}_on_id_convert_to_bigint" + + # TODO: Index to be created synchronously in https://gitlab.com/gitlab-org/gitlab/-/issues/397000 + def up + prepare_async_index TABLE_NAME, :id_convert_to_bigint, unique: true, name: INDEX_NAME + end + + def down + unprepare_async_index TABLE_NAME, :id_convert_to_bigint, unique: true, name: INDEX_NAME + end +end diff --git a/db/schema_migrations/20230622073752 b/db/schema_migrations/20230622073752 new file mode 100644 index 00000000000..5dcd11379dc --- /dev/null +++ b/db/schema_migrations/20230622073752 @@ -0,0 +1 @@ +0bf41a90a42bd448727459b22f94b24f78e933fc2f5d1f4b27cf37c40cc7bbe6
\ No newline at end of file diff --git a/db/schema_migrations/20230623073906 b/db/schema_migrations/20230623073906 new file mode 100644 index 00000000000..0783428a741 --- /dev/null +++ b/db/schema_migrations/20230623073906 @@ -0,0 +1 @@ +d76cadfee80a039889d8abe1a0d62f37db683d7c82f7b2bc9a5882af6c65cdf9
\ No newline at end of file diff --git a/doc/administration/geo/index.md b/doc/administration/geo/index.md index ae2cc262160..44782540fed 100644 --- a/doc/administration/geo/index.md +++ b/doc/administration/geo/index.md @@ -203,6 +203,7 @@ This list of limitations only reflects the latest version of GitLab. If you are - [Disaster recovery](disaster_recovery/index.md) for multi-secondary sites causes downtime due to the complete re-synchronization and re-configuration of all non-promoted secondaries. - For Git over SSH, to make the project clone URL display correctly regardless of which site you are browsing, secondary sites must use the same port as the primary. [GitLab issue #339262](https://gitlab.com/gitlab-org/gitlab/-/issues/339262) proposes to remove this limitation. - Git push over SSH against a secondary site does not work for pushes over 1.86 GB. [GitLab issue #413109](https://gitlab.com/gitlab-org/gitlab/-/issues/413109) tracks this bug. +- Backups [cannot be run on secondaries](replication/troubleshooting.md#message-error-canceling-statement-due-to-conflict-with-recovery). ### Limitations on replication/verification diff --git a/doc/administration/geo/replication/troubleshooting.md b/doc/administration/geo/replication/troubleshooting.md index 4047167e4af..641170bf425 100644 --- a/doc/administration/geo/replication/troubleshooting.md +++ b/doc/administration/geo/replication/troubleshooting.md @@ -1404,6 +1404,27 @@ In this case, make sure to update the changed URL on all your sites: 1. On the left sidebar, select **Geo > Sites**. 1. Change the URL and save the change. +### Message: `ERROR: canceling statement due to conflict with recovery` during backup + +Running a backup on a Geo **secondary** [is not supported](https://gitlab.com/gitlab-org/gitlab/-/issues/211668). + +When running a backup on a **secondary** you might encounter the following error message: + +```plaintext +Dumping PostgreSQL database gitlabhq_production ... +pg_dump: error: Dumping the contents of table "notes" failed: PQgetResult() failed. +pg_dump: error: Error message from server: ERROR: canceling statement due to conflict with recovery +DETAIL: User query might have needed to see row versions that must be removed. +pg_dump: error: The command was: COPY public.notes (id, note, [...], last_edited_at) TO stdout; +``` + +To prevent a database backup being made automatically during GitLab upgrades on your Geo **secondaries**, +create the following empty file: + +```shell +sudo touch /etc/gitlab/skip-auto-backup +``` + ## Fixing non-PostgreSQL replication failures If you notice replication failures in `Admin > Geo > Sites` or the [Sync status Rake task](#sync-status-rake-task), you can try to resolve the failures with the following general steps: diff --git a/doc/api/group_access_tokens.md b/doc/api/group_access_tokens.md index 446aa3668d8..9234a116969 100644 --- a/doc/api/group_access_tokens.md +++ b/doc/api/group_access_tokens.md @@ -81,7 +81,8 @@ curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/a ## Create a group access token -> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/77236) in GitLab 14.7. +> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/77236) in GitLab 14.7. +> - The `expires_at` attribute default was [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/120213) in GitLab 16.0. Create a [group access token](../user/group/settings/group_access_tokens.md). You must have the Owner role for the group to create group access tokens. @@ -96,7 +97,7 @@ POST groups/:id/access_tokens | `name` | String | yes | Name of the group access token | | `scopes` | `Array[String]` | yes | [List of scopes](../user/group/settings/group_access_tokens.md#scopes-for-a-group-access-token) | | `access_level` | Integer | no | Access level. Valid values are `10` (Guest), `20` (Reporter), `30` (Developer), `40` (Maintainer), and `50` (Owner). | -| `expires_at` | Date | no | Token expires at midnight UTC on that date | +| `expires_at` | Date | no | Expiration date of the access token in ISO format (`YYYY-MM-DD`). If no date is set, the expiration is set to the [maximum allowable lifetime of an access token](../user/profile/personal_access_tokens.md#when-personal-access-tokens-expire). | ```shell curl --request POST --header "PRIVATE-TOKEN: <your_access_token>" \ diff --git a/doc/api/project_access_tokens.md b/doc/api/project_access_tokens.md index 437bdaa70f4..e52804e30da 100644 --- a/doc/api/project_access_tokens.md +++ b/doc/api/project_access_tokens.md @@ -84,6 +84,7 @@ curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/a > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/55408) in GitLab 13.10. > - The `token` attribute was [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/55408) in GitLab 13.10. +> - The `expires_at` attribute default was [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/120213) in GitLab 16.0. Create a [project access token](../user/project/settings/project_access_tokens.md). @@ -105,7 +106,7 @@ POST projects/:id/access_tokens | `name` | String | yes | Name of the project access token | | `scopes` | `Array[String]` | yes | [List of scopes](../user/project/settings/project_access_tokens.md#scopes-for-a-project-access-token) | | `access_level` | Integer | no | Access level. Valid values are `10` (Guest), `20` (Reporter), `30` (Developer), `40` (Maintainer), and `50` (Owner). Defaults to `40`. | -| `expires_at` | Date | no | Token expires at midnight UTC on that date | +| `expires_at` | Date | no | Expiration date of the access token in ISO format (`YYYY-MM-DD`). If no date is set, the expiration is set to the [maximum allowable lifetime of an access token](../user/profile/personal_access_tokens.md#when-personal-access-tokens-expire). | ```shell curl --request POST --header "PRIVATE-TOKEN: <your_access_token>" \ diff --git a/doc/api/users.md b/doc/api/users.md index 7b418e7a08b..ed788600e62 100644 --- a/doc/api/users.md +++ b/doc/api/users.md @@ -2051,6 +2051,7 @@ curl --request DELETE --header "PRIVATE-TOKEN: <your_access_token>" "https://git > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/17176) in GitLab 13.6. > - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/267553) in GitLab 13.8. +> - The `expires_at` attribute default was [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/120213) in GitLab 16.0. Use this API to create a new personal access token. Token values are returned once so, make sure you save it as you can't access it again. This API can only be used by @@ -2064,7 +2065,7 @@ POST /users/:user_id/personal_access_tokens | ------------ | ------- | -------- | ------------------------------------------------------------------------------------------------------------------------ | | `user_id` | integer | yes | ID of the user | | `name` | string | yes | Name of the personal access token | -| `expires_at` | date | no | Expiration date of the personal access token in ISO format (`YYYY-MM-DD`) | +| `expires_at` | date | no | Expiration date of the access token in ISO format (`YYYY-MM-DD`). If no date is set, the expiration is set to the [maximum allowable lifetime of an access token](../user/profile/personal_access_tokens.md#when-personal-access-tokens-expire). | | `scopes` | array | yes | Array of scopes of the personal access token. See [personal access token scopes](../user/profile/personal_access_tokens.md#personal-access-token-scopes) for possible values. | ```shell diff --git a/doc/development/database/batched_background_migrations.md b/doc/development/database/batched_background_migrations.md index 5aca74acc56..21689472e04 100644 --- a/doc/development/database/batched_background_migrations.md +++ b/doc/development/database/batched_background_migrations.md @@ -289,22 +289,27 @@ turn can be handled by defining foreign keys with cascading deletes. ### Requeuing batched background migrations -If one of the batched background migrations contains a bug that is fixed in a patch -release, you must requeue the batched background migration so the migration -repeats on systems that already performed the initial migration. - -When you requeue the batched background migration, turn the original -queuing into a no-op by clearing up the `#up` and `#down` methods of the -migration performing the requeuing. Otherwise, the batched background migration is -queued multiple times on systems that are upgrading multiple patch releases at -once. - -When you start the second post-deployment migration, delete the -previously batched migration with the provided code: - -```ruby -delete_batched_background_migration(MIGRATION_NAME, TABLE_NAME, COLUMN, JOB_ARGUMENTS) -``` +A batched background migration might need to be re-run for one of several +reasons: + +- The migration contains a bug ([example](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/93546)). +- The migration cleaned up data but the data became de-normalized again due to a + bypass in application logic ([example](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/123002)). +- The batch size of the original migration causes the migration to fail ([example](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/121404)). + +To requeue a batched background migration, you must: + +- No-op the contents of the `#up` and `#down` methods of the + original migration file. Otherwise, the batched background migration is created, + deleted, then created again on systems that are upgrading multiple patch + releases at once. +- Add a new post-deployment migration that re-runs the batched background + migration. +- In the new post-deployment migration, delete the existing batched background + migration using the `delete_batched_background_migration` method at the start + of the `#up` method to ensure that any existing runs are cleaned up. +- Update the `db/docs/batched_background_migration/*.yml` file from the original + migration to include information about the requeue. ## Cleaning up diff --git a/doc/update/deprecations.md b/doc/update/deprecations.md index 709b966d46b..5703620b688 100644 --- a/doc/update/deprecations.md +++ b/doc/update/deprecations.md @@ -54,7 +54,7 @@ For deprecation reviewers (Technical Writers only): <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/390424). </div> @@ -68,7 +68,7 @@ Due to low customer usage, Accessibility Testing is deprecated and will be remov <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/369117). </div> @@ -85,7 +85,7 @@ next major release, GitLab 16.0. This gem sees very little use and its <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/211643). </div> @@ -101,7 +101,7 @@ Because Cloud Native Buildpacks do not support automatic testing, the Auto Test <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/388719). </div> @@ -115,7 +115,7 @@ Due to limited customer usage, Browser Performance Testing is deprecated and wil <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/372117). </div> @@ -130,7 +130,7 @@ If you rely on the order of the returned projects to be `id_asc`, change your sc <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/409332). </div> @@ -145,7 +145,7 @@ the aliasing for the `CiRunnerUpgradeStatusType` type will be removed. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/383467). </div> @@ -162,7 +162,7 @@ These three variables will be removed in GitLab 17.0. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">16.1</span> - End of Support: GitLab <span class="milestone">17.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/414864). </div> @@ -190,7 +190,7 @@ The runner's legacy escape sequence mechanism to handle variable expansion imple <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/390855). </div> @@ -205,7 +205,7 @@ major release, GitLab 17.0. This gem sees very little use and is better suited f <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/groups/gitlab-org/-/epics/9661). </div> @@ -231,7 +231,7 @@ To avoid any disruptions, you should replace `filepath` with `direct_asset_path` <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/charts/gitlab/-/issues/4097). </div> @@ -252,7 +252,7 @@ Because the new values provide a streamlined, comprehensive method to enable TLS <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/387937). </div> @@ -269,7 +269,7 @@ are deprecated and will be removed from the GraphQL API. For installation instru <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.6</span> - End of Support: GitLab <span class="milestone">17.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/382077). </div> @@ -292,7 +292,7 @@ This change is a breaking change. You should use an [authentication token](../ci <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">16.1</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/414236). </div> @@ -308,7 +308,7 @@ Use `dependencyProxyTotalSizeBytes` instead, introduced in GitLab 16.1. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/409333). </div> @@ -323,7 +323,7 @@ the aliasing for the `RunnerMembershipFilter` type will be removed. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/385636). </div> @@ -337,7 +337,7 @@ In GitLab 17.0, the `DISABLED_WITH_OVERRIDE` value of the `SharedRunnersSetting` <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/388723). </div> @@ -351,7 +351,7 @@ Due to low customer usage, Load Performance Testing is deprecated and will be re <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/370471). </div> @@ -373,7 +373,7 @@ settings for the group using either the GitLab UI or GraphQL API. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/289956). </div> @@ -389,7 +389,7 @@ In milestone 17.0, we will remove the `pipelines` attribute from the API respons <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.1</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/343475). </div> @@ -404,7 +404,7 @@ The [`project_fingerprint`](https://gitlab.com/groups/gitlab-org/-/epics/2791) a <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">16.0</span> - End of Support: GitLab <span class="milestone">17.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/groups/gitlab-org/-/epics/9065). </div> @@ -425,7 +425,7 @@ PostgreSQL 14 will also be supported for instances that want to upgrade prior to <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> - End of Support: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/390787). </div> @@ -444,7 +444,7 @@ While the above approach is recommended for most instances, Sidekiq can also be <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.6</span> - End of Support: GitLab <span class="milestone">17.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/379743). </div> @@ -474,7 +474,7 @@ This change is a breaking change. You should [create a runner in the UI](../ci/r <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.6</span> - End of Support: GitLab <span class="milestone">17.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/380872). </div> @@ -501,7 +501,7 @@ This change is a breaking change. You should [create a runner in the UI](../ci/r <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/389467). </div> @@ -518,7 +518,7 @@ that is available now. We recommend this alternative solution because it provide <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">16.1</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/411239). </div> @@ -532,7 +532,7 @@ The option to run self-managed installations of GitLab on a single database is n <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/groups/gitlab-org/configure/-/epics/8). </div> @@ -558,7 +558,7 @@ For updates and details about this deprecation, follow [this epic](https://gitla <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/387898). </div> @@ -582,7 +582,7 @@ automatically from GitLab 16.0 onwards. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> - End of Support: GitLab <span class="milestone">17.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/372411). </div> @@ -602,7 +602,7 @@ we'll be introducing support in [this epic](https://gitlab.com/groups/gitlab-org <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.7</span> - End of Support: GitLab <span class="milestone">17.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/383341). </div> @@ -629,7 +629,7 @@ From GitLab 17.0 and later, the runner registration methods implemented by the n <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/390263). </div> @@ -643,7 +643,7 @@ We will be transitioning to a new IID as a result of moving requirements to a [w <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/387751). </div> @@ -658,7 +658,7 @@ Due to limited customer usage and capabilities, the Visual Reviews feature for R <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.7</span> - End of Support: GitLab <span class="milestone">17.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/385235). </div> @@ -672,7 +672,7 @@ The [`gitlab-runner exec`](https://docs.gitlab.com/runner/commands/#gitlab-runne <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/285493). </div> @@ -686,7 +686,7 @@ In some cases, like when a downstream pipeline had the `passed with warnings` st <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">16.1</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/groups/gitlab-org/-/epics/9662). </div> @@ -706,7 +706,7 @@ You can still access unified approval rules with the API. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.4</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/372332). </div> @@ -724,7 +724,7 @@ removed in 17.0. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.6</span> - End of Support: GitLab <span class="milestone">17.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/381111). </div> @@ -744,7 +744,7 @@ From GitLab 17.0 and later, the methods to register runners introduced by the ne <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/398132). </div> @@ -790,7 +790,7 @@ We hope this will simplify infrastructure setup and add several improvements to <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.1</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/343475). </div> @@ -822,7 +822,7 @@ Enabling the `ldap_settings_unlock_groups_by_owners` feature flag allowed non-LD <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/366798). </div> @@ -851,7 +851,7 @@ In GitLab 16.0 and later: <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/366798). </div> @@ -899,7 +899,7 @@ be available in CI/CD jobs. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">16.0</span> - End of Support: GitLab <span class="milestone">16.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/omnibus-gitlab/-/issues/7772). </div> @@ -924,7 +924,7 @@ However, enabling the bundled Grafana will no longer work from GitLab 16.3. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/387561). </div> @@ -974,7 +974,7 @@ We will stop publishing runner images based on the following, end-of-life Alpine <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/343988). </div> @@ -993,7 +993,7 @@ set the `POSTGRES_ENABLED` CI/CD variable to `true`. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/container-registry/-/issues/854). </div> @@ -1011,7 +1011,7 @@ This breaking change will happen in GitLab 16.0. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/charts/gitlab/-/issues/4353). </div> @@ -1034,7 +1034,7 @@ and [connect Grafana to the GitLab UI](https://docs.gitlab.com/ee/administration <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/369127). </div> @@ -1050,7 +1050,7 @@ release, GitLab 16.0. This gem sees very little use and its lack of upstream mai <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/353080). </div> @@ -1064,7 +1064,7 @@ When using the native HashiCorp Vault integration, CI/CD jobs will fail when no <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/408396). </div> @@ -1081,7 +1081,7 @@ Instead of changing which single module would be scanned, we [improved multi-mod <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/353097). </div> @@ -1097,7 +1097,7 @@ Instead, use the [`/approval_rules` endpoint](https://docs.gitlab.com/ee/api/mer <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/384455). </div> @@ -1114,7 +1114,7 @@ This unintended functionality is deprecated in GitLab 15.8 and will be removed i <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.6</span> - End of Support: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/379064). </div> @@ -1128,7 +1128,7 @@ From GitLab 13.6, users can [specify any runner configuration in the GitLab Runn <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/388255). </div> @@ -1146,7 +1146,7 @@ config file locations instead, for example `config/redis.cache.yml` or <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/container-registry/-/issues/842). </div> @@ -1160,7 +1160,7 @@ The Container Registry [pull-through cache](https://docs.docker.com/registry/rec <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.4</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/371840). </div> @@ -1174,7 +1174,7 @@ All Container Scanning variables that are prefixed by `DOCKER_` in variable name <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/387299). </div> @@ -1190,7 +1190,7 @@ to continue to use the GitLab for Jira Cloud app. Without OAuth, you can't manag <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/384198). </div> @@ -1204,7 +1204,7 @@ With the move to the new DAST API analyzer and the `DAST-API.gitlab-ci.yml` temp <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/383467). </div> @@ -1224,7 +1224,7 @@ These two variables will be removed in GitLab 16.0. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/384340). </div> @@ -1240,7 +1240,7 @@ These three variables will be removed in GitLab 16.0. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/395708). </div> @@ -1262,7 +1262,7 @@ To prepare for this change, users on GitLab.com or self-managed GitLab 15.9 or l <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/387560). </div> @@ -1276,7 +1276,7 @@ GitLab has deprecated Dependency Scanning support for Java versions 13, 14, 15, <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/328500). </div> @@ -1290,7 +1290,7 @@ The Deployment API will now return an error when `updated_at` filtering and `upd <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/352609). </div> @@ -1308,7 +1308,7 @@ GitLab instances that use `GIT_CONFIG_SYSTEM` and `GIT_CONFIG_GLOBAL` to configu <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/omnibus-gitlab/-/issues/7278). </div> @@ -1329,7 +1329,7 @@ For more information, see [the deprecation notes for Consul 1.9.0](https://githu <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> - End of Support: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/391896). </div> @@ -1343,7 +1343,7 @@ The [`CI_PRE_CLONE_SCRIPT` variable](https://docs.gitlab.com/ee/ci/runners/saas/ <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/387891). </div> @@ -1359,7 +1359,7 @@ will be able to import projects to that group. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/375505). </div> @@ -1373,7 +1373,7 @@ In GitLab 16.0 the GitLab Dependency Scanning analyzer will begin reporting deve <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/389477). </div> @@ -1388,7 +1388,7 @@ We intend to replace this feature with the ability to [embed charts](https://git <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/372770). </div> @@ -1410,7 +1410,7 @@ Users on self-managed instances should update their pipelines to ensure they do <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/382532). </div> @@ -1424,7 +1424,7 @@ From GitLab 16.0, when you search for environments with the API, you must use at <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). </div> In the [GraphQL API](https://docs.gitlab.com/ee/api/graphql/), the `external` field of [`ReleaseAssetLink` type](https://docs.gitlab.com/ee/api/graphql/reference/index.html#releaseassetlink) was used to indicate whether a [release link](https://docs.gitlab.com/ee/user/project/releases/release_fields.html#links) is internal or external to your GitLab instance. @@ -1439,7 +1439,7 @@ To avoid any disruptions to your workflow, please stop using the `external` fiel <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). </div> In [Releases API](https://docs.gitlab.com/ee/api/releases/) and [Release Links API](https://docs.gitlab.com/ee/api/releases/links.html), the `external` field was used to indicate whether a [release link](https://docs.gitlab.com/ee/user/project/releases/release_fields.html#links) is internal or external to your GitLab instance. @@ -1470,7 +1470,7 @@ GitLab 16.0. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/348909). </div> @@ -1503,7 +1503,7 @@ See [migrated group items](https://docs.gitlab.com/ee/user/group/import/#migrate <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/344648). </div> @@ -1524,7 +1524,7 @@ When checking if a runner is `paused`, API users are advised to check the boolea <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/360545). </div> @@ -1543,7 +1543,7 @@ be present during the 16.x cycle to avoid breaking the API signature, and will b <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/371485). </div> @@ -1557,7 +1557,7 @@ The `confidential` field for a `Note` will be deprecated and renamed to `interna <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.1</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/groups/gitlab-org/-/epics/7508). </div> @@ -1574,7 +1574,7 @@ The Jira DVCS connector is also deprecated for Jira 8.13 and earlier. You can on <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.7</span> - End of Support: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/383039). </div> @@ -1589,7 +1589,7 @@ This port is used for much more than just metrics, which warranted this change t <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/393574). </div> @@ -1612,7 +1612,7 @@ You should update to the new configuration structure as soon as possible using <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/390291). </div> @@ -1634,7 +1634,7 @@ didn't match. The change improves consistency between Omnibus GitLab and source <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/214217). </div> @@ -1654,7 +1654,7 @@ Update any scripts or bookmarks that reference the legacy URLs. GitLab APIs are <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/390417). </div> @@ -1668,7 +1668,7 @@ The [License-Check feature](https://docs.gitlab.com/ee/user/compliance/license_c <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/387721). </div> @@ -1682,7 +1682,7 @@ With external authorization enabled, personal access tokens (PATs) and deploy to <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/charts/gitlab/-/issues/3442). </div> @@ -1704,7 +1704,7 @@ The full GitLab Helm Chart 7.0 upgrade steps will be available in the [upgrade d <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/390417). </div> @@ -1734,7 +1734,7 @@ The [**Maximum number of active pipelines per project** limit](https://docs.gitl <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/346541). </div> @@ -1749,7 +1749,7 @@ However, since certificate-based integration with Kubernetes clusters is depreca <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.4</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/369122). </div> @@ -1776,7 +1776,7 @@ default is applied: <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/388269). </div> @@ -1797,7 +1797,7 @@ and `config/redis.shared_state.yml` files. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/389557). </div> @@ -1815,7 +1815,7 @@ The option to delete groups and projects immediately by default was deprecated t <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.1</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/346335). </div> @@ -1829,7 +1829,7 @@ Previously, the [PipelineSecurityReportFinding GraphQL type was updated](https:/ <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/349185). </div> @@ -1849,7 +1849,7 @@ Support for PostgreSQL 13 was added to Geo in GitLab 15.2. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/385798). </div> @@ -1893,7 +1893,7 @@ Alternatives to using the `gitlab:import:repos` Rake task include: <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.3</span> - End of Support: GitLab <span class="milestone">15.6</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/331468). </div> @@ -1909,7 +1909,7 @@ If you are using your own Redis 5.0 instance, you should upgrade it to Redis 6.0 <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.2</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/334253). </div> @@ -1925,7 +1925,7 @@ This could be a breaking change for anyone that developed their own runner that <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/390416). </div> @@ -1965,7 +1965,7 @@ Work to replace the PHPCS Security Audit-based analyzer is tracked in [issue 364 <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/390912). </div> @@ -2008,7 +2008,7 @@ Specifically, the following are being deprecated and will no longer be updated a <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/391822). </div> @@ -2043,7 +2043,7 @@ However, due to compatibility issues [discussed in the deprecation issue](https: <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/366477). </div> @@ -2064,7 +2064,7 @@ For more information, refer to [security report validation](https://docs.gitlab. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.7</span> - End of Support: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/377824). </div> @@ -2079,7 +2079,7 @@ and will be moved to the JiHu GitLab codebase. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.4</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/368828). </div> @@ -2093,7 +2093,7 @@ GitLab's operational container scanning capabilities no longer require starboard <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/390266). </div> @@ -2116,7 +2116,7 @@ This may require updating your metrics collection targets to also scrape `/db_me <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.7</span> - End of Support: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/385564). </div> @@ -2140,7 +2140,7 @@ To use the full state name, including the period, [migrate to the full state fil <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/382129). </div> @@ -2165,7 +2165,7 @@ This change affects the following REST and GraphQL API endpoints: <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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-com/Product/-/issues/4894). </div> @@ -2179,7 +2179,7 @@ The [Phabricator task importer](https://docs.gitlab.com/ee/user/project/import/p <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/386001). </div> @@ -2202,7 +2202,7 @@ To accommodate the changes, you might need to adjust the [`rules`](https://docs. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.4</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/365365). </div> @@ -2216,7 +2216,7 @@ In order to make the behavior of toggling the draft status of a merge request mo <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/350670). </div> @@ -2230,7 +2230,7 @@ Toggling notes confidentiality with REST and GraphQL APIs is being deprecated. U <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/367166). </div> @@ -2245,7 +2245,7 @@ You can use the vulnerabilityFindingDismiss GraphQL mutation to set the status o <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> - End of Support: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/376216). </div> @@ -2267,7 +2267,7 @@ Moving forward, we'll continue to invest in developing and releasing new feature <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/393836). </div> @@ -2289,7 +2289,7 @@ In GitLab 16.0 we will remove the ability to use a global ID in the work items p <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.7</span> - End of Support: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/377825). </div> @@ -2304,7 +2304,7 @@ and will be moved to the JiHu GitLab codebase. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/352957). </div> @@ -2333,7 +2333,7 @@ The predefined CI/CD variables that start with `CI_BUILD_*` were deprecated in G <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/381669). </div> @@ -2347,7 +2347,7 @@ The `POST ci/lint` API endpoint is deprecated in 15.7, and will be removed in 16 <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/365939). </div> @@ -2361,7 +2361,7 @@ To avoid confusion and duplication, the `environment_tier` parameter is deprecat <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/334018). </div> @@ -2381,7 +2381,7 @@ We plan to continue to support the `started` state in REST API version until the <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/375645). </div> @@ -2423,7 +2423,7 @@ Starting in GitLab 15.7 we started providing packages for openSUSE Leap 15.4, an <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> - End of Support: GitLab <span class="milestone">15.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/387976). </div> @@ -2445,7 +2445,7 @@ We are deprecating support for [uploading backups to remote storage](https://doc <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/383889). </div> @@ -2459,7 +2459,7 @@ The Live Preview feature of the Web IDE was intended to provide a client-side pr <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/groups/gitlab-org/configure/-/epics/8). </div> @@ -2488,7 +2488,7 @@ GitLab self-managed customers can still use the feature [with a feature flag](ht <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/29407). </div> @@ -2551,7 +2551,7 @@ This is not expected to cause any incompatibilities with the previous version of <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/352554). </div> @@ -2654,7 +2654,7 @@ Long term service and support (LTSS) for [Debian 9 Stretch ends in July 2022](ht <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/337993). </div> @@ -2672,7 +2672,7 @@ dramatically slow down GitLab instances. For this reason, they are being removed <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/26600). </div> @@ -2693,7 +2693,7 @@ GitLab will publish additional guidance to assist affected customers in migratin <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.6</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/342800). </div> @@ -2707,7 +2707,7 @@ In GitLab 15.0 we are going to limit the number of characters in CI/CD job names <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/345347). </div> @@ -2725,7 +2725,7 @@ Administrators who need to add runners for multiple projects can register a runn <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). </div> All functionality related to GitLab's Container Network Security and Container Host Security categories is deprecated in GitLab 14.8 and scheduled for removal in GitLab 15.0. Users who need a replacement for this functionality are encouraged to evaluate the following open source projects as potential solutions that can be installed and managed outside of GitLab: [AppArmor](https://gitlab.com/apparmor/apparmor), [Cilium](https://github.com/cilium/cilium), [Falco](https://github.com/falcosecurity/falco), [FluentD](https://github.com/fluent/fluentd), [Pod Security Admission](https://kubernetes.io/docs/concepts/security/pod-security-admission/). To integrate these technologies into GitLab, add the desired Helm charts into your copy of the [Cluster Management Project Template](https://docs.gitlab.com/ee/user/clusters/management_project_template.html). Deploy these Helm charts in production by calling commands through GitLab [CI/CD](https://docs.gitlab.com/ee/user/clusters/agent/ci_cd_workflow.html). @@ -2816,7 +2816,7 @@ in the Vulnerability Report. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/334060). </div> @@ -2848,7 +2848,7 @@ gemnasium-python-dependency_scanning: <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). </div> In GitLab 15.0, for Dependency Scanning, the default version of Java that the scanner expects will be updated from 11 to 17. Java 17 is [the most up-to-date Long Term Support (LTS) version](https://en.wikipedia.org/wiki/Java_version_history). Dependency scanning continues to support the same [range of versions (8, 11, 13, 14, 15, 16, 17)](https://docs.gitlab.com/ee/user/application_security/dependency_scanning/#supported-languages-and-package-managers), only the default version is changing. If your project uses the previous default of Java 11, be sure to [set the `DS_Java_Version` variable to match](https://docs.gitlab.com/ee/user/application_security/dependency_scanning/#configuring-specific-analyzers-used-by-dependency-scanning). @@ -2930,7 +2930,7 @@ The following `geo:db:*` tasks will be replaced with their corresponding `db:*:g <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/262019). </div> @@ -2944,7 +2944,7 @@ The feature flag `PUSH_RULES_SUPERSEDE_CODE_OWNERS` is being removed in GitLab 1 <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/350275). </div> @@ -2987,7 +2987,7 @@ in the Vulnerability Report. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). </div> The [external status check API](https://docs.gitlab.com/ee/api/status_checks.html) was originally implemented to @@ -3026,7 +3026,7 @@ In 15.0, support for daemon mode for GitLab Pages will be removed. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/groups/gitlab-org/configure/-/epics/6). </div> @@ -3058,7 +3058,7 @@ and will remove it in GitLab 15.0 <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/257883). </div> @@ -3122,7 +3122,7 @@ an inline argument expression). <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). </div> The GitLab Package stage offers a Package Registry, Container Registry, and Dependency Proxy to help you manage all of your dependencies using GitLab. Each of these product categories has a variety of settings that can be adjusted using the API. @@ -3142,7 +3142,7 @@ The permissions model for GraphQL is being updated. After 15.0, users with the G <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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-runner/-/issues/28192). </div> @@ -3158,7 +3158,7 @@ In GitLab 15.0 and later, the default value for this configuration option will c <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.6</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/335707). </div> @@ -3174,7 +3174,7 @@ If you are using our License Compliance API you should stop using the `approved` <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/338182). </div> @@ -3192,7 +3192,7 @@ This deprecation mainly impacts users compiling GitLab from source because Omnib <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/346485). </div> @@ -3218,7 +3218,7 @@ The [`custom_hooks_dir`](https://docs.gitlab.com/ee/administration/server_hooks. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). </div> The OAuth implicit grant authorization flow will be removed in our next major release, GitLab 15.0. Any applications that use OAuth implicit grant should switch to alternative [supported OAuth flows](https://docs.gitlab.com/ee/api/oauth2.html). @@ -3231,7 +3231,7 @@ The OAuth implicit grant authorization flow will be removed in our next major re <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). </div> By default, all new applications expire access tokens after 2 hours. In GitLab 14.2 and earlier, OAuth access tokens @@ -3252,7 +3252,7 @@ tokens before GitLab 15.0 is released: <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/337384). </div> @@ -3270,7 +3270,7 @@ Note that we are not deprecating the Kerberos SPNEGO integration, only the old p <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/351962). </div> @@ -3286,7 +3286,7 @@ Unexpected behavior in a security feature is inherently dangerous, so we have de <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/351963). </div> @@ -3302,7 +3302,7 @@ Unexpected behavior in a security feature is inherently dangerous, so we have de <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/352549). </div> @@ -3327,7 +3327,7 @@ If you rely on Java 8 being present in the analyzer environment, you must take a <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/359133). </div> @@ -3357,7 +3357,7 @@ It is now considered deprecated, and will be removed in GitLab 15.0. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/332323). </div> @@ -3371,7 +3371,7 @@ The `instanceStatisticsMeasurements` GraphQL node has been renamed to `usageTren <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/352488). </div> @@ -3391,7 +3391,7 @@ For more information, check the [summary section of the deprecation issue](https <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). </div> The [required pipeline configuration](https://docs.gitlab.com/ee/user/admin_area/settings/continuous_integration.html#required-pipeline-configuration) feature is deprecated in GitLab 14.8 for Premium customers and is scheduled for removal in GitLab 15.0. This feature is not deprecated for GitLab Ultimate customers. @@ -3409,7 +3409,7 @@ This change will also help GitLab remain consistent in its tiering strategy with <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/350510). </div> @@ -3449,7 +3449,7 @@ in the Vulnerability Report. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/352553). </div> @@ -3533,7 +3533,7 @@ in the Vulnerability Report. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/352564). </div> @@ -3561,7 +3561,7 @@ See the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/352564 <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/350936). </div> @@ -3606,7 +3606,7 @@ Specifically, the following are being deprecated and will no longer be updated a <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/347509). </div> @@ -3653,7 +3653,7 @@ Current users of the Static Site Editor can view the [documentation](https://doc <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). </div> Long term service and support (LTSS) for SUSE Linux Enterprise Server (SLES) 12 SP2 [ended on March 31, 2021](https://www.suse.com/lifecycle/). The CA certificates on SP2 include the expired DST root certificate, and it's not getting new CA certificate package updates. We have implemented some [workarounds](https://gitlab.com/gitlab-org/gitlab-omnibus-builder/-/merge_requests/191), but we will not be able to continue to keep the build running properly. @@ -3666,7 +3666,7 @@ Long term service and support (LTSS) for SUSE Linux Enterprise Server (SLES) 12 <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). </div> Although not recommended or documented, it was possible to deploy a gRPC-aware proxy between Gitaly and @@ -3689,7 +3689,7 @@ the [relevant epic](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/463). <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). </div> To simplify setting a test coverage pattern, in GitLab 15.0 the @@ -3707,7 +3707,7 @@ testing coverage results in merge requests. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/346540). </div> @@ -3721,7 +3721,7 @@ Tracing in GitLab is an integration with Jaeger, an open-source end-to-end distr <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/336912). </div> @@ -3737,7 +3737,7 @@ The `GET /groups/:id/registry/repositories` endpoint will remain, but won't retu <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/343210). </div> @@ -3753,7 +3753,7 @@ If you monitor Value Stream Analytics metrics and rely on the date filter, to av <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). </div> The vulnerability check feature is deprecated in GitLab 14.8 and scheduled for removal in GitLab 15.0. We encourage you to migrate to the new security approvals feature instead. You can do so by navigating to **Security & Compliance > Policies** and creating a new Scan Result Policy. @@ -3773,7 +3773,7 @@ The new security approvals feature is similar to vulnerability check. For exampl <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/327453). </div> @@ -3789,7 +3789,7 @@ In milestone 15.0, we will completely remove `Version` from `PackageType`. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/348980). </div> @@ -3806,7 +3806,7 @@ only supported report file in 15.0, but this is the first step towards GitLab su <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/345451). </div> @@ -3820,7 +3820,7 @@ The GraphQL API field `defaultMergeCommitMessageWithDescription` has been deprec <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/276777). </div> @@ -3836,7 +3836,7 @@ In milestone 15.0, we will remove the feature flag entirely. Moving forward, you <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/342882). </div> @@ -3855,7 +3855,7 @@ To mitigate possible performance problems, we will remove the `versions` field's <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). </div> The `projectFingerprint` field in the [PipelineSecurityReportFinding](https://docs.gitlab.com/ee/api/graphql/reference/index.html#pipelinesecurityreportfinding) @@ -3871,7 +3871,7 @@ exposed in the UUID field. Data previously available in the projectFingerprint f <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/345207). </div> @@ -3885,7 +3885,7 @@ In GitLab 14.5, we introduced the command `gitlab-ctl promote` to promote any Ge <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/345207). </div> @@ -3899,7 +3899,7 @@ In GitLab 14.5, we introduced the command `gitlab-ctl promote` to promote any Ge <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.6</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). </div> The `type` and `types` CI/CD keywords will be removed in GitLab 15.0. Pipelines that use these keywords will stop working, so you must switch to `stage` and `stages`, which have the same behavior. @@ -3912,7 +3912,7 @@ The `type` and `types` CI/CD keywords will be removed in GitLab 15.0. Pipelines <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.6</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/333233). </div> @@ -3928,7 +3928,7 @@ which isn't being used in GitLab anymore. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.6</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [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/289832). </div> @@ -3944,7 +3944,7 @@ If you have explicitly excluded bundler-audit using DS_EXCLUDED_ANALYZERS you wi <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). </div> The Container Registry supports [authentication](https://gitlab.com/gitlab-org/container-registry/-/blob/master/docs/configuration.md#auth) with `htpasswd`. It relies on an [Apache `htpasswd` file](https://httpd.apache.org/docs/2.4/programs/htpasswd.html), with passwords hashed using `bcrypt`. @@ -3959,7 +3959,7 @@ Since it isn't used in the context of GitLab (the product), `htpasswd` authentic <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). </div> The `user_email_lookup_limit` [API field](https://docs.gitlab.com/ee/api/settings.html) is deprecated and will be removed in GitLab 15.0. Until GitLab 15.0, `user_email_lookup_limit` is aliased to `search_rate_limit` and existing workflows will continue to work. @@ -3979,7 +3979,7 @@ Any API calls attempting to change the rate limits for `user_email_lookup_limit` <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). </div> The GitLab Composer repository can be used to push, search, fetch metadata about, and download PHP dependencies. All these actions require authentication, except for downloading dependencies. diff --git a/doc/update/removals.md b/doc/update/removals.md index 97f25897bf5..370870db65a 100644 --- a/doc/update/removals.md +++ b/doc/update/removals.md @@ -59,7 +59,7 @@ We recommend that customers use GitLab Runner versions published with Alpine 3.1 <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/343988). </div> @@ -74,7 +74,7 @@ set the `POSTGRES_ENABLED` CI/CD variable to `true`. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/container-registry/-/issues/854). </div> @@ -86,7 +86,7 @@ In GitLab 16.0, the new default configuration for the storage driver uses `triml <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/charts/gitlab/-/issues/4353). </div> @@ -104,7 +104,7 @@ and [connect Grafana to the GitLab UI](https://docs.gitlab.com/ee/administration <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/369127). </div> @@ -114,7 +114,7 @@ The `omniauth-cas3` gem that provides GitLab with the CAS OmniAuth provider is b <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/361801). </div> @@ -127,7 +127,7 @@ instead. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/384455). </div> @@ -137,7 +137,7 @@ The [GitLab Conan repository](https://docs.gitlab.com/ee/user/packages/conan_rep <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/388255). </div> @@ -151,7 +151,7 @@ configuration file locations instead, for example `config/redis.cache.yml` or <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/container-registry/-/issues/937). </div> @@ -161,7 +161,7 @@ The Container Registry [pull-through cache](https://docs.docker.com/registry/rec <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.4</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/371840). </div> @@ -183,7 +183,7 @@ Instead, use the [new variable names](https://docs.gitlab.com/ee/user/applicatio <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.4</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/369122). </div> @@ -193,7 +193,7 @@ From GitLab 16.0, any personal, project, or group access token [must have an exp <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/387560). </div> @@ -203,7 +203,7 @@ Dependency Scanning no longer supports projects that use Java versions 13, 14, 1 <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/387891). </div> @@ -216,7 +216,7 @@ From GitLab 16.0, only users with at least the Maintainer role for a group can i <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/389477). </div> @@ -228,7 +228,7 @@ with the [GitLab Observability UI](https://gitlab.com/gitlab-org/opstrace/opstra <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/372770). </div> @@ -246,7 +246,7 @@ Users on self-managed instances should update their pipelines to ensure they do <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">16.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/12776). </div> @@ -272,7 +272,7 @@ See [migrated group items](https://docs.gitlab.com/ee/user/group/import/#migrate <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/344648). </div> @@ -285,7 +285,7 @@ In GitLab 16.0 and later, the GraphQL query for runners will no longer return th <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.1</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/362168). </div> @@ -296,7 +296,7 @@ If you cannot upgrade your Jira instance in time and are on GitLab self-managed <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/393574). </div> @@ -314,7 +314,7 @@ instructions, see [Gitaly - Omnibus GitLab configuration structure change](https <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/352609). </div> @@ -329,7 +329,7 @@ using `config.toml`. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390291). </div> @@ -347,7 +347,7 @@ instructions, see [Praefect - Omnibus GitLab configuration structure change](htt <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/214217). </div> @@ -363,7 +363,7 @@ Update any scripts or bookmarks that reference the legacy URLs. GitLab APIs are <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390417). </div> @@ -373,7 +373,7 @@ The License Check Policies feature has been removed. Additionally, the Policies <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/395708). </div> @@ -391,7 +391,7 @@ To prepare for this change, users on GitLab.com or self-managed GitLab 15.9 or l <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390417). </div> @@ -417,7 +417,7 @@ The [**Maximum number of active pipelines per project** limit](https://docs.gitl <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/346541). </div> @@ -440,7 +440,7 @@ This removal only refers to the GitLab Metrics capabilities, and **does not** in <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.4</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/369123). </div> @@ -453,7 +453,7 @@ In GitLab 16.0, any personal, project, or group access token that does not have <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/388269). </div> @@ -470,7 +470,7 @@ and `config/redis.shared_state.yml` files. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.1</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/346335). </div> @@ -480,7 +480,7 @@ Previously, the [PipelineSecurityReportFinding GraphQL type was updated](https:/ <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/7395). </div> @@ -496,7 +496,7 @@ Before upgrading to GitLab 16.0, if you are: <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390266). </div> @@ -510,7 +510,7 @@ You must update your metrics collection targets to use the `/db_metrics` endpoin <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/385798). </div> @@ -552,7 +552,7 @@ Alternatives to using the `gitlab:import:repos` Rake task include: <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/331468). </div> @@ -565,7 +565,7 @@ or later. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.2</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/334253). </div> @@ -616,7 +616,7 @@ In GitLab 13.6 and later, users can [specify any runner configuration in the Git <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.2</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/365939). </div> @@ -628,7 +628,7 @@ If you use the `environment_tier` parameter in your integration (REST or GraphQL <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/388983). </div> @@ -638,7 +638,7 @@ From GitLab 15.9, all Release links are external. The `external` field of the `R <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/388984). </div> @@ -648,7 +648,7 @@ From GitLab 15.9, all Release links are external. The `external` field in the Re <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/366798). </div> @@ -660,7 +660,7 @@ The old `CI_JOB_JWT*` tokens will be completely removed in GitLab 16.5, so you m <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/391822). </div> @@ -688,7 +688,7 @@ If you currently use the `_DISABLED` variables but set a value other than `"true <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/366477). </div> @@ -699,7 +699,7 @@ Security reports that use schema version 14.x.x will cause an error in the pipel <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/groups/gitlab-org/-/epics/10030). </div> @@ -709,7 +709,7 @@ GitLab self-monitoring project was meant to enable self-hosted GitLab administra <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.4</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/368828). </div> @@ -728,7 +728,7 @@ As of GitLab 16.0, GitLab Runner images based on Windows Server 2004 and 20H2 wi <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-com/Product/-/issues/4894). </div> @@ -742,7 +742,7 @@ tool. There has been no activity on the open related issues on GitLab. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/390416). </div> @@ -764,7 +764,7 @@ If you customize the behavior of GitLab SAST by disabling the Semgrep-based anal <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/386001). </div> @@ -786,7 +786,7 @@ To accommodate the changes, you might need to adjust the [`rules`](https://docs. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/383467). </div> @@ -800,7 +800,7 @@ The variables `DAST_API_HOST_OVERRIDE` and `DAST_API_SPECIFICATION` have been re <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/367166). </div> @@ -810,7 +810,7 @@ You can use the vulnerabilityFindingDismiss GraphQL mutation to set the status o <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.4</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/372332). </div> @@ -822,7 +822,7 @@ between the reports and our public APIs, the `confidence` attribute on any vulne <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/352957). </div> @@ -847,7 +847,7 @@ The predefined CI/CD variables that start with `CI_BUILD_*` were deprecated in G <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/29405). </div> @@ -857,7 +857,7 @@ In GitLab 16.0 and later, the `CI_PRE_CLONE_SCRIPT` variable option on GitLab Sa <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">12.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/353097). </div> @@ -867,7 +867,7 @@ The `/approvals` endpoint was [deprecated](https://gitlab.com/gitlab-org/gitlab/ <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/381669). </div> @@ -886,7 +886,7 @@ In GitLab 16.0 and later, the `docker-ssh` and `docker+machine-ssh` executors fo <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/375645). </div> @@ -927,7 +927,7 @@ To continue using GitLab, [upgrade](https://en.opensuse.org/SDB:System_upgrade) <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/383889). </div> @@ -937,7 +937,7 @@ The Live Preview feature of the Web IDE was intended to provide a client-side pr <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/389452). </div> @@ -947,7 +947,7 @@ The Live Preview feature of the Web IDE was intended to provide a client-side pr <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">10.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/388959). </div> @@ -987,7 +987,7 @@ From GitLab 15.8, importing a JSON-formatted group file exports is not supported <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/322454). </div> @@ -1003,7 +1003,7 @@ In GitLab 15.10, this feature's code was refactored. On instances with this feat <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">15.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/29407). </div> @@ -1051,7 +1051,7 @@ We encourage customers currently using NFS for Git repositories to migrate as so <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/352554). </div> @@ -1133,7 +1133,7 @@ The minimum supported browser versions are: <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.6</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/347303). </div> @@ -1148,7 +1148,7 @@ The `not_connected` status is no longer valid. It was replaced with `never_conta <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/337993). </div> @@ -1163,7 +1163,7 @@ Please note that we will add high-volume audit events in the future as part of [ <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/26600). </div> @@ -1211,7 +1211,7 @@ Support for setting `GITLAB_LEGACY_BACKGROUND_UPLOADS` will be removed in GitLab <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/groups/gitlab-org/-/epics/7477). </div> @@ -1230,7 +1230,7 @@ For additional context, or to provide feedback regarding this change, please ref <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> The Container Registry supports [authentication](https://gitlab.com/gitlab-org/container-registry/-/blob/master/docs/configuration.md#auth) with `htpasswd`. It relies on an [Apache `htpasswd` file](https://httpd.apache.org/docs/2.4/programs/htpasswd.html), with passwords hashed using `bcrypt`. @@ -1269,7 +1269,7 @@ The following `geo:db:*` tasks have been removed from GitLab 15.0 and have been <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/333299). </div> @@ -1279,7 +1279,7 @@ We are removing the `DS_DEFAULT_ANALYZERS` environment variable from Dependency <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> For Dependency Scanning, the default version of Java that the scanner expects will be updated from 11 to 17. Java 17 is [the most up-to-date Long Term Support (LTS) version](https://en.wikipedia.org/wiki/Java_version_history). Dependency Scanning continues to support the same [range of versions (8, 11, 13, 14, 15, 16, 17)](https://docs.gitlab.com/ee/user/application_security/dependency_scanning/#supported-languages-and-package-managers), only the default version is changing. If your project uses the previous default of Java 11, be sure to [set the `DS_JAVA_VERSION` variable to match](https://docs.gitlab.com/ee/user/application_security/dependency_scanning/#configuring-specific-analyzers-used-by-dependency-scanning). Please note that consequently the default version of Gradle is now 7.3.3. @@ -1288,7 +1288,7 @@ For Dependency Scanning, the default version of Java that the scanner expects wi <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/346485). </div> @@ -1298,7 +1298,7 @@ The logging features in GitLab allow users to install the ELK stack (Elasticsear <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/350275). </div> @@ -1312,7 +1312,7 @@ View the [version requirements](https://docs.gitlab.com/ee/integration/advanced_ <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/351503). </div> @@ -1322,7 +1322,7 @@ For those using Dependency Scanning for Python projects, we are removing support <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/339039). </div> @@ -1346,7 +1346,7 @@ To align with this change, API calls to list external status checks also return <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/groups/gitlab-org/configure/-/epics/6). </div> @@ -1361,7 +1361,7 @@ For additional context, or to provide feedback regarding this change, please ref <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">13.12</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> Configuring the Gitaly nodes directly in the virtual storage's root configuration object has been deprecated in GitLab 13.12 and is no longer supported in GitLab 15.0. You must move the Gitaly nodes under the `'nodes'` key as described in [the Praefect configuration](https://docs.gitlab.com/ee/administration/gitaly/praefect.html#praefect). @@ -1370,7 +1370,7 @@ Configuring the Gitaly nodes directly in the virtual storage's root configuratio <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> The GitLab Package stage offers a Package Registry, Container Registry, and Dependency Proxy to help you manage all of your dependencies using GitLab. Each of these product categories has a variety of settings that can be adjusted using the API. @@ -1388,7 +1388,7 @@ The issue for this removal is [GitLab-#350682](https://gitlab.com/gitlab-org/git <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/346540). </div> @@ -1398,7 +1398,7 @@ Tracing in GitLab is an integration with Jaeger, an open-source end-to-end distr <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28192). </div> @@ -1428,7 +1428,7 @@ We have now removed the deprecated legacy names for approval status of license p <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/6150). </div> @@ -1438,7 +1438,7 @@ The Gitaly Cluster configuration keys for `praefect['database_host_no_proxy']` a <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/4208). </div> @@ -1448,7 +1448,7 @@ The [`custom_hooks_dir`](https://docs.gitlab.com/ee/administration/server_hooks. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> The OAuth implicit grant authorization flow is no longer supported. Any applications that use OAuth implicit grant must switch to alternative [supported OAuth flows](https://docs.gitlab.com/ee/api/oauth2.html). @@ -1457,7 +1457,7 @@ The OAuth implicit grant authorization flow is no longer supported. Any applicat <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> GitLab no longer supports OAuth tokens [without an expiration](https://docs.gitlab.com/ee/integration/oauth_provider.html#expiring-access-tokens). @@ -1468,7 +1468,7 @@ Any existing token without an expiration has one automatically generated and app <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/351963). </div> @@ -1480,7 +1480,7 @@ expiration on all SSH keys. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/351962). </div> @@ -1512,7 +1512,7 @@ If you rely on Java 8 being present in the analyzer environment, you must take a <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/342882). </div> @@ -1527,7 +1527,7 @@ To mitigate possible performance problems, we will remove the `versions` field's <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/219952). </div> @@ -1538,7 +1538,7 @@ It was removed in GitLab 15.0. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/352488). </div> @@ -1554,7 +1554,7 @@ For more information, check the [summary section of the deprecation issue](https <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> [Required pipeline configuration](https://docs.gitlab.com/ee/user/admin_area/settings/continuous_integration.html#required-pipeline-configuration) helps to define and mandate organization-wide pipeline configurations and is a requirement at an executive and organizational level. To align better with our [pricing philosophy](https://about.gitlab.com/company/pricing/#three-tiers), this feature is removed from the Premium tier in GitLab 15.0. This feature continues to be available in the GitLab Ultimate tier. @@ -1570,7 +1570,7 @@ This change also helps GitLab remain consistent in our tiering strategy with the <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/289830). </div> @@ -1582,7 +1582,7 @@ If you have explicitly excluded retire.js using the `DS_EXCLUDED_ANALYZERS` vari <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.6</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/347305). </div> @@ -1622,7 +1622,7 @@ If you rely on .NET 2.1 support being present in the analyzer image by default, <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> Long term service and support (LTSS) for SUSE Linux Enterprise Server (SLES) 12 SP2 [ended on March 31, 2021](https://www.suse.com/lifecycle/). The CA certificates on SP2 include the expired DST root certificate, and it's not getting new CA certificate package updates. We have implemented some [workarounds](https://gitlab.com/gitlab-org/gitlab-omnibus-builder/-/merge_requests/191), but we will not be able to continue to keep the build running properly. @@ -1654,7 +1654,7 @@ For further details, see [the deprecation issue for this change](https://gitlab. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/groups/gitlab-org/configure/-/epics/8). </div> @@ -1672,7 +1672,7 @@ For updates and details, follow [this epic](https://gitlab.com/groups/gitlab-org <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/347509). </div> @@ -1703,7 +1703,7 @@ The Static Site Editor was deprecated in GitLab 14.7 and the feature is being re <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.10</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/6758). </div> @@ -1713,7 +1713,7 @@ Gitaly introduced a new directory that holds all runtime data Gitaly requires to <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/338182). </div> @@ -1729,7 +1729,7 @@ Instructions are available [in the source update documentation](https://docs.git <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> To specify a test coverage pattern, in GitLab 15.0 the @@ -1743,7 +1743,7 @@ To set test coverage parsing, use the project’s `.gitlab-ci.yml` file by provi <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/345207). </div> @@ -1753,7 +1753,7 @@ In GitLab 14.5, we introduced the command `gitlab-ctl promote` to promote any Ge <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/336912). </div> @@ -1765,7 +1765,7 @@ The `GET /groups/:id/registry/repositories` endpoint will remain, but won't retu <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/327453). </div> @@ -1777,7 +1777,7 @@ In GitLab 15.0, we will completely remove `Version` from `PackageType`. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/357300). </div> @@ -1794,7 +1794,7 @@ The new security approvals feature is similar to vulnerability check. For exampl <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.0</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/333610). </div> @@ -1804,7 +1804,7 @@ The `Managed-Cluster-Applications.gitlab-ci.yml` CI/CD template is being removed <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.7</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/348980). </div> @@ -1817,7 +1817,7 @@ Cobertura is the only supported report file, but this is the first step towards <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/345451). </div> @@ -1827,7 +1827,7 @@ The GraphQL API field `defaultMergeCommitMessageWithDescription` has been remove <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/276777). </div> @@ -1839,7 +1839,7 @@ In GitLab 15.0, we will remove the feature flag, and you must always authenticat <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.3</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> The `omniauth-kerberos` gem is no longer supported. This gem has not been maintained and has very little usage. Therefore, we @@ -1853,7 +1853,7 @@ We are not removing Kerberos SPNEGO integration. We are removing the old passwor <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.5</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/345207). </div> @@ -1863,7 +1863,7 @@ In GitLab 14.5, we introduced the command `gitlab-ctl promote` to promote any Ge <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/262019). </div> @@ -1873,7 +1873,7 @@ The `push_rules_supersede_code_owners` feature flag has been removed in GitLab 1 <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.6</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> The `type` and `types` CI/CD keywords is removed in GitLab 15.0, so pipelines that use these keywords fail with a syntax error. Switch to `stage` and `stages`, which have the same behavior. @@ -1882,7 +1882,7 @@ The `type` and `types` CI/CD keywords is removed in GitLab 15.0, so pipelines th <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.8</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/347491). </div> @@ -1896,7 +1896,7 @@ If you have explicitly excluded bundler-audit using the `DS_EXCLUDED_ANALYZERS` <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> The GitLab Composer repository can be used to push, search, fetch metadata about, and download PHP dependencies. All these actions require authentication, except for downloading dependencies. @@ -1909,7 +1909,7 @@ Downloading Composer dependencies without authentication is deprecated in GitLab <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone">14.9</span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/353639). </div> @@ -2014,7 +2014,7 @@ The minimum supported browser versions are: <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/300862). </div> @@ -2026,7 +2026,7 @@ Since the v1 and v2 versions are not backward-compatible, your project might enc <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/328500). </div> @@ -2038,7 +2038,7 @@ The current stable and latest templates are not compatible, and the current late <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> By default, the Code Quality feature has not provided support for Ruby 2.6+ if you're using the Code Quality template. To better support the latest versions of Ruby, the default RuboCop version is updated to add support for Ruby 2.4 through 3.0. As a result, support for Ruby 2.1, 2.2, and 2.3 is removed. You can re-enable support for older versions by [customizing your configuration](https://docs.gitlab.com/ee/ci/testing/code_quality.html#rubocop-errors). @@ -2049,7 +2049,7 @@ Relevant Issue: [Default `codeclimate-rubocop` engine does not support Ruby 2.6+ <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> Clair, the default container scanning engine, was deprecated in GitLab 13.9 and is removed from GitLab 14.0 and replaced by Trivy. We advise customers who are customizing variables for their container scanning job to [follow these instructions](https://docs.gitlab.com/ee/user/application_security/container_scanning/#change-scanners) to ensure that their container scanning jobs continue to work. @@ -2058,7 +2058,7 @@ Clair, the default container scanning engine, was deprecated in GitLab 13.9 and <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> In GitLab 14.0, we've removed the stages defined in the current `DAST.gitlab-ci.yml` template to avoid the situation where the template overrides manual changes made by DAST users. We're making this change in response to customer issues where the stages in the template cause problems when used with customized DAST configurations. Because of this removal, `gitlab-ci.yml` configurations that do not specify a `dast` stage must be updated to include this stage. @@ -2067,7 +2067,7 @@ In GitLab 14.0, we've removed the stages defined in the current `DAST.gitlab-ci. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> GitLab 13.8 renamed multiple environment variables to support their broader usage in different workflows. In GitLab 14.0, the old variables have been permanently removed and will no longer work. Any configurations using these variables must be updated to the new variable names. Any scans using these variables in GitLab 14.0 and later will fail to be configured correctly. These variables are: @@ -2085,7 +2085,7 @@ GitLab 13.8 renamed multiple environment variables to support their broader usag <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> Browser Performance Testing has run in a job named `performance` by default. With the introduction of [Load Performance Testing](https://docs.gitlab.com/ee/ci/testing/code_quality.html) in GitLab 13.2, this naming could be confusing. To make it clear which job is running [Browser Performance Testing](https://docs.gitlab.com/ee/ci/testing/browser_performance_testing.html), the default job name is changed from `performance` to `browser_performance` in the template in GitLab 14.0. @@ -2096,7 +2096,7 @@ Relevant Issue: [Rename default Browser Performance Testing job](https://gitlab. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> In GitLab 14.0, DAST has removed the current method of resetting the scan to the hostname when starting to spider. Prior to GitLab 14.0, the spider would not begin at the specified target path for the URL but would instead reset the URL to begin crawling at the host root. GitLab 14.0 changes the default for the new variable `DAST_SPIDER_START_AT_HOST` to `false` to better support users' intention of beginning spidering and scanning at the specified target URL, rather than the host root URL. This change has an added benefit: scans can take less time, if the specified path does not contain links to the entire site. This enables easier scanning of smaller sections of an application, rather than crawling the entire app during every scan. @@ -2105,7 +2105,7 @@ In GitLab 14.0, DAST has removed the current method of resetting the scan to the <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> Every Git repository has an initial branch, which is named `master` by default. It's the first branch to be created automatically when you create a new repository. Future [Git versions](https://lore.kernel.org/git/pull.656.v4.git.1593009996.gitgitgadget@gmail.com/) will change the default branch name in Git from `master` to `main`. In coordination with the Git project and the broader community, [GitLab has changed the default branch name](https://gitlab.com/gitlab-org/gitlab/-/issues/223789) for new projects on both our SaaS (GitLab.com) and self-managed offerings starting with GitLab 14.0. This will not affect existing projects. @@ -2118,7 +2118,7 @@ For more information, check out our [blog post](https://about.gitlab.com/blog/20 <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> As mentioned in [13.9](https://about.gitlab.com/releases/2021/02/22/gitlab-13-9-released/#deprecations-for-dependency-scanning) and [this blog post](https://about.gitlab.com/blog/2021/02/08/composition-analysis-14-deprecations-and-removals/) several removals for Dependency Scanning take effect. @@ -2131,7 +2131,7 @@ Previously, to prevent the Gemnasium analyzers to fetch the advisory database at <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> In accordance with our [GraphQL deprecation and removal process](https://docs.gitlab.com/ee/api/graphql/#deprecation-process), the following fields that were deprecated prior to 13.7 are [fully removed in 14.0](https://gitlab.com/gitlab-org/gitlab/-/issues/267966): @@ -2147,7 +2147,7 @@ In accordance with our [GraphQL deprecation and removal process](https://docs.gi <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> The first release of the DevOps Adoption report had a concept of **Segments**. Segments were [quickly removed from the report](https://gitlab.com/groups/gitlab-org/-/epics/5251) because they introduced an additional layer of complexity on top of **Groups** and **Projects**. Subsequent iterations of the DevOps Adoption report focus on comparing adoption across groups rather than segments. GitLab 14.0 removes all references to **Segments** [from the GraphQL API](https://gitlab.com/gitlab-org/gitlab/-/issues/324414) and replaces them with **Enabled groups**. @@ -2156,7 +2156,7 @@ The first release of the DevOps Adoption report had a concept of **Segments**. S <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/5993). </div> @@ -2166,7 +2166,7 @@ GitLab Pages [API-based configuration](https://docs.gitlab.com/ee/administration <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> GitLab supports a [queue selector](https://docs.gitlab.com/ee/administration/operations/extra_sidekiq_processes.html#queue-selector) to run only a subset of background jobs for a given process. When it was introduced, this option had an 'experimental' prefix (`experimental_queue_selector` in Omnibus, `experimentalQueueSelector` in Helm charts). @@ -2177,7 +2177,7 @@ As announced in the [13.6 release post](https://about.gitlab.com/releases/2020/1 <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> For self-managed instances using the experimental [external pipeline validation service](https://docs.gitlab.com/ee/administration/external_pipeline_validation.html), the range of error codes GitLab accepts will be reduced. Currently, pipelines are invalidated when the validation service returns a response code from `400` to `499`. In GitLab 14.0 and later, pipelines will be invalidated for the `406: Not Accepted` response code only. @@ -2186,7 +2186,7 @@ For self-managed instances using the experimental [external pipeline validation <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> As [announced in GitLab 13.3](https://about.gitlab.com/releases/2020/08/22/gitlab-13-3-released/#geo-foreign-data-wrapper-settings-deprecated), the following configuration settings in `/etc/gitlab/gitlab.rb` have been removed in 14.0: @@ -2200,7 +2200,7 @@ As [announced in GitLab 13.3](https://about.gitlab.com/releases/2020/08/22/gitla <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/288516). </div> @@ -2212,7 +2212,7 @@ Migrate your existing applications to other supported [OAuth2 flows](https://doc <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> In 14.0, we are now pulling the GitLab Runner [helper image](https://docs.gitlab.com/runner/configuration/advanced-configuration.html#helper-image) from the GitLab Container Registry instead of Docker Hub. Refer to [issue #27218](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27218) for details. @@ -2221,7 +2221,7 @@ In 14.0, we are now pulling the GitLab Runner [helper image](https://docs.gitlab <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> In GitLab Runner 14.0, the installation process will ignore the `skel` directory by default when creating the user home directory. Refer to [issue #4845](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4845) for details. @@ -2230,7 +2230,7 @@ In GitLab Runner 14.0, the installation process will ignore the `skel` directory <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> Now that Praefect supports a [primary election strategy](https://docs.gitlab.com/ee/administration/gitaly/praefect.html#repository-specific-primary-nodes) for each repository, we have removed the `sql` election strategy. @@ -2242,7 +2242,7 @@ If you had configured the `sql` election strategy, you must follow the [migratio <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/301216). </div> @@ -2256,7 +2256,7 @@ This deprecation and removal changes our [previously announced plan](https://abo <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> Our CI/CD templates have been updated to no longer use hard-coded references to a `master` branch. In 14.0, they all use a variable that points to your project's configured default branch instead. If your CI/CD pipeline relies on our built-in templates, verify that this change works with your current configuration. For example, if you have a `master` branch and a different default branch, the updates to the templates may cause changes to your pipeline behavior. For more information, [read the issue](https://gitlab.com/gitlab-org/gitlab/-/issues/324131). @@ -2265,7 +2265,7 @@ Our CI/CD templates have been updated to no longer use hard-coded references to <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> Helm v2 was [officially deprecated](https://helm.sh/blog/helm-v2-deprecation-timeline/) in November of 2020, with the `stable` repository being [de-listed from the Helm Hub](https://about.gitlab.com/blog/2020/11/09/ensure-auto-devops-work-after-helm-stable-repo/) shortly thereafter. With the release of GitLab 14.0, which will include the 5.0 release of the [GitLab Helm chart](https://docs.gitlab.com/charts/), Helm v2 will no longer be supported. @@ -2276,7 +2276,7 @@ Users of the chart should [upgrade to Helm v3](https://helm.sh/docs/topics/v2_v3 <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> The legacy method of DAST Domain Validation for CI/CD scans was deprecated in GitLab 13.8, and is removed in GitLab 14.0. This method of domain validation only disallows scans if the `DAST_FULL_SCAN_DOMAIN_VALIDATION_REQUIRED` environment variable is set to `true` in the `gitlab-ci.yml` file, and a `Gitlab-DAST-Permission` header on the site is not set to `allow`. This two-step method required users to opt in to using the variable before they could opt out from using the header. @@ -2287,7 +2287,7 @@ For more information, see the [removal issue](https://gitlab.com/gitlab-org/gitl <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/254324). </div> @@ -2297,7 +2297,7 @@ Legacy feature flags became read-only in GitLab 13.4. GitLab 14.0 removes suppor <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> As a part of the migration to a common report format for all of the Secure scanners in GitLab, DAST is making changes to the DAST JSON report. Certain legacy fields were deprecated in 13.8 and have been completely removed in 14.0. These fields are `@generated`, `@version`, `site`, and `spider`. This should not affect any normal DAST operation, but does affect users who consume the JSON report in an automated way and use these fields. Anyone affected by these changes, and needs these fields for business reasons, is encouraged to open a new GitLab issue and explain the need. @@ -2308,7 +2308,7 @@ For more information, see [the removal issue](https://gitlab.com/gitlab-org/gitl <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> As [announced in GitLab 13.0](https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-released/#planned-removal-of-legacy-storage-in-14.0), [legacy storage](https://docs.gitlab.com/ee/administration/repository_storage_types.html#legacy-storage) has been removed in GitLab 14.0. @@ -2317,7 +2317,7 @@ As [announced in GitLab 13.0](https://about.gitlab.com/releases/2020/05/22/gitla <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> In 13.0, we deprecated the License-Management CI template and renamed it License-Scanning. We have been providing backward compatibility by warning users of the old template to switch. Now in 14.0, we are completely removing the License-Management CI template. Read about it in [issue #216261](https://gitlab.com/gitlab-org/gitlab/-/issues/216261) or [this blog post](https://about.gitlab.com/blog/2021/02/08/composition-analysis-14-deprecations-and-removals/). @@ -2326,7 +2326,7 @@ In 13.0, we deprecated the License-Management CI template and renamed it License <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/257829). </div> @@ -2336,7 +2336,7 @@ To improve performance, we are limiting the number of projects returned from the <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> In GitLab Runner 13.2, PowerShell Core support was added to the Shell executor. In 14.0, PowerShell Core, `pwsh` is now the default shell for newly-registered Windows runners. Windows `CMD` will still be available as a shell option for Windows runners. Refer to [issue #26419](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26419) for details. @@ -2345,7 +2345,7 @@ In GitLab Runner 13.2, PowerShell Core support was added to the Shell executor. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/229974). </div> @@ -2356,7 +2356,7 @@ Beginning with 13.9, [we migrated](https://gitlab.com/gitlab-org/gitlab/-/blob/1 <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> In GitLab Runner 13.0, [issue #5069](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/5069), we introduced new timing options for the GitLab Docker Machine executor. In GitLab Runner 14.0, we have removed the old configuration option, [off peak time mode](https://docs.gitlab.com/runner/configuration/autoscale.html#off-peak-time-mode-configuration-deprecated). @@ -2365,7 +2365,7 @@ In GitLab Runner 13.0, [issue #5069](https://gitlab.com/gitlab-org/gitlab-runner <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> Support for [OpenSUSE Leap 15.1 is being deprecated](https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/5135). Support for 15.1 will be dropped in 14.0. We are now providing support for openSUSE Leap 15.2 packages. @@ -2374,7 +2374,7 @@ Support for [OpenSUSE Leap 15.1 is being deprecated](https://gitlab.com/gitlab-o <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> GitLab 14.0 requires PostgreSQL 12 or later. It offers [significant improvements](https://www.postgresql.org/about/news/postgresql-12-released-1976/) to indexing, partitioning, and general performance benefits. @@ -2385,7 +2385,7 @@ Starting in GitLab 13.7, all new installations default to PostgreSQL version 12. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/325931). </div> @@ -2395,7 +2395,7 @@ The [deployment frequency project-level API](https://docs.gitlab.com/ee/api/dora <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/300887). </div> @@ -2405,7 +2405,7 @@ GitLab 14.0 removes support for the release description in the Tags API. You can <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> By default, the `Ruby.gitlab-ci.yml` file has included Ruby 2.5. @@ -2418,7 +2418,7 @@ Relevant Issue: [Updates Ruby version 2.5 to 3.0](https://gitlab.com/gitlab-org/ <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/301215). </div> @@ -2429,7 +2429,7 @@ GitLab 14.0 removes the old `SAST_GOSEC_CONFIG variable`. If you use or override <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> Service Templates are [removed in GitLab 14.0](https://gitlab.com/groups/gitlab-org/-/epics/5672). They were used to apply identical settings to a large number of projects, but they only did so at the time of project creation. @@ -2440,7 +2440,7 @@ While they solved part of the problem, _updating_ those values later proved to b <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> In GitLab Runner 13.5, we introduced `failed` and `success` states for a job. To support Prometheus rules, we chose to convert `success/failure` to `finished` for the metric. In 14.0, the conversion has now been removed. Refer to [issue #26900](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26900) for details. @@ -2449,7 +2449,7 @@ In GitLab Runner 13.5, we introduced `failed` and `success` states for a job. To <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](). </div> @@ -2470,7 +2470,7 @@ To check the new changes, see the [new "major version" template](https://gitlab. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> Ubuntu 16.04 [reached end-of-life in April 2021](https://ubuntu.com/about/release-cycle), and no longer receives maintenance updates. We strongly recommend users to upgrade to a newer release, such as 20.04. @@ -2481,7 +2481,7 @@ GitLab 13.12 will be the last release with Ubuntu 16.04 support. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> Ubuntu 19.10 (Eoan Ermine) reached end of life on Friday, July 17, 2020. In GitLab Runner 14.0, Ubuntu 19.10 (Eoan Ermine) is no longer available from our package distribution. Refer to [issue #26036](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26036) for details. @@ -2490,7 +2490,7 @@ Ubuntu 19.10 (Eoan Ermine) reached end of life on Friday, July 17, 2020. In GitL <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> [Support for Unicorn](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/6078) has been removed in GitLab 14.0 in favor of Puma. [Puma has a multi-threaded architecture](https://docs.gitlab.com/ee/administration/operations/puma.html) which uses less memory than a multi-process application server like Unicorn. On GitLab.com, we saw a 40% reduction in memory consumption by using Puma. @@ -2499,7 +2499,7 @@ Ubuntu 19.10 (Eoan Ermine) reached end of life on Friday, July 17, 2020. In GitL <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> The WIP (work in progress) status for merge requests signaled to reviewers that the merge request in question wasn't ready to merge. We've renamed the WIP feature to **Draft**, a more inclusive and self-explanatory term. **Draft** clearly communicates the merge request in question isn't ready for review, and makes no assumptions about the progress being made toward it. **Draft** also reduces the cognitive load for new users, non-English speakers, and anyone unfamiliar with the WIP acronym. @@ -2508,7 +2508,7 @@ The WIP (work in progress) status for merge requests signaled to reviewers that <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> The Web Application Firewall (WAF) was deprecated in GitLab 13.6 and is removed from GitLab 14.0. The WAF had limitations inherent in the architectural design that made it difficult to meet the requirements traditionally expected of a WAF. By removing the WAF, GitLab is able to focus on improving other areas in the product where more value can be provided to users. Users who currently rely on the WAF can continue to use the free and open source [ModSecurity](https://github.com/SpiderLabs/ModSecurity) project, which is independent from GitLab. Additional details are available in the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/271276). @@ -2517,7 +2517,7 @@ The Web Application Firewall (WAF) was deprecated in GitLab 13.6 and is removed <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> In 14.0, we have removed Windows Server 1903. Microsoft ended support for this version on 2020-08-12. Refer to [issue #27551](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27551) for details. @@ -2526,7 +2526,7 @@ In 14.0, we have removed Windows Server 1903. Microsoft ended support for this v <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> In 14.0, we have removed Windows Server 1909. Microsoft ended support for this version on 2021-05-11. Refer to [issue #27899](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27899) for details. @@ -2535,7 +2535,7 @@ In 14.0, we have removed Windows Server 1909. Microsoft ended support for this v <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> In GitLab Runner 13.3, a symlink was added from `/user/lib/gitlab-runner/gitlab-runner` to `/usr/bin/gitlab-runner`. In 14.0, the symlink has been removed and the runner is now installed in `/usr/bin/gitlab-runner`. Refer to [issue #26651](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26651) for details. @@ -2544,7 +2544,7 @@ In GitLab Runner 13.3, a symlink was added from `/user/lib/gitlab-runner/gitlab- <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> To create a consistent experience for users based on their preferences, support for toggling whitespace changes via URL parameter has been removed in GitLab 14.0. @@ -2553,7 +2553,7 @@ To create a consistent experience for users based on their preferences, support <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> The `CI_PROJECT_CONFIG_PATH` [predefined project variable](https://docs.gitlab.com/ee/ci/variables/predefined_variables.html) @@ -2566,7 +2566,7 @@ please update them to use `CI_CONFIG_PATH` instead. <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> In 14.0, we have deactivated the `FF_RESET_HELPER_IMAGE_ENTRYPOINT` feature flag. Refer to issue [#26679](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26679) for details. @@ -2575,7 +2575,7 @@ In 14.0, we have deactivated the `FF_RESET_HELPER_IMAGE_ENTRYPOINT` feature flag <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> In [GitLab Runner 13.1](https://docs.gitlab.com/runner/executors/shell.html#gitlab-131-and-later), [issue #3376](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/3376), we introduced `sigterm` and then `sigkill` to a process in the Shell executor. We also introduced a new feature flag, `FF_SHELL_EXECUTOR_USE_LEGACY_PROCESS_KILL`, so you can use the previous process termination sequence. In GitLab Runner 14.0, [issue #6413](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/6413), the feature flag has been removed. @@ -2584,7 +2584,7 @@ In [GitLab Runner 13.1](https://docs.gitlab.com/runner/executors/shell.html#gitl <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> GitLab Runner 14.0 removes the `FF_USE_GO_CLOUD_WITH_CACHE_ARCHIVER` feature flag. Refer to [issue #27175](https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27175) for details. @@ -2593,7 +2593,7 @@ GitLab Runner 14.0 removes the `FF_USE_GO_CLOUD_WITH_CACHE_ARCHIVER` feature fla <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. - To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/297269). </div> @@ -2604,7 +2604,7 @@ If you override or maintain custom versions of `SAST.gitlab-ci.yml` or `Secret-D <div class="deprecation-notes"> - Announced in: GitLab <span class="milestone"></span> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). Review the details carefully before upgrading. +- This is a [breaking change](https://docs.gitlab.com/ee/update/terminology.html#breaking-change). Review the details carefully before upgrading. </div> GitLab Runner was updated in GitLab 13.4 to internally stop passing the `trace` parameter to the `/api/jobs/:id` endpoint. GitLab 14.0 deprecates the `trace` parameter entirely for all other requests of this endpoint. Make sure your [GitLab Runner version matches your GitLab version](https://docs.gitlab.com/runner/#gitlab-runner-versions) to ensure consistent behavior. diff --git a/doc/user/admin_area/settings/account_and_limit_settings.md b/doc/user/admin_area/settings/account_and_limit_settings.md index ae0dc184bc7..e244c2de4f0 100644 --- a/doc/user/admin_area/settings/account_and_limit_settings.md +++ b/doc/user/admin_area/settings/account_and_limit_settings.md @@ -276,10 +276,10 @@ When a user's SSH key becomes invalid they can delete and re-add the same key ag > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/3649) in GitLab 12.6. -Users can optionally specify a lifetime for +Users can optionally specify a maximum lifetime in days for access tokens, this includes [personal](../../profile/personal_access_tokens.md), [group](../../group/settings/group_access_tokens.md), and [project](../../project/settings/project_access_tokens.md) access tokens. -This lifetime is not a requirement, and can be set to any arbitrary number of days. +This lifetime is not a requirement, and can be set to any value greater than 0 and less than or equal to 365. If this setting is left blank, the default allowable lifetime of access tokens is 365 days. Access tokens are the only tokens needed for programmatic access to GitLab. However, organizations with security requirements may want to enforce more protection by diff --git a/doc/user/infrastructure/iac/index.md b/doc/user/infrastructure/iac/index.md index 12ad207e4f8..f27f1306c31 100644 --- a/doc/user/infrastructure/iac/index.md +++ b/doc/user/infrastructure/iac/index.md @@ -54,7 +54,7 @@ If you use earlier versions of GitLab, you might face incompatibility errors between the GitLab version and the template version. In this case, you can opt to use one of these templates: -- [The stable template](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Terraform.gitlab-ci.yml) with an skeleton that you can built on top of. +- [The stable template](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Terraform.gitlab-ci.yml) with a skeleton that you can built on top of. - [The advanced template](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Terraform/Base.gitlab-ci.yml) to fully customize your setup. NOTE: diff --git a/doc/user/packages/container_registry/authenticate_with_container_registry.md b/doc/user/packages/container_registry/authenticate_with_container_registry.md index 31337d19d59..6a7c92fd924 100644 --- a/doc/user/packages/container_registry/authenticate_with_container_registry.md +++ b/doc/user/packages/container_registry/authenticate_with_container_registry.md @@ -21,7 +21,7 @@ To authenticate with the Container Registry, you can use a: All of these authentication methods require the minimum scope: - For read (pull) access, to be `read_registry`. -- For write (push) access, to be`write_registry` and `read_registry`. +- For write (push) access, to be `write_registry` and `read_registry`. To authenticate, run the `docker login` command. For example: diff --git a/doc/user/profile/personal_access_tokens.md b/doc/user/profile/personal_access_tokens.md index bda92ce8388..39f0d2e21df 100644 --- a/doc/user/profile/personal_access_tokens.md +++ b/doc/user/profile/personal_access_tokens.md @@ -131,7 +131,8 @@ Personal access tokens expire on the date you define, at midnight UTC. - GitLab runs a check at 01:00 AM UTC every day to identify personal access tokens that expire in the next seven days. The owners of these tokens are notified by email. - GitLab runs a check at 02:00 AM UTC every day to identify personal access tokens that expire on the current date. The owners of these tokens are notified by email. - In GitLab Ultimate, administrators can - [limit the lifetime of access tokens](../admin_area/settings/account_and_limit_settings.md#limit-the-lifetime-of-access-tokens). + [limit the allowable lifetime of access tokens](../admin_area/settings/account_and_limit_settings.md#limit-the-lifetime-of-access-tokens). If not set, the maximum allowable lifetime of a personal access token is 365 days. +- In GitLab Free and Premium, the maximum allowable lifetime of a personal access token is 365 days. ## Create a personal access token programmatically **(FREE SELF)** diff --git a/lib/gitlab/usage_data_counters/issue_activity_unique_counter.rb b/lib/gitlab/usage_data_counters/issue_activity_unique_counter.rb index 31f090e0f51..429ca636b2c 100644 --- a/lib/gitlab/usage_data_counters/issue_activity_unique_counter.rb +++ b/lib/gitlab/usage_data_counters/issue_activity_unique_counter.rb @@ -38,8 +38,7 @@ module Gitlab class << self def track_issue_created_action(author:, namespace:) - track_snowplow_action(ISSUE_CREATED, author, namespace) - track_unique_action(ISSUE_CREATED, author) + track_internal_action(ISSUE_CREATED, author, namespace) end def track_issue_title_changed_action(author:, project:) @@ -180,14 +179,7 @@ module Gitlab private def track_snowplow_action(event_name, author, container) - namespace, project = case container - when Project - [container.namespace, container] - when Namespaces::ProjectNamespace - [container.parent, container.project] - else - [container, nil] - end + namespace, project = get_params_from_container(container) return unless author @@ -208,6 +200,30 @@ module Gitlab Gitlab::UsageDataCounters::HLLRedisCounter.track_event(event_name, values: author.id) end + + def track_internal_action(event_name, author, container) + return unless author + + namespace, project = get_params_from_container(container) + + Gitlab::InternalEvents.track_event( + event_name, + user_id: author.id, + project_id: project&.id, + namespace_id: namespace&.id + ) + end + + def get_params_from_container(container) + case container + when Project + [container.namespace, container] + when Namespaces::ProjectNamespace + [container.parent, container.project] + else + [container, nil] + end + end end end end diff --git a/locale/gitlab.pot b/locale/gitlab.pot index 3fee337177a..0bd6acd65e3 100644 --- a/locale/gitlab.pot +++ b/locale/gitlab.pot @@ -11765,6 +11765,9 @@ msgstr "" msgid "ComplianceReport|No projects found" msgstr "" +msgid "ComplianceReport|No projects found that match filters" +msgstr "" + msgid "ComplianceReport|No violations found" msgstr "" @@ -34888,6 +34891,9 @@ msgstr "" msgid "ProductAnalytics|Feature Usages" msgstr "" +msgid "ProductAnalytics|For more information, see the %{linkStart}docs%{linkEnd}." +msgstr "" + msgid "ProductAnalytics|For the product analytics dashboard to start showing you some data, you need to add the analytics tracking code to your project." msgstr "" diff --git a/spec/features/projects/settings/service_desk_setting_spec.rb b/spec/features/projects/settings/service_desk_setting_spec.rb index c18da56f3ee..d068cb219f1 100644 --- a/spec/features/projects/settings/service_desk_setting_spec.rb +++ b/spec/features/projects/settings/service_desk_setting_spec.rb @@ -2,18 +2,20 @@ require 'spec_helper' -RSpec.describe 'Service Desk Setting', :js, :clean_gitlab_redis_cache, feature_category: :groups_and_projects do - let(:project) { create(:project_empty_repo, :private, service_desk_enabled: false) } +RSpec.describe 'Service Desk Setting', :js, :clean_gitlab_redis_cache, feature_category: :service_desk do + let_it_be_with_reload(:project) { create(:project_empty_repo, :private, service_desk_enabled: false) } let(:presenter) { project.present(current_user: user) } - let(:user) { create(:user) } + let_it_be_with_reload(:user) { create(:user) } before do project.add_maintainer(user) sign_in(user) - allow_any_instance_of(Project).to receive(:present).with(current_user: user).and_return(presenter) - allow(::Gitlab::Email::IncomingEmail).to receive(:enabled?) { true } - allow(::Gitlab::Email::IncomingEmail).to receive(:supports_wildcard?) { true } + allow_next_instance_of(Project) do |project| + allow(project).to receive(:present).with(current_user: user).and_return(presenter) + end + allow(::Gitlab::Email::IncomingEmail).to receive(:enabled?).and_return(true) + allow(::Gitlab::Email::IncomingEmail).to receive(:supports_wildcard?).and_return(true) end it 'shows activation checkbox' do @@ -43,8 +45,8 @@ RSpec.describe 'Service Desk Setting', :js, :clean_gitlab_redis_cache, feature_c context 'when service_desk_email is enabled' do before do - allow(::Gitlab::Email::ServiceDeskEmail).to receive(:enabled?) { true } - allow(::Gitlab::Email::ServiceDeskEmail).to receive(:address_for_key) { 'address-suffix@example.com' } + allow(::Gitlab::Email::ServiceDeskEmail).to receive(:enabled?).and_return(true) + allow(::Gitlab::Email::ServiceDeskEmail).to receive(:address_for_key).and_return('address-suffix@example.com') visit edit_project_path(project) end @@ -66,7 +68,7 @@ RSpec.describe 'Service Desk Setting', :js, :clean_gitlab_redis_cache, feature_c expect(find('[data-testid="incoming-email"]').value).to eq('address-suffix@example.com') end - context 'issue description templates' do + describe 'issue description templates' do let_it_be(:issuable_project_template_files) do { '.gitlab/issue_templates/project-issue-bar.md' => 'Project Issue Template Bar', @@ -82,8 +84,13 @@ RSpec.describe 'Service Desk Setting', :js, :clean_gitlab_redis_cache, feature_c end let_it_be_with_reload(:group) { create(:group) } - let_it_be_with_reload(:project) { create(:project, :custom_repo, group: group, files: issuable_project_template_files) } - let_it_be(:group_template_repo) { create(:project, :custom_repo, group: group, files: issuable_group_template_files) } + let_it_be_with_reload(:project) do + create(:project, :custom_repo, group: group, files: issuable_project_template_files) + end + + let_it_be(:group_template_repo) do + create(:project, :custom_repo, group: group, files: issuable_group_template_files) + end before do stub_licensed_features(custom_file_templates_for_namespace: false, custom_file_templates: false) @@ -94,4 +101,10 @@ RSpec.describe 'Service Desk Setting', :js, :clean_gitlab_redis_cache, feature_c it_behaves_like 'issue description templates from current project only' end end + + it 'pushes service_desk_custom_email feature flag to frontend' do + visit edit_project_path(project) + + expect(page).to have_pushed_frontend_feature_flags(serviceDeskCustomEmail: true) + end end diff --git a/spec/frontend/analytics/usage_trends/components/users_chart_spec.js b/spec/frontend/analytics/usage_trends/components/users_chart_spec.js index 20836d7cc70..8638d82ae3c 100644 --- a/spec/frontend/analytics/usage_trends/components/users_chart_spec.js +++ b/spec/frontend/analytics/usage_trends/components/users_chart_spec.js @@ -22,23 +22,19 @@ describe('UsersChart', () => { let queryHandler; const createComponent = ({ - loadingError = false, - loading = false, users = [], additionalData = [], + handler = mockQueryResponse({ key: 'users', data: users, additionalData }), } = {}) => { - queryHandler = mockQueryResponse({ key: 'users', data: users, loading, additionalData }); + queryHandler = handler; - return shallowMount(UsersChart, { + wrapper = shallowMount(UsersChart, { + apolloProvider: createMockApollo([[usersQuery, queryHandler]]), props: { startDate: new Date(2020, 9, 26), endDate: new Date(2020, 10, 1), totalDataPoints: mockCountsData2.length, }, - apolloProvider: createMockApollo([[usersQuery, queryHandler]]), - data() { - return { loadingError }; - }, }); }; @@ -48,7 +44,7 @@ describe('UsersChart', () => { describe('while loading', () => { beforeEach(() => { - wrapper = createComponent({ loading: true }); + createComponent({ loading: true }); }); it('displays the skeleton loader', () => { @@ -62,7 +58,7 @@ describe('UsersChart', () => { describe('without data', () => { beforeEach(async () => { - wrapper = createComponent({ users: [] }); + createComponent({ users: [] }); await nextTick(); }); @@ -81,7 +77,7 @@ describe('UsersChart', () => { describe('with data', () => { beforeEach(async () => { - wrapper = createComponent({ users: mockCountsData2 }); + createComponent({ users: mockCountsData2 }); await waitForPromises(); }); @@ -102,11 +98,17 @@ describe('UsersChart', () => { describe('with errors', () => { beforeEach(async () => { - wrapper = createComponent({ loadingError: true }); + createComponent(); await nextTick(); }); - it('renders an error message', () => { + it('renders an error message', async () => { + createComponent({ + handler: jest.fn().mockRejectedValue({}), + }); + + await waitForPromises(); + expect(findAlert().text()).toBe( 'Could not load the user chart. Please refresh the page to try again.', ); @@ -124,42 +126,37 @@ describe('UsersChart', () => { describe('when fetching more data', () => { describe('when the fetchMore query returns data', () => { beforeEach(async () => { - wrapper = createComponent({ + createComponent({ users: mockCountsData2, additionalData: mockCountsData1, }); - jest.spyOn(wrapper.vm.$apollo.queries.users, 'fetchMore'); await nextTick(); }); it('requests data twice', () => { expect(queryHandler).toHaveBeenCalledTimes(2); }); - - it('calls fetchMore', () => { - expect(wrapper.vm.$apollo.queries.users.fetchMore).toHaveBeenCalledTimes(1); - }); }); describe('when the fetchMore query throws an error', () => { beforeEach(async () => { - wrapper = createComponent({ + createComponent({ users: mockCountsData2, additionalData: mockCountsData1, }); - jest - .spyOn(wrapper.vm.$apollo.queries.users, 'fetchMore') - .mockImplementation(jest.fn().mockRejectedValue()); await waitForPromises(); }); it('calls fetchMore', () => { - expect(wrapper.vm.$apollo.queries.users.fetchMore).toHaveBeenCalledTimes(1); + expect(queryHandler).toHaveBeenCalledTimes(2); }); - it('renders an error message', () => { + it('renders an error message', async () => { + createComponent({ handler: jest.fn().mockRejectedValue({}) }); + await waitForPromises(); + expect(findAlert().text()).toBe( 'Could not load the user chart. Please refresh the page to try again.', ); diff --git a/spec/frontend/observability/observability_app_spec.js b/spec/frontend/observability/observability_app_spec.js index 4a9be71b880..392992a5962 100644 --- a/spec/frontend/observability/observability_app_spec.js +++ b/spec/frontend/observability/observability_app_spec.js @@ -1,4 +1,5 @@ import { shallowMountExtended } from 'helpers/vue_test_utils_helper'; +import { stubComponent } from 'helpers/stub_component'; import ObservabilityApp from '~/observability/components/observability_app.vue'; import ObservabilitySkeleton from '~/observability/components/skeleton/index.vue'; import { @@ -21,7 +22,7 @@ describe('ObservabilityApp', () => { query: { otherQuery: 100 }, }; - const mockHandleSkeleton = jest.fn(); + const mockSkeletonOnContentLoaded = jest.fn(); const findIframe = () => wrapper.findByTestId('observability-ui-iframe'); @@ -36,7 +37,9 @@ describe('ObservabilityApp', () => { ...props, }, stubs: { - 'observability-skeleton': ObservabilitySkeleton, + ObservabilitySkeleton: stubComponent(ObservabilitySkeleton, { + methods: { onContentLoaded: mockSkeletonOnContentLoaded }, + }), }, mocks: { $route, @@ -155,14 +158,14 @@ describe('ObservabilityApp', () => { describe('on GOUI_LOADED', () => { beforeEach(() => { mountComponent(); - wrapper.vm.$refs.observabilitySkeleton.onContentLoaded = mockHandleSkeleton; }); + it('should call onContentLoaded method', () => { dispatchMessageEvent({ data: { type: MESSAGE_EVENT_TYPE.GOUI_LOADED }, origin: 'https://observe.gitlab.com', }); - expect(mockHandleSkeleton).toHaveBeenCalled(); + expect(mockSkeletonOnContentLoaded).toHaveBeenCalled(); }); it('should not call onContentLoaded method if origin is different', () => { @@ -170,7 +173,7 @@ describe('ObservabilityApp', () => { data: { type: MESSAGE_EVENT_TYPE.GOUI_LOADED }, origin: 'https://example.com', }); - expect(mockHandleSkeleton).not.toHaveBeenCalled(); + expect(mockSkeletonOnContentLoaded).not.toHaveBeenCalled(); }); it('should not call onContentLoaded method if event type is different', () => { @@ -178,7 +181,7 @@ describe('ObservabilityApp', () => { data: { type: 'UNKNOWN_EVENT' }, origin: 'https://observe.gitlab.com', }); - expect(mockHandleSkeleton).not.toHaveBeenCalled(); + expect(mockSkeletonOnContentLoaded).not.toHaveBeenCalled(); }); }); diff --git a/spec/lib/gitlab/usage_data_counters/issue_activity_unique_counter_spec.rb b/spec/lib/gitlab/usage_data_counters/issue_activity_unique_counter_spec.rb index ba83d979cad..50e20e4fbcf 100644 --- a/spec/lib/gitlab/usage_data_counters/issue_activity_unique_counter_spec.rb +++ b/spec/lib/gitlab/usage_data_counters/issue_activity_unique_counter_spec.rb @@ -66,7 +66,7 @@ RSpec.describe Gitlab::UsageDataCounters::IssueActivityUniqueCounter, :clean_git end context 'for Issue created actions' do - it_behaves_like 'tracked issuable snowplow and service ping events with project' do + it_behaves_like 'tracked issuable internal event with project' do let(:action) { described_class::ISSUE_CREATED } let(:original_params) { { namespace: project.project_namespace.reload } } diff --git a/spec/lib/gitlab/usage_data_counters/merge_request_activity_unique_counter_spec.rb b/spec/lib/gitlab/usage_data_counters/merge_request_activity_unique_counter_spec.rb index 25c57aa00c6..53eee62b386 100644 --- a/spec/lib/gitlab/usage_data_counters/merge_request_activity_unique_counter_spec.rb +++ b/spec/lib/gitlab/usage_data_counters/merge_request_activity_unique_counter_spec.rb @@ -54,11 +54,6 @@ RSpec.describe Gitlab::UsageDataCounters::MergeRequestActivityUniqueCounter, :cl let(:merge_request) { create(:merge_request) } let(:target_project) { merge_request.target_project } - let(:fake_tracker) { instance_spy(Gitlab::Tracking::Destinations::Snowplow) } - - before do - allow(Gitlab::Tracking).to receive(:tracker).and_return(fake_tracker) - end it_behaves_like 'a tracked merge request unique event' do let(:action) { described_class::MR_USER_CREATE_ACTION } @@ -68,36 +63,10 @@ RSpec.describe Gitlab::UsageDataCounters::MergeRequestActivityUniqueCounter, :cl let(:action) { described_class::MR_CREATE_ACTION } end - it 'logs to Snowplow', :aggregate_failures do - # This logic should be extracted to shared_examples - namespace = target_project.namespace - - expect(Gitlab::Tracking::StandardContext) - .to receive(:new) - .with( - project_id: target_project.id, - user_id: user.id, - namespace_id: namespace.id, - plan_name: namespace.actual_plan_name - ) - .and_call_original - - expect(Gitlab::Tracking::ServicePingContext) - .to receive(:new) - .with(data_source: :redis_hll, event: described_class::MR_USER_CREATE_ACTION) - .and_call_original - - expect(fake_tracker).to receive(:event) - .with( - 'InternalEventTracking', - described_class::MR_USER_CREATE_ACTION, - context: [ - an_instance_of(SnowplowTracker::SelfDescribingJson), - an_instance_of(SnowplowTracker::SelfDescribingJson) - ] - ) - .exactly(:once) - subject + it_behaves_like 'internal event tracking' do + let(:action) { described_class::MR_USER_CREATE_ACTION } + let(:project) { target_project } + let(:namespace) { project.namespace } end end diff --git a/spec/models/issue_spec.rb b/spec/models/issue_spec.rb index ee47f90fb40..4cd73cd3fe6 100644 --- a/spec/models/issue_spec.rb +++ b/spec/models/issue_spec.rb @@ -338,11 +338,13 @@ RSpec.describe Issue, feature_category: :team_planning do create(:issue) end - it_behaves_like 'issue_edit snowplow tracking' do + it_behaves_like 'internal event tracking' do let(:issue) { create(:issue) } let(:project) { issue.project } - let(:property) { Gitlab::UsageDataCounters::IssueActivityUniqueCounter::ISSUE_CREATED } let(:user) { issue.author } + let(:action) { Gitlab::UsageDataCounters::IssueActivityUniqueCounter::ISSUE_CREATED } + let(:namespace) { project.namespace } + subject(:service_action) { issue } end end diff --git a/spec/models/work_item_spec.rb b/spec/models/work_item_spec.rb index e0ec54fd5ff..bf43a2032e7 100644 --- a/spec/models/work_item_spec.rb +++ b/spec/models/work_item_spec.rb @@ -212,11 +212,13 @@ RSpec.describe WorkItem, feature_category: :portfolio_management do create(:work_item) end - it_behaves_like 'issue_edit snowplow tracking' do + it_behaves_like 'internal event tracking' do let(:work_item) { create(:work_item) } - let(:property) { Gitlab::UsageDataCounters::IssueActivityUniqueCounter::ISSUE_CREATED } + let(:action) { Gitlab::UsageDataCounters::IssueActivityUniqueCounter::ISSUE_CREATED } let(:project) { work_item.project } let(:user) { work_item.author } + let(:namespace) { project.namespace } + subject(:service_action) { work_item } end end diff --git a/spec/support/rspec_order_todo.yml b/spec/support/rspec_order_todo.yml index 4168820a2b3..adee31ca644 100644 --- a/spec/support/rspec_order_todo.yml +++ b/spec/support/rspec_order_todo.yml @@ -4151,7 +4151,6 @@ - './spec/features/projects/settings/registry_settings_spec.rb' - './spec/features/projects/settings/repository_settings_spec.rb' - './spec/features/projects/settings/secure_files_spec.rb' -- './spec/features/projects/settings/service_desk_setting_spec.rb' - './spec/features/projects/settings/user_archives_project_spec.rb' - './spec/features/projects/settings/user_changes_avatar_spec.rb' - './spec/features/projects/settings/user_changes_default_branch_spec.rb' diff --git a/spec/support/shared_examples/controllers/internal_event_tracking_examples.rb b/spec/support/shared_examples/controllers/internal_event_tracking_examples.rb new file mode 100644 index 00000000000..e2a4fb31361 --- /dev/null +++ b/spec/support/shared_examples/controllers/internal_event_tracking_examples.rb @@ -0,0 +1,50 @@ +# frozen_string_literal: true + +# Requires a context containing: +# - subject +# - action +# - user +# Optionally, the context can contain: +# - project +# - namespace + +RSpec.shared_examples 'internal event tracking' do + let(:fake_tracker) { instance_spy(Gitlab::Tracking::Destinations::Snowplow) } + let(:namespace) { nil } + let(:proejct) { nil } + + before do + allow(Gitlab::Tracking).to receive(:tracker).and_return(fake_tracker) + + allow(Gitlab::Tracking::StandardContext).to receive(:new).and_call_original + allow(Gitlab::Tracking::ServicePingContext).to receive(:new).and_call_original + end + + it 'logs to Snowplow', :aggregate_failures do + subject + + expect(Gitlab::Tracking::StandardContext) + .to have_received(:new) + .with( + project_id: project&.id, + user_id: user.id, + namespace_id: namespace&.id, + plan_name: namespace&.actual_plan_name + ) + + expect(Gitlab::Tracking::ServicePingContext) + .to have_received(:new) + .with(data_source: :redis_hll, event: action) + + expect(fake_tracker).to have_received(:event) + .with( + 'InternalEventTracking', + action, + context: [ + an_instance_of(SnowplowTracker::SelfDescribingJson), + an_instance_of(SnowplowTracker::SelfDescribingJson) + ] + ) + .exactly(:once) + end +end diff --git a/spec/support/shared_examples/controllers/snowplow_event_tracking_examples.rb b/spec/support/shared_examples/controllers/snowplow_event_tracking_examples.rb index ba00e3e0610..3d3b619451d 100644 --- a/spec/support/shared_examples/controllers/snowplow_event_tracking_examples.rb +++ b/spec/support/shared_examples/controllers/snowplow_event_tracking_examples.rb @@ -6,7 +6,7 @@ # - category # - action # - namespace -# Optionaly, the context can contain: +# Optionally, the context can contain: # - project # - property # - user diff --git a/spec/support/shared_examples/lib/gitlab/usage_data_counters/issuable_activity_shared_examples.rb b/spec/support/shared_examples/lib/gitlab/usage_data_counters/issuable_activity_shared_examples.rb index 169fceced7a..9dc18555340 100644 --- a/spec/support/shared_examples/lib/gitlab/usage_data_counters/issuable_activity_shared_examples.rb +++ b/spec/support/shared_examples/lib/gitlab/usage_data_counters/issuable_activity_shared_examples.rb @@ -1,6 +1,6 @@ # frozen_string_literal: true -RSpec.shared_examples 'tracked issuable snowplow and service ping events for given event params' do +RSpec.shared_examples 'tracked issuable events' do before do stub_application_setting(usage_ping_enabled: true) end @@ -21,6 +21,10 @@ RSpec.shared_examples 'tracked issuable snowplow and service ping events for giv it 'does not track edit actions if author is not present' do expect(track_action({ author: nil }.merge(track_params))).to be_nil end +end + +RSpec.shared_examples 'tracked issuable snowplow and service ping events for given event params' do + it_behaves_like 'tracked issuable events' it 'emits snowplow event' do track_action({ author: user1 }.merge(track_params)) @@ -29,6 +33,23 @@ RSpec.shared_examples 'tracked issuable snowplow and service ping events for giv end end +RSpec.shared_examples 'tracked issuable internal event for given event params' do + it_behaves_like 'tracked issuable events' + + it_behaves_like 'internal event tracking' do + subject(:track_event) { track_action({ author: user1 }.merge(track_params)) } + + let(:user) { user1 } + let(:namespace) { project&.namespace } + end +end + +RSpec.shared_examples 'tracked issuable internal event with project' do + it_behaves_like 'tracked issuable internal event for given event params' do + let(:track_params) { original_params || { project: project } } + end +end + RSpec.shared_examples 'tracked issuable snowplow and service ping events with project' do it_behaves_like 'tracked issuable snowplow and service ping events for given event params' do let(:context) do |