From e4384360a16dd9a19d4d2d25d0ef1f2b862ed2a6 Mon Sep 17 00:00:00 2001 From: GitLab Bot Date: Wed, 19 Jul 2023 14:16:28 +0000 Subject: Add latest changes from gitlab-org/gitlab@16-2-stable-ee --- data/deprecations/ 16-2-cirunner_fields.yml | 13 +++ .../14-10-old-search-migration-removal.yml | 5 +- ...nce-required-pipeline-configuration-premium.yml | 2 +- data/deprecations/14-8-enforce-pat-expiration.yml | 2 +- data/deprecations/14-8-enforce-ssh-expiration.yml | 2 +- data/deprecations/14-8-sast-analyzer-removals.yml | 5 +- .../14-9-deprecate-testcoveragesetting.yml | 2 +- data/deprecations/15-0-oauth-noexpiry.yml | 2 +- data/deprecations/15-3-pipeline_activity_limit.yml | 6 +- .../15-9-accessibility-testing-deprecation.yml | 26 ------ ...5-9-browser-performance-testing-deprecation.yml | 26 ------ .../15-9-license-compliance-ci-template.yml | 6 +- .../15-9-load-performance-testing-deprecation.yml | 26 ------ .../15-9-required-pipeline-configuration.yml | 2 +- ...recate-sidekiq-delivery-method-for-mailroom.yml | 5 +- ...-deprecate-message-from-vulnerabilitycreate.yml | 10 +++ .../16-1-non-decomposed-mode-deprecation.yml | 10 ++- data/deprecations/16-2-agentk-builtin-gitops.yml | 13 +++ .../16-2-deprecation-omniauth-facebook.yml | 11 +++ .../16-2-registry-size-estimated-graphql-field.yml | 11 +++ data/deprecations/16_2-custom_sign_in_fields.yml | 11 +++ .../templates/_deprecation_template.md.erb | 12 +-- data/removals/14_0/14_0-ds-deprecations.yml | 11 --- data/removals/14_0/14_0-lc-deprecations.yml | 7 -- .../14_0/change_default_branch_name_to_main.yml | 11 --- .../removals/14_0/create-code-review-draft-wip.yml | 7 -- .../create-code-review-w-parameter-removal.yml | 7 -- ...deprecation_bump_terraform_template_version.yml | 19 ----- .../14_0/deprecation_manage_access_14_0.yml | 19 ----- ...icd_templates_to_stop_using_hardcode_master.yml | 7 -- .../14_0/deuley_servicetemplates_removal.yml | 9 -- ...e_announce_deprecation_of_release_notes_api.yml | 8 -- .../14_0/release_deprecation_auto-deploy-image.yml | 10 --- ..._configuration_for_gitlab_pages_deprecation.yml | 8 -- .../release_legacy_feature_flags_deprecation.yml | 8 -- ...dant_keyvalue_pair_from_the_payload_of_dora.yml | 8 -- data/removals/14_0/removal-geo-fdw-settings.yml | 12 --- data/removals/14_0/removal-graphql-fields.yml | 14 ---- data/removals/14_0/removal-legacy-storage.yml | 7 -- data/removals/14_0/removal-protect-features.yml | 15 ---- ...removal-sidekiq_experimental_queue_selector.yml | 9 -- data/removals/14_0/removal-unicorn.yml | 7 -- .../14_0/removal_ci_project_config_path.yml | 11 --- data/removals/14_0/removal_enablement_helm2.yml | 9 -- .../14_0/removal_enablement_opensuse_15_1.yml | 7 -- data/removals/14_0/removal_enablement_pg11.yml | 9 -- .../removals/14_0/removal_enablement_ubuntu_16.yml | 9 -- .../removal_repost_static_analysis_notices.yml | 42 ---------- data/removals/14_0/removal_runner_25555.yml | 7 -- data/removals/14_0/removal_runner_26036.yml | 7 -- data/removals/14_0/removal_runner_26419.yml | 7 -- data/removals/14_0/removal_runner_4845.yml | 7 -- data/removals/14_0/removal_runner_6413.yml | 7 -- data/removals/14_0/removals-14-testing-team.yml | 29 ------- data/removals/14_0/removals_runner_26651.yml | 7 -- data/removals/14_0/removals_runner_26679.yml | 7 -- data/removals/14_0/removals_runner_26900.yml | 7 -- data/removals/14_0/removals_runner_27175.yml | 7 -- data/removals/14_0/removals_runner_27218.yml | 7 -- data/removals/14_0/removals_runner_27551.yml | 7 -- data/removals/14_0/removals_runner_27899.yml | 7 -- data/removals/14_0/remove-sql-elector.yml | 10 --- data/removals/14_0/remove_dast_env_variables.yml | 16 ---- .../14_0/remove_dast_legacy_domain_validation.yml | 9 -- .../14_0/remove_dast_legacy_report_fields.yml | 9 -- .../14_0/remove_dast_spider_host_reset.yml | 7 -- data/removals/14_0/remove_dast_template_stages.yml | 7 -- data/removals/14_0/remove_optimize_api.yml | 7 -- data/removals/14_0/remove_terraform_template.yml | 10 --- .../14_0/verify-ci-removal-parametertrace.yml | 7 -- .../14_0/verify-ci-removalpipelineservice.yml | 7 -- .../removal-memory-prometheus-options-source.yml | 9 -- .../14_1/removal-outdated-browser-support.yml | 21 ----- .../14-10-package-permissions-composer-change.yml | 12 --- data/removals/14_2/removal-verify-build-log.yml | 8 -- data/removals/14_3/removal-limit-tags-to-50.yml | 7 -- .../14_3/removal-verify-pe-pipelinefindername.yml | 7 -- .../14_3/removal_legacy_storage_setting.yml | 9 -- data/removals/14_6/limit_trigger_pipelines.yml | 6 -- data/removals/14_6/removal-release-cli-s3.yml | 6 -- ...l_monitor_respond_integrated_error_tracking.yml | 14 ---- ...al-status-names-from-License-Compliance-API.yml | 11 --- data/removals/15_0/15-0-Pseudonymizer.yml | 13 --- data/removals/15_0/15-0-Retire-js-analyzer.yml | 13 --- data/removals/15_0/15-0-SLES-12-SP2.yml | 10 --- .../15-0-advanced-search-elasticsearch-6-8.yml | 16 ---- data/removals/15_0/15-0-bundler-audit.yml | 13 --- ...e-self-managed-cert-based-kube-feature-flag.yml | 24 ------ .../15_0/15-0-container-registry-htpasswd.yml | 11 --- data/removals/15_0/15-0-custom_hooks_dir.yml | 12 --- ...5-0-database-deprecate-legacy-database-conf.yml | 17 ---- ...-0-dependency-scanning-default-java-version.yml | 15 ---- .../15_0/15-0-dependency-scanning-python-image.yml | 11 --- data/removals/15_0/15-0-ds-default-analyzers.yml | 12 --- .../15_0/15-0-geo-remove-db-rake-tasks.yml | 31 ------- data/removals/15_0/15-0-geo-remove-promote-db.yml | 13 --- .../15-0-geo-remove-promote-to-primary-node.yml | 13 --- .../15_0/15-0-gitaly-internal-socket-dir.yml | 13 --- .../15_0/15-0-managed-cluster-applications.yml | 12 --- data/removals/15_0/15-0-merge-commit-message.yml | 16 ---- data/removals/15_0/15-0-oauth-implicit-grant.yml | 16 ---- data/removals/15_0/15-0-oauth-tokens-no-expiry.yml | 18 ---- data/removals/15_0/15-0-omniauth-kerberos-gem.yml | 21 ----- .../15-0-package-container-registry-group-api.yml | 14 ---- .../15_0/15-0-package-settings-permissions.yml | 18 ---- .../15_0/15-0-praefect-database-no-proxy.yml | 11 --- .../15_0/15-0-praefect-virtual-storage.yml | 9 -- data/removals/15_0/15-0-protect-cns-chs.yml | 21 ----- .../15_0/15-0-protect-vulnerability-check.yml | 18 ---- .../15_0/15-0-removal-artifacts-keyword.yml | 16 ---- .../15_0/15-0-removal-testcoveragesetting.yml | 14 ---- ...5-0-remove-background-upload-object-storage.yml | 52 ------------ .../15-0-remove-dependency-proxy-feature-flag.yml | 13 --- .../15_0/15-0-remove-replicaiton-detail-routes.yml | 12 --- .../15_0/15-0-remove-versions-packagetype.yml | 13 --- ...-remove_ff_push_rules_supersede_code_owners.yml | 16 ---- data/removals/15_0/15-0-request-profiling.yml | 18 ---- ...5-0-runner-api-status-renames-not_connected.yml | 16 ---- .../15-0-runner-disable-strict-host-key-check.yml | 14 ---- ...runner_api_new_stale_status_breaking_change.yml | 17 ---- data/removals/15_0/15-0-sast-dotnet-21.yml | 33 -------- data/removals/15_0/15-0-sast-spotbugs-java-8.yml | 28 ------- .../15_0/15-0-secret-detection-configurations.yml | 30 ------- data/removals/15_0/15-0-serverless.yml | 17 ---- .../15-0-sidekiq-metrics-health-check-config.yml | 24 ------ data/removals/15_0/15-0-static-site-editor.yml | 17 ---- data/removals/15_0/15-0-tracing.yml | 16 ---- data/removals/15_0/15-0-type.yml | 10 --- data/removals/15_0/15_0-logging.yml | 16 ---- .../15_0-remove-pipelines-from-version-field.yml | 16 ---- .../removal-manage-premium-required-pipelines.yml | 18 ---- .../removal_manage_optional_pat_expiration.yml | 13 --- .../removal_manage_repository_push_audit_event.yml | 17 ---- .../15_0/removal_manage_ssh_expiration.yml | 13 --- .../removal_manage_status_check_passed_status.yml | 25 ------ data/removals/15_10/15_10-non-public-artifacts.yml | 25 ------ data/removals/15_11/15-11-opensuse-15-3.yml | 14 ---- .../15_11/15-11-project-export-import-ndjson.yml | 16 ---- .../15_2/removal-outdated-browser-support.yml | 20 ----- .../15_3/15-3-vulnerability-report-state-sort.yml | 25 ------ .../15_3/15-3-vulnerability-report-tool-sort.yml | 26 ------ data/removals/15_3/removal_debian9.yml | 6 -- .../15_4/15-4-sast-analyzer-consolidation.yml | 30 ------- .../15_6/15-6-nfs-git-repository-storage.yml | 32 ------- ...e-expansion-file-type-variables-ci-pipeline.yml | 20 ----- .../15_7/15-7-remove-flowdock-integration.yml | 18 ---- .../15-8-auto-deploy-helm-chart-cilium-policy.yml | 16 ---- .../15_8/15-8-group-export-import-ndjson.yml | 16 ---- data/removals/15_9/15-9-live-preview.yml | 11 --- data/removals/15_9/15-9-omniauth-authentiq.yml | 11 --- data/removals/15_9/15-9-omniauth-shibboleth.yml | 11 --- ...ineSecurityReportFinding-name-GraphQL-field.yml | 10 --- .../16-0-Security-report-schemas-version-14.yml | 11 --- data/removals/16_0/16-0-api-lint-removal.yml | 41 --------- .../16_0/16-0-auto-deploy-postgres-enabled.yml | 16 ---- .../16_0/16-0-azure-storage-driver-registry.yml | 12 --- data/removals/16_0/16-0-cas3-authentication.yml | 23 ----- .../16_0/16-0-ci-builds-column-validations.yml | 24 ------ ...16-0-ci-cd-settings-update-mutation-renamed.yml | 17 ---- .../16_0/16-0-conan-search-limited-to-project.yml | 11 --- data/removals/16_0/16-0-cs-docker-variables.yml | 31 ------- .../16_0/16-0-dast-api-variable-removal.yml | 13 --- .../16-0-dependency-scanning-java-versions.yml | 19 ----- ...ternal-field-grapql-release-asset-link-type.yml | 11 --- ...0-external-field-releases-release-links-api.yml | 11 --- .../16_0/16-0-gitaly-legacy-config-vars.yml | 19 ----- data/removals/16_0/16-0-gitlab-com-importer.yml | 16 ---- data/removals/16_0/16-0-grafana-chart.yml | 19 ----- .../16-0-graphql-dora-environment-tier-param.yml | 14 ---- .../16-0-import-bare-repositories-rake-task.yml | 25 ------ .../16-0-jira-github-enterprise-dvcs-connector.yml | 10 --- data/removals/16_0/16-0-job_age.yml | 11 --- data/removals/16_0/16-0-licenses-check.yml | 10 --- data/removals/16_0/16-0-limit-ci-job-token.yml | 32 ------- data/removals/16_0/16-0-managed-licenses-api.yml | 14 ---- .../16_0/16-0-non-expiring-access-tokens.yml | 19 ----- .../16-0-operations-access-level-api-field.yml | 16 ---- data/removals/16_0/16-0-phabricator-importer.yml | 13 --- .../removals/16_0/16-0-pipeline_activity_limit.yml | 12 --- data/removals/16_0/16-0-postgresql-12.yml | 17 ---- .../16-0-pull-thru-cache-container-registry.yml | 11 --- data/removals/16_0/16-0-redis-5.yml | 14 ---- data/removals/16_0/16-0-redis-config-env.yml | 13 --- data/removals/16_0/16-0-redis-localhost.yml | 16 ---- data/removals/16_0/16-0-removal-variables.yml | 29 ------- ...6-0-remove-embed-grafana-panels-in-markdown.yml | 13 --- .../16-0-remove-legacy-gitaly-config-structure.yml | 22 ----- ...6-0-remove-legacy-praefect-config-structure.yml | 22 ----- data/removals/16_0/16-0-remove-metrics.yml | 24 ------ ...16-0-remove-praefect-custom-metric-endpoint.yml | 18 ---- ...0-restrict-imports-to-maintainers-and-above.yml | 12 --- .../16_0/16-0-sast-analyzer-consolidation.yml | 21 ----- .../removals/16_0/16-0-secure-template-changes.yml | 27 ------ data/removals/16_0/16-0-self-monitor-removal.yml | 9 -- .../16_0/16-0-source-code-approvals-endpoint.yml | 30 ------- .../removals/16_0/16-0-source-code-branch-push.yml | 16 ---- data/removals/16_0/16-0-source-code-routes.yml | 36 -------- data/removals/16_0/16-0-starboard-directive.yml | 19 ----- .../16_0/16-0-terraform-latest-stable-change.yml | 21 ----- data/removals/16_0/16-0-ttl-days-removal.yml | 16 ---- .../16_0/16-0-vulnerability-confidence-field.yml | 11 --- ...ulnerabilityFindingDismiss-GraphQL-mutation.yml | 11 --- .../16-0-vulnerabilityFindingDismiss-mutation.yml | 11 --- data/removals/16_0/16-00-JWT-limit-setting.yml | 21 ----- .../16_0/16.0-config-fields-runner-helm-chart.yml | 39 --------- data/removals/16_0/16.0-docker-ssh-executors.yml | 9 -- .../16_0/16.0-eol-windows-server-2004-and-20H2.yml | 9 -- .../16_0/16.0-pre-clone-script-gitlab-saas.yml | 9 -- ....0-runner-api-does-not-return-paused-active.yml | 12 --- data/removals/templates/_removal_template.md.erb | 57 ------------- data/removals/templates/example.yml | 45 ---------- data/whats_new/202011230001_13_06.yml | 2 +- data/whats_new/202105220001_13_12.yml | 2 +- data/whats_new/202106220001_14_0.yml | 4 +- data/whats_new/202107220001_14_1.yml | 2 +- data/whats_new/202108190001_14_02.yml | 2 +- data/whats_new/202202210001_14_08.yml | 2 +- data/whats_new/2022082200001_15_03.yml | 2 +- data/whats_new/20230220001_15_08.yml | 2 +- data/whats_new/202306220001_16_1.yml | 98 ++++++++++++++++++++++ 220 files changed, 214 insertions(+), 3034 deletions(-) create mode 100644 data/deprecations/ 16-2-cirunner_fields.yml delete mode 100644 data/deprecations/15-9-accessibility-testing-deprecation.yml delete mode 100644 data/deprecations/15-9-browser-performance-testing-deprecation.yml delete mode 100644 data/deprecations/15-9-load-performance-testing-deprecation.yml create mode 100644 data/deprecations/16-1-deprecate-message-from-vulnerabilitycreate.yml create mode 100644 data/deprecations/16-2-agentk-builtin-gitops.yml create mode 100644 data/deprecations/16-2-deprecation-omniauth-facebook.yml create mode 100644 data/deprecations/16-2-registry-size-estimated-graphql-field.yml create mode 100644 data/deprecations/16_2-custom_sign_in_fields.yml delete mode 100644 data/removals/14_0/14_0-ds-deprecations.yml delete mode 100644 data/removals/14_0/14_0-lc-deprecations.yml delete mode 100644 data/removals/14_0/change_default_branch_name_to_main.yml delete mode 100644 data/removals/14_0/create-code-review-draft-wip.yml delete mode 100644 data/removals/14_0/create-code-review-w-parameter-removal.yml delete mode 100644 data/removals/14_0/deprecation_bump_terraform_template_version.yml delete mode 100644 data/removals/14_0/deprecation_manage_access_14_0.yml delete mode 100644 data/removals/14_0/deprecation_update_cicd_templates_to_stop_using_hardcode_master.yml delete mode 100644 data/removals/14_0/deuley_servicetemplates_removal.yml delete mode 100644 data/removals/14_0/release_announce_deprecation_of_release_notes_api.yml delete mode 100644 data/removals/14_0/release_deprecation_auto-deploy-image.yml delete mode 100644 data/removals/14_0/release_domainsource_configuration_for_gitlab_pages_deprecation.yml delete mode 100644 data/removals/14_0/release_legacy_feature_flags_deprecation.yml delete mode 100644 data/removals/14_0/release_remove_redundant_keyvalue_pair_from_the_payload_of_dora.yml delete mode 100644 data/removals/14_0/removal-geo-fdw-settings.yml delete mode 100644 data/removals/14_0/removal-graphql-fields.yml delete mode 100644 data/removals/14_0/removal-legacy-storage.yml delete mode 100644 data/removals/14_0/removal-protect-features.yml delete mode 100644 data/removals/14_0/removal-sidekiq_experimental_queue_selector.yml delete mode 100644 data/removals/14_0/removal-unicorn.yml delete mode 100644 data/removals/14_0/removal_ci_project_config_path.yml delete mode 100644 data/removals/14_0/removal_enablement_helm2.yml delete mode 100644 data/removals/14_0/removal_enablement_opensuse_15_1.yml delete mode 100644 data/removals/14_0/removal_enablement_pg11.yml delete mode 100644 data/removals/14_0/removal_enablement_ubuntu_16.yml delete mode 100644 data/removals/14_0/removal_repost_static_analysis_notices.yml delete mode 100644 data/removals/14_0/removal_runner_25555.yml delete mode 100644 data/removals/14_0/removal_runner_26036.yml delete mode 100644 data/removals/14_0/removal_runner_26419.yml delete mode 100644 data/removals/14_0/removal_runner_4845.yml delete mode 100644 data/removals/14_0/removal_runner_6413.yml delete mode 100644 data/removals/14_0/removals-14-testing-team.yml delete mode 100644 data/removals/14_0/removals_runner_26651.yml delete mode 100644 data/removals/14_0/removals_runner_26679.yml delete mode 100644 data/removals/14_0/removals_runner_26900.yml delete mode 100644 data/removals/14_0/removals_runner_27175.yml delete mode 100644 data/removals/14_0/removals_runner_27218.yml delete mode 100644 data/removals/14_0/removals_runner_27551.yml delete mode 100644 data/removals/14_0/removals_runner_27899.yml delete mode 100644 data/removals/14_0/remove-sql-elector.yml delete mode 100644 data/removals/14_0/remove_dast_env_variables.yml delete mode 100644 data/removals/14_0/remove_dast_legacy_domain_validation.yml delete mode 100644 data/removals/14_0/remove_dast_legacy_report_fields.yml delete mode 100644 data/removals/14_0/remove_dast_spider_host_reset.yml delete mode 100644 data/removals/14_0/remove_dast_template_stages.yml delete mode 100644 data/removals/14_0/remove_optimize_api.yml delete mode 100644 data/removals/14_0/remove_terraform_template.yml delete mode 100644 data/removals/14_0/verify-ci-removal-parametertrace.yml delete mode 100644 data/removals/14_0/verify-ci-removalpipelineservice.yml delete mode 100644 data/removals/14_1/removal-memory-prometheus-options-source.yml delete mode 100644 data/removals/14_1/removal-outdated-browser-support.yml delete mode 100644 data/removals/14_10/14-10-package-permissions-composer-change.yml delete mode 100644 data/removals/14_2/removal-verify-build-log.yml delete mode 100644 data/removals/14_3/removal-limit-tags-to-50.yml delete mode 100644 data/removals/14_3/removal-verify-pe-pipelinefindername.yml delete mode 100644 data/removals/14_3/removal_legacy_storage_setting.yml delete mode 100644 data/removals/14_6/limit_trigger_pipelines.yml delete mode 100644 data/removals/14_6/removal-release-cli-s3.yml delete mode 100644 data/removals/14_9/removal_monitor_respond_integrated_error_tracking.yml delete mode 100644 data/removals/15_0/15-0-Legacy-approval-status-names-from-License-Compliance-API.yml delete mode 100644 data/removals/15_0/15-0-Pseudonymizer.yml delete mode 100644 data/removals/15_0/15-0-Retire-js-analyzer.yml delete mode 100644 data/removals/15_0/15-0-SLES-12-SP2.yml delete mode 100644 data/removals/15_0/15-0-advanced-search-elasticsearch-6-8.yml delete mode 100644 data/removals/15_0/15-0-bundler-audit.yml delete mode 100644 data/removals/15_0/15-0-configure-self-managed-cert-based-kube-feature-flag.yml delete mode 100644 data/removals/15_0/15-0-container-registry-htpasswd.yml delete mode 100644 data/removals/15_0/15-0-custom_hooks_dir.yml delete mode 100644 data/removals/15_0/15-0-database-deprecate-legacy-database-conf.yml delete mode 100644 data/removals/15_0/15-0-dependency-scanning-default-java-version.yml delete mode 100644 data/removals/15_0/15-0-dependency-scanning-python-image.yml delete mode 100644 data/removals/15_0/15-0-ds-default-analyzers.yml delete mode 100644 data/removals/15_0/15-0-geo-remove-db-rake-tasks.yml delete mode 100644 data/removals/15_0/15-0-geo-remove-promote-db.yml delete mode 100644 data/removals/15_0/15-0-geo-remove-promote-to-primary-node.yml delete mode 100644 data/removals/15_0/15-0-gitaly-internal-socket-dir.yml delete mode 100644 data/removals/15_0/15-0-managed-cluster-applications.yml delete mode 100644 data/removals/15_0/15-0-merge-commit-message.yml delete mode 100644 data/removals/15_0/15-0-oauth-implicit-grant.yml delete mode 100644 data/removals/15_0/15-0-oauth-tokens-no-expiry.yml delete mode 100644 data/removals/15_0/15-0-omniauth-kerberos-gem.yml delete mode 100644 data/removals/15_0/15-0-package-container-registry-group-api.yml delete mode 100644 data/removals/15_0/15-0-package-settings-permissions.yml delete mode 100644 data/removals/15_0/15-0-praefect-database-no-proxy.yml delete mode 100644 data/removals/15_0/15-0-praefect-virtual-storage.yml delete mode 100644 data/removals/15_0/15-0-protect-cns-chs.yml delete mode 100644 data/removals/15_0/15-0-protect-vulnerability-check.yml delete mode 100644 data/removals/15_0/15-0-removal-artifacts-keyword.yml delete mode 100644 data/removals/15_0/15-0-removal-testcoveragesetting.yml delete mode 100644 data/removals/15_0/15-0-remove-background-upload-object-storage.yml delete mode 100644 data/removals/15_0/15-0-remove-dependency-proxy-feature-flag.yml delete mode 100644 data/removals/15_0/15-0-remove-replicaiton-detail-routes.yml delete mode 100644 data/removals/15_0/15-0-remove-versions-packagetype.yml delete mode 100644 data/removals/15_0/15-0-remove_ff_push_rules_supersede_code_owners.yml delete mode 100644 data/removals/15_0/15-0-request-profiling.yml delete mode 100644 data/removals/15_0/15-0-runner-api-status-renames-not_connected.yml delete mode 100644 data/removals/15_0/15-0-runner-disable-strict-host-key-check.yml delete mode 100644 data/removals/15_0/15-0-runner_api_new_stale_status_breaking_change.yml delete mode 100644 data/removals/15_0/15-0-sast-dotnet-21.yml delete mode 100644 data/removals/15_0/15-0-sast-spotbugs-java-8.yml delete mode 100644 data/removals/15_0/15-0-secret-detection-configurations.yml delete mode 100644 data/removals/15_0/15-0-serverless.yml delete mode 100644 data/removals/15_0/15-0-sidekiq-metrics-health-check-config.yml delete mode 100644 data/removals/15_0/15-0-static-site-editor.yml delete mode 100644 data/removals/15_0/15-0-tracing.yml delete mode 100644 data/removals/15_0/15-0-type.yml delete mode 100644 data/removals/15_0/15_0-logging.yml delete mode 100644 data/removals/15_0/15_0-remove-pipelines-from-version-field.yml delete mode 100644 data/removals/15_0/removal-manage-premium-required-pipelines.yml delete mode 100644 data/removals/15_0/removal_manage_optional_pat_expiration.yml delete mode 100644 data/removals/15_0/removal_manage_repository_push_audit_event.yml delete mode 100644 data/removals/15_0/removal_manage_ssh_expiration.yml delete mode 100644 data/removals/15_0/removal_manage_status_check_passed_status.yml delete mode 100644 data/removals/15_10/15_10-non-public-artifacts.yml delete mode 100644 data/removals/15_11/15-11-opensuse-15-3.yml delete mode 100644 data/removals/15_11/15-11-project-export-import-ndjson.yml delete mode 100644 data/removals/15_2/removal-outdated-browser-support.yml delete mode 100644 data/removals/15_3/15-3-vulnerability-report-state-sort.yml delete mode 100644 data/removals/15_3/15-3-vulnerability-report-tool-sort.yml delete mode 100644 data/removals/15_3/removal_debian9.yml delete mode 100644 data/removals/15_4/15-4-sast-analyzer-consolidation.yml delete mode 100644 data/removals/15_6/15-6-nfs-git-repository-storage.yml delete mode 100644 data/removals/15_7/15-7-remove-expansion-file-type-variables-ci-pipeline.yml delete mode 100644 data/removals/15_7/15-7-remove-flowdock-integration.yml delete mode 100644 data/removals/15_8/15-8-auto-deploy-helm-chart-cilium-policy.yml delete mode 100644 data/removals/15_8/15-8-group-export-import-ndjson.yml delete mode 100644 data/removals/15_9/15-9-live-preview.yml delete mode 100644 data/removals/15_9/15-9-omniauth-authentiq.yml delete mode 100644 data/removals/15_9/15-9-omniauth-shibboleth.yml delete mode 100644 data/removals/16_0/16-0-PipelineSecurityReportFinding-name-GraphQL-field.yml delete mode 100644 data/removals/16_0/16-0-Security-report-schemas-version-14.yml delete mode 100644 data/removals/16_0/16-0-api-lint-removal.yml delete mode 100644 data/removals/16_0/16-0-auto-deploy-postgres-enabled.yml delete mode 100644 data/removals/16_0/16-0-azure-storage-driver-registry.yml delete mode 100644 data/removals/16_0/16-0-cas3-authentication.yml delete mode 100644 data/removals/16_0/16-0-ci-builds-column-validations.yml delete mode 100644 data/removals/16_0/16-0-ci-cd-settings-update-mutation-renamed.yml delete mode 100644 data/removals/16_0/16-0-conan-search-limited-to-project.yml delete mode 100644 data/removals/16_0/16-0-cs-docker-variables.yml delete mode 100644 data/removals/16_0/16-0-dast-api-variable-removal.yml delete mode 100644 data/removals/16_0/16-0-dependency-scanning-java-versions.yml delete mode 100644 data/removals/16_0/16-0-external-field-grapql-release-asset-link-type.yml delete mode 100644 data/removals/16_0/16-0-external-field-releases-release-links-api.yml delete mode 100644 data/removals/16_0/16-0-gitaly-legacy-config-vars.yml delete mode 100644 data/removals/16_0/16-0-gitlab-com-importer.yml delete mode 100644 data/removals/16_0/16-0-grafana-chart.yml delete mode 100644 data/removals/16_0/16-0-graphql-dora-environment-tier-param.yml delete mode 100644 data/removals/16_0/16-0-import-bare-repositories-rake-task.yml delete mode 100644 data/removals/16_0/16-0-jira-github-enterprise-dvcs-connector.yml delete mode 100644 data/removals/16_0/16-0-job_age.yml delete mode 100644 data/removals/16_0/16-0-licenses-check.yml delete mode 100644 data/removals/16_0/16-0-limit-ci-job-token.yml delete mode 100644 data/removals/16_0/16-0-managed-licenses-api.yml delete mode 100644 data/removals/16_0/16-0-non-expiring-access-tokens.yml delete mode 100644 data/removals/16_0/16-0-operations-access-level-api-field.yml delete mode 100644 data/removals/16_0/16-0-phabricator-importer.yml delete mode 100644 data/removals/16_0/16-0-pipeline_activity_limit.yml delete mode 100644 data/removals/16_0/16-0-postgresql-12.yml delete mode 100644 data/removals/16_0/16-0-pull-thru-cache-container-registry.yml delete mode 100644 data/removals/16_0/16-0-redis-5.yml delete mode 100644 data/removals/16_0/16-0-redis-config-env.yml delete mode 100644 data/removals/16_0/16-0-redis-localhost.yml delete mode 100644 data/removals/16_0/16-0-removal-variables.yml delete mode 100644 data/removals/16_0/16-0-remove-embed-grafana-panels-in-markdown.yml delete mode 100644 data/removals/16_0/16-0-remove-legacy-gitaly-config-structure.yml delete mode 100644 data/removals/16_0/16-0-remove-legacy-praefect-config-structure.yml delete mode 100644 data/removals/16_0/16-0-remove-metrics.yml delete mode 100644 data/removals/16_0/16-0-remove-praefect-custom-metric-endpoint.yml delete mode 100644 data/removals/16_0/16-0-restrict-imports-to-maintainers-and-above.yml delete mode 100644 data/removals/16_0/16-0-sast-analyzer-consolidation.yml delete mode 100644 data/removals/16_0/16-0-secure-template-changes.yml delete mode 100644 data/removals/16_0/16-0-self-monitor-removal.yml delete mode 100644 data/removals/16_0/16-0-source-code-approvals-endpoint.yml delete mode 100644 data/removals/16_0/16-0-source-code-branch-push.yml delete mode 100644 data/removals/16_0/16-0-source-code-routes.yml delete mode 100644 data/removals/16_0/16-0-starboard-directive.yml delete mode 100644 data/removals/16_0/16-0-terraform-latest-stable-change.yml delete mode 100644 data/removals/16_0/16-0-ttl-days-removal.yml delete mode 100644 data/removals/16_0/16-0-vulnerability-confidence-field.yml delete mode 100644 data/removals/16_0/16-0-vulnerabilityFindingDismiss-GraphQL-mutation.yml delete mode 100644 data/removals/16_0/16-0-vulnerabilityFindingDismiss-mutation.yml delete mode 100644 data/removals/16_0/16-00-JWT-limit-setting.yml delete mode 100644 data/removals/16_0/16.0-config-fields-runner-helm-chart.yml delete mode 100644 data/removals/16_0/16.0-docker-ssh-executors.yml delete mode 100644 data/removals/16_0/16.0-eol-windows-server-2004-and-20H2.yml delete mode 100644 data/removals/16_0/16.0-pre-clone-script-gitlab-saas.yml delete mode 100644 data/removals/16_0/16.0-runner-api-does-not-return-paused-active.yml delete mode 100644 data/removals/templates/_removal_template.md.erb delete mode 100644 data/removals/templates/example.yml create mode 100644 data/whats_new/202306220001_16_1.yml (limited to 'data') diff --git a/data/deprecations/ 16-2-cirunner_fields.yml b/data/deprecations/ 16-2-cirunner_fields.yml new file mode 100644 index 00000000000..1d43ed1b7c9 --- /dev/null +++ b/data/deprecations/ 16-2-cirunner_fields.yml @@ -0,0 +1,13 @@ +- title: "Deprecate `CiRunner` GraphQL fields duplicated in `CiRunnerManager`" # (required) The name of the feature to be deprecated + announcement_milestone: "16.2" # (required) The milestone when this feature was first announced as deprecated. + announcement_date: "2023-07-22" # (required) The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_milestone: "17.0" # (required) The milestone when this feature is planned to be removed + removal_date: "2024-05-22" # (required) The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + breaking_change: true # (required) If this deprecation is a breaking change, set this value to true + reporter: DarrenEastman # (required) GitLab username of the person reporting the deprecation + stage: Verify # (required) String value of the stage that the feature was created in. e.g., Growth + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/41518 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + These fields (`architectureName`, `ipAddress`, `platformName`, `revision`, `version`) are now deprecated from the [GraphQL `CiRunner`](https://docs.gitlab.com/ee/api/graphql/reference/#cirunner) type as they are duplicated with the introduction of runner managers grouped within a runner configuration. + end_of_support_milestone: "17.0" # (optional) Use "XX.YY" format. The milestone when support for this feature will end. + end_of_support_date: "2024-05-22" # (optional) The date of the milestone release when support for this feature will end. diff --git a/data/deprecations/14-10-old-search-migration-removal.yml b/data/deprecations/14-10-old-search-migration-removal.yml index 4700063e68f..260880dda57 100644 --- a/data/deprecations/14-10-old-search-migration-removal.yml +++ b/data/deprecations/14-10-old-search-migration-removal.yml @@ -3,7 +3,10 @@ removal_milestone: "15.0" breaking_change: true body: | - As Advanced Search migrations usually require support multiple code paths for a long period of time, it’s important to clean those up when we safely can. We use GitLab major version upgrades as a safe time to remove backward compatibility for indices that have not been fully migrated. See the [upgrade documentation](https://docs.gitlab.com/ee/update/index.html#upgrading-to-a-new-major-version) for details. + As Advanced Search migrations usually require support multiple code paths for a long period of time, + it's important to clean those up when we safely can. We use GitLab major version upgrades as a safe + time to remove backward compatibility for indices that have not been fully migrated. See the + [upgrade documentation](https://docs.gitlab.com/ee/update/index.html#upgrading-to-a-new-major-version) for details. stage: enablement tiers: premium, ultimate issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/359133 diff --git a/data/deprecations/14-8-compliance-required-pipeline-configuration-premium.yml b/data/deprecations/14-8-compliance-required-pipeline-configuration-premium.yml index cd94adca75f..67d2c94e776 100644 --- a/data/deprecations/14-8-compliance-required-pipeline-configuration-premium.yml +++ b/data/deprecations/14-8-compliance-required-pipeline-configuration-premium.yml @@ -4,7 +4,7 @@ breaking_change: true reporter: sam.white body: | # Do not modify this line, instead modify the lines below. - 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. + The [required pipeline configuration](https://docs.gitlab.com/ee/administration/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. This change to move the feature to GitLab's Ultimate tier is intended to help our features better align with our [pricing philosophy](https://about.gitlab.com/company/pricing/#three-tiers) as we see demand for this feature originating primarily from executives. diff --git a/data/deprecations/14-8-enforce-pat-expiration.yml b/data/deprecations/14-8-enforce-pat-expiration.yml index 37cf4d827d1..a420f19387d 100644 --- a/data/deprecations/14-8-enforce-pat-expiration.yml +++ b/data/deprecations/14-8-enforce-pat-expiration.yml @@ -9,4 +9,4 @@ Unexpected behavior in a security feature is inherently dangerous, so we have decided to remove this feature. stage: manage issue_url: "https://gitlab.com/gitlab-org/gitlab/-/issues/351962" # (optional) This is a link to the deprecation issue in GitLab - documentation_url: "https://docs.gitlab.com/ee/user/admin_area/settings/account_and_limit_settings.html#allow-expired-personal-access-tokens-to-be-used-deprecated" # (optional) This is a link to the current documentation page + documentation_url: "https://docs.gitlab.com/ee/administration/settings/account_and_limit_settings.html#allow-expired-personal-access-tokens-to-be-used-deprecated" # (optional) This is a link to the current documentation page diff --git a/data/deprecations/14-8-enforce-ssh-expiration.yml b/data/deprecations/14-8-enforce-ssh-expiration.yml index 6a67eee4b5f..c2662aaf3d0 100644 --- a/data/deprecations/14-8-enforce-ssh-expiration.yml +++ b/data/deprecations/14-8-enforce-ssh-expiration.yml @@ -9,4 +9,4 @@ Unexpected behavior in a security feature is inherently dangerous, so we have decided to remove this feature. stage: manage issue_url: "https://gitlab.com/gitlab-org/gitlab/-/issues/351963" # (optional) This is a link to the deprecation issue in GitLab - documentation_url: "https://docs.gitlab.com/ee/user/admin_area/settings/account_and_limit_settings.html#allow-expired-ssh-keys-to-be-used-deprecated" # (optional) This is a link to the current documentation page + documentation_url: "https://docs.gitlab.com/ee/administration/settings/account_and_limit_settings.html#allow-expired-ssh-keys-to-be-used-deprecated" # (optional) This is a link to the current documentation page diff --git a/data/deprecations/14-8-sast-analyzer-removals.yml b/data/deprecations/14-8-sast-analyzer-removals.yml index 3ebfd23beb5..427833d569e 100644 --- a/data/deprecations/14-8-sast-analyzer-removals.yml +++ b/data/deprecations/14-8-sast-analyzer-removals.yml @@ -17,7 +17,6 @@ NOTE: This change was originally planned for GitLab 15.0 and was postponed to GitLab 15.4. - See [the removal notice](./removals.md#sast-analyzer-consolidation-and-cicd-template-changes) for further details. These analyzers will be removed from the [GitLab-managed SAST CI/CD template](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Security/SAST.gitlab-ci.yml) and replaced with the [Semgrep-based analyzer](https://gitlab.com/gitlab-org/security-products/analyzers/semgrep). Effective immediately, they will receive only security updates; other routine improvements or updates are not guaranteed. @@ -30,8 +29,8 @@ If you've already dismissed a vulnerability finding from one of the deprecated analyzers, the replacement attempts to respect your previous dismissal. The system behavior depends on: - - whether you’ve excluded the Semgrep-based analyzer from running in the past. - - which analyzer first discovered the vulnerabilities shown in the project’s Vulnerability Report. + - whether you've excluded the Semgrep-based analyzer from running in the past. + - which analyzer first discovered the vulnerabilities shown in the project's Vulnerability Report. See [Vulnerability translation documentation](https://docs.gitlab.com/ee/user/application_security/sast/analyzers.html#vulnerability-translation) for further details. diff --git a/data/deprecations/14-9-deprecate-testcoveragesetting.yml b/data/deprecations/14-9-deprecate-testcoveragesetting.yml index 1f50aab1c27..52f58fc707e 100644 --- a/data/deprecations/14-9-deprecate-testcoveragesetting.yml +++ b/data/deprecations/14-9-deprecate-testcoveragesetting.yml @@ -8,6 +8,6 @@ [project setting for test coverage parsing](https://docs.gitlab.com/ee/ci/pipelines/settings.html#add-test-coverage-results-using-project-settings-removed) is being removed. - Instead, using the project’s `.gitlab-ci.yml`, provide a regular expression with the `coverage` keyword to set + Instead, using the project's `.gitlab-ci.yml`, provide a regular expression with the `coverage` keyword to set testing coverage results in merge requests. stage: verify diff --git a/data/deprecations/15-0-oauth-noexpiry.yml b/data/deprecations/15-0-oauth-noexpiry.yml index e27ac4d8725..1eeb912a588 100644 --- a/data/deprecations/15-0-oauth-noexpiry.yml +++ b/data/deprecations/15-0-oauth-noexpiry.yml @@ -11,7 +11,7 @@ tokens before GitLab 15.0 is released: 1. Edit the application. - 1. Select **Expire access tokens** to enable them. Tokens must be revoked or they don’t expire. + 1. Select **Expire access tokens** to enable them. Tokens must be revoked or they don't expire. # The following items are not published on the docs page, but may be used in the future. reporter: hsutor diff --git a/data/deprecations/15-3-pipeline_activity_limit.yml b/data/deprecations/15-3-pipeline_activity_limit.yml index ea7d0476910..c0e37292d06 100644 --- a/data/deprecations/15-3-pipeline_activity_limit.yml +++ b/data/deprecations/15-3-pipeline_activity_limit.yml @@ -25,7 +25,7 @@ stage: Verify # (required) String value of the stage that the feature was created in. e.g., Growth issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/368195 # (required) Link to the deprecation issue in GitLab body: | # (required) Do not modify this line, instead modify the lines below. - The [**Maximum number of active pipelines per project** limit](https://docs.gitlab.com/ee/user/admin_area/settings/continuous_integration.html#set-cicd-limits) was never enabled by default and will be removed in GitLab 16.0. This limit can also be configured in the Rails console under [`ci_active_pipelines`](https://docs.gitlab.com/ee/administration/instance_limits.html#number-of-pipelines-running-concurrently). Instead, use the other recommended rate limits that offer similar protection: + The [**Maximum number of active pipelines per project** limit](https://docs.gitlab.com/ee/administration/settings/continuous_integration.html#set-cicd-limits) was never enabled by default and will be removed in GitLab 16.0. This limit can also be configured in the Rails console under [`ci_active_pipelines`](https://docs.gitlab.com/ee/administration/instance_limits.html#number-of-pipelines-running-concurrently). Instead, use the other recommended rate limits that offer similar protection: - - [**Pipelines rate limits**](https://docs.gitlab.com/ee/user/admin_area/settings/rate_limit_on_pipelines_creation.html). - - [**Total number of jobs in currently active pipelines**](https://docs.gitlab.com/ee/user/admin_area/settings/continuous_integration.html#set-cicd-limits). + - [**Pipelines rate limits**](https://docs.gitlab.com/ee/administration/settings/rate_limit_on_pipelines_creation.html). + - [**Total number of jobs in currently active pipelines**](https://docs.gitlab.com/ee/administration/settings/continuous_integration.html#set-cicd-limits). diff --git a/data/deprecations/15-9-accessibility-testing-deprecation.yml b/data/deprecations/15-9-accessibility-testing-deprecation.yml deleted file mode 100644 index 74fb61ed2fc..00000000000 --- a/data/deprecations/15-9-accessibility-testing-deprecation.yml +++ /dev/null @@ -1,26 +0,0 @@ -# -# REQUIRED FIELDS -# -- title: "Accessibility Testing is deprecated" # (required) Clearly explain the change, or planned change. For example, "The `confidential` field for a `Note` is deprecated" or "CI/CD job names will be limited to 250 characters." - announcement_milestone: "15.9" # (required) The milestone when this feature was first announced as deprecated. - removal_milestone: "17.0" # (required) The milestone when this feature is planned to be removed - breaking_change: true # (required) Change to false if this is not a breaking change. - reporter: jocelynjane # (required) GitLab username of the person reporting the change - stage: Verify # (required) String value of the stage that the feature was created in. e.g., Growth - issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/390424 # (required) Link to the deprecation issue in GitLab - body: | # (required) Do not modify this line, instead modify the lines below. - Due to low customer usage, Accessibility Testing is deprecated and will be removed. There is no planned replacement and users should stop using Accessibility Testing before GitLab 17.0. -# -# OPTIONAL END OF SUPPORT FIELDS -# -# If an End of Support period applies, the announcement should be shared with GitLab Support -# in the `#spt_managers` channel in Slack, and mention `@gitlab-com/support` in this MR. -# - end_of_support_milestone: # (optional) Use "XX.YY" format. The milestone when support for this feature will end. - # - # OTHER OPTIONAL FIELDS - # - tiers: # (optional - may be required in the future) An array of tiers that the feature is available in currently. e.g., [Free, Silver, Gold, Core, Premium, Ultimate] - documentation_url: https://docs.gitlab.com/ee/ci/testing/accessibility_testing.html # (optional) This is a link to the current documentation page - image_url: # (optional) This is a link to a thumbnail image depicting the feature - video_url: # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg diff --git a/data/deprecations/15-9-browser-performance-testing-deprecation.yml b/data/deprecations/15-9-browser-performance-testing-deprecation.yml deleted file mode 100644 index a5d7429b56b..00000000000 --- a/data/deprecations/15-9-browser-performance-testing-deprecation.yml +++ /dev/null @@ -1,26 +0,0 @@ -# -# REQUIRED FIELDS -# -- title: "Browser Performance Testing is deprecated" # (required) Clearly explain the change, or planned change. For example, "The `confidential` field for a `Note` is deprecated" or "CI/CD job names will be limited to 250 characters." - announcement_milestone: "15.9" # (required) The milestone when this feature was first announced as deprecated. - removal_milestone: "17.0" # (required) The milestone when this feature is planned to be removed - breaking_change: true # (required) Change to false if this is not a breaking change. - reporter: jocelynjane # (required) GitLab username of the person reporting the change - stage: Verify # (required) String value of the stage that the feature was created in. e.g., Growth - issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/388719 # (required) Link to the deprecation issue in GitLab - body: | # (required) Do not modify this line, instead modify the lines below. - Due to limited customer usage, Browser Performance Testing is deprecated and will be removed. There is no planned replacement and users should stop using Browser Performance Testing before GitLab 17.0. -# -# OPTIONAL END OF SUPPORT FIELDS -# -# If an End of Support period applies, the announcement should be shared with GitLab Support -# in the `#spt_managers` channel in Slack, and mention `@gitlab-com/support` in this MR. -# - end_of_support_milestone: # (optional) Use "XX.YY" format. The milestone when support for this feature will end. - # - # OTHER OPTIONAL FIELDS - # - tiers: Premium # (optional - may be required in the future) An array of tiers that the feature is available in currently. e.g., [Free, Silver, Gold, Core, Premium, Ultimate] - documentation_url: https://docs.gitlab.com/ee/ci/testing/browser_performance_testing.html # (optional) This is a link to the current documentation page - image_url: # (optional) This is a link to a thumbnail image depicting the feature - video_url: # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg diff --git a/data/deprecations/15-9-license-compliance-ci-template.yml b/data/deprecations/15-9-license-compliance-ci-template.yml index edce1062883..9b2ab1cbe90 100644 --- a/data/deprecations/15-9-license-compliance-ci-template.yml +++ b/data/deprecations/15-9-license-compliance-ci-template.yml @@ -1,16 +1,16 @@ - title: "License Compliance CI Template" announcement_milestone: "15.9" - removal_milestone: "16.1" + removal_milestone: "16.3" breaking_change: true reporter: sam.white stage: secure issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/387561 body: | - **Update:** We previously announced we would remove the existing License Compliance CI template in GitLab 16.0. However, due to performance issues with the [license scanning of CycloneDX files](https://docs.gitlab.com/ee/user/compliance/license_scanning_of_cyclonedx_files/) we will do this change in 16.1 instead. + **Update:** We previously announced we would remove the existing License Compliance CI template in GitLab 16.0. However, due to performance issues with the [license scanning of CycloneDX files](https://docs.gitlab.com/ee/user/compliance/license_scanning_of_cyclonedx_files/) we will do this change in 16.3 instead. The GitLab [License Compliance](https://docs.gitlab.com/ee/user/compliance/license_compliance/) CI template is now deprecated and is scheduled for removal in the GitLab 16.1 release. Users who wish to continue using GitLab for License Compliance should remove the License Compliance template from their CI pipeline and add the [Dependency Scanning template](https://docs.gitlab.com/ee/user/application_security/dependency_scanning/#configuration). The Dependency Scanning template is now capable of gathering the required license information so it is no longer necessary to run a separate License Compliance job. The License Compliance CI template should not be removed prior to verifying that the `license_scanning_sbom_scanner` and `package_metadata_synchronization` flags are enabled for the instance and that the instance has been upgraded to a version that supports [the new method of license scanning](https://docs.gitlab.com/ee/user/compliance/license_scanning_of_cyclonedx_files/). - | CI Pipeline Includes | GitLab <= 15.8 | 15.9 <= GitLab < 16.1 | GitLab >= 16.1 | + | CI Pipeline Includes | GitLab <= 15.8 | 15.9 <= GitLab < 16.3 | GitLab >= 16.3 | | ------------- | ------------- | ------------- | ------------- | | Both DS and LS templates | License data from LS job is used | License data from LS job is used | License data from DS job is used | | DS template is included but LS template is not | No license data | License data from DS job is used | License data from DS job is used | diff --git a/data/deprecations/15-9-load-performance-testing-deprecation.yml b/data/deprecations/15-9-load-performance-testing-deprecation.yml deleted file mode 100644 index 77b56c69f92..00000000000 --- a/data/deprecations/15-9-load-performance-testing-deprecation.yml +++ /dev/null @@ -1,26 +0,0 @@ -# -# REQUIRED FIELDS -# -- title: "Load Performance Testing is deprecated" # (required) Clearly explain the change, or planned change. For example, "The `confidential` field for a `Note` is deprecated" or "CI/CD job names will be limited to 250 characters." - announcement_milestone: "15.9" # (required) The milestone when this feature was first announced as deprecated. - removal_milestone: "17.0" # (required) The milestone when this feature is planned to be removed - breaking_change: true # (required) Change to false if this is not a breaking change. - reporter: jocelynjane # (required) GitLab username of the person reporting the change - stage: Verify # (required) String value of the stage that the feature was created in. e.g., Growth - issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/388723 # (required) Link to the deprecation issue in GitLab - body: | # (required) Do not modify this line, instead modify the lines below. - Due to low customer usage, Load Performance Testing is deprecated and will be removed. There is no planned replacement and users should stop using Load Performance Testing before GitLab 17.0. -# -# OPTIONAL END OF SUPPORT FIELDS -# -# If an End of Support period applies, the announcement should be shared with GitLab Support -# in the `#spt_managers` channel in Slack, and mention `@gitlab-com/support` in this MR. -# - end_of_support_milestone: # (optional) Use "XX.YY" format. The milestone when support for this feature will end. - # - # OTHER OPTIONAL FIELDS - # - tiers: Premium # (optional - may be required in the future) An array of tiers that the feature is available in currently. e.g., [Free, Silver, Gold, Core, Premium, Ultimate] - documentation_url: https://docs.gitlab.com/ee/ci/testing/load_performance_testing.html # (optional) This is a link to the current documentation page - image_url: # (optional) This is a link to a thumbnail image depicting the feature - video_url: # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg diff --git a/data/deprecations/15-9-required-pipeline-configuration.yml b/data/deprecations/15-9-required-pipeline-configuration.yml index 03ebaab555d..f43c7dd068a 100644 --- a/data/deprecations/15-9-required-pipeline-configuration.yml +++ b/data/deprecations/15-9-required-pipeline-configuration.yml @@ -24,6 +24,6 @@ # OTHER OPTIONAL FIELDS # tiers: # (optional - may be required in the future) An array of tiers that the feature is available in currently. e.g., [Free, Silver, Gold, Core, Premium, Ultimate] - documentation_url: https://docs.gitlab.com/ee/user/admin_area/settings/continuous_integration.html#required-pipeline-configuration # (optional) This is a link to the current documentation page + documentation_url: https://docs.gitlab.com/ee/administration/settings/continuous_integration.html#required-pipeline-configuration # (optional) This is a link to the current documentation page image_url: # (optional) This is a link to a thumbnail image depicting the feature video_url: # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg diff --git a/data/deprecations/16-0-deprecate-sidekiq-delivery-method-for-mailroom.yml b/data/deprecations/16-0-deprecate-sidekiq-delivery-method-for-mailroom.yml index a7715f89abb..d0795687b50 100644 --- a/data/deprecations/16-0-deprecate-sidekiq-delivery-method-for-mailroom.yml +++ b/data/deprecations/16-0-deprecate-sidekiq-delivery-method-for-mailroom.yml @@ -34,7 +34,10 @@ If you run GitLab on more than one machine, you need to provide the secret key file for each machine. - We highly encourage GitLab administrators to start using the `webhook` delivery method for + We encourage GitLab administrators to switch to the webhook delivery method for `incoming_email_delivery_method` and `service_desk_email_delivery_method` instead of `sidekiq`. + + [Issue 393157](https://gitlab.com/gitlab-org/gitlab/-/issues/393157) tracks improving email ingestion in general. + We hope this will simplify infrastructure setup and add several improvements to how you manage GitLab in the near future. tiers: [Free, Silver, Gold, Core, Premium, Ultimate] documentation_url: https://docs.gitlab.com/ee/user/project/service_desk.html#use-a-custom-email-address diff --git a/data/deprecations/16-1-deprecate-message-from-vulnerabilitycreate.yml b/data/deprecations/16-1-deprecate-message-from-vulnerabilitycreate.yml new file mode 100644 index 00000000000..505a6b1bdd9 --- /dev/null +++ b/data/deprecations/16-1-deprecate-message-from-vulnerabilitycreate.yml @@ -0,0 +1,10 @@ +- title: "Deprecate `message` field from Vulnerability Management features" + announcement_milestone: "16.1" + removal_milestone: "17.0" + breaking_change: true + reporter: abellucci + stage: Govern + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/411573 + body: | # (required) Do not modify this line, instead modify the lines below. + This MR deprecates the `message` field on the `VulnerabilityCreate` GraphQL mutation, and in the `AdditionalInfo` column of the vulnerability export. + The message field was removed from security reports schema in GitLab 16.0 and is no longer being used elsewhere. diff --git a/data/deprecations/16-1-non-decomposed-mode-deprecation.yml b/data/deprecations/16-1-non-decomposed-mode-deprecation.yml index 963fc0d8230..83f99fc2dbd 100644 --- a/data/deprecations/16-1-non-decomposed-mode-deprecation.yml +++ b/data/deprecations/16-1-non-decomposed-mode-deprecation.yml @@ -6,4 +6,12 @@ stage: data_stores issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/411239 body: | - The option to run self-managed installations of GitLab on a single database is now deprecated. From GitLab 17.0, we will require a [separate database for CI features](https://gitlab.com/groups/gitlab-org/-/epics/7509). With this change, self-managed versions of GitLab will behave similarly to GitLab.com. This change applies to installation methods with Omnibus GitLab, GitLab Helm chart, GitLab Operator, GitLab Docker images, and installation from source. Before upgrading to GitLab 17.0, please ensure [migration](https://docs.gitlab.com/ee/administration/postgresql/multiple_databases.html) to two databases. + From GitLab 17.0, we will require a [separate database for CI features](https://gitlab.com/groups/gitlab-org/-/epics/7509). + We recommend running both databases on the same Postgres instance(s) due to ease of management for most deployments. + + We are providing this as an informational advance notice but we do not recommend taking action yet. + We will have another update communicated (as well as the deprecation note) when we recommend admins to start the migration process. + + This change provides additional scalability for the largest of GitLab instances, like GitLab.com. + This change applies to all installation methods: Omnibus GitLab, GitLab Helm chart, GitLab Operator, GitLab Docker images, and installation from source. + Before upgrading to GitLab 17.0, please ensure you have [migrated](https://docs.gitlab.com/ee/administration/postgresql/multiple_databases.html) to two databases. diff --git a/data/deprecations/16-2-agentk-builtin-gitops.yml b/data/deprecations/16-2-agentk-builtin-gitops.yml new file mode 100644 index 00000000000..297c069bc47 --- /dev/null +++ b/data/deprecations/16-2-agentk-builtin-gitops.yml @@ -0,0 +1,13 @@ +- title: "The pull-based deployment features of the GitLab agent for Kubernetes is deprecated" + removal_milestone: "17.0" + announcement_milestone: "16.2" + breaking_change: true # (required) Change to false if this is not a breaking change. + reporter: nagyv-gitlab # (required) GitLab username of the person reporting the change + stage: deploy + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/406545 + body: | # (required) Do not modify this line, instead modify the lines below. + We are deprecating the built-in pull-based deployment features of the GitLab agent for Kubernetes in favor of Flux and related integrations. + + The GitLab agent for Kubernetes **is not deprecated**. This change affects only the pull-based functionality of the agent. All other functionality will remain intact, and GitLab will continue to support the agent for Kubernetes. + + If you use the agent for pull-based deployments, you should [migrate to Flux](https://docs.gitlab.com/ee/user/clusters/agent/gitops/agent.html#migrate-to-flux). Because Flux is a mature CNCF project for GitOps, we decided to [integrate Flux with GitLab in February 2023](https://about.gitlab.com/blog/2023/02/08/why-did-we-choose-to-integrate-fluxcd-with-gitlab/). diff --git a/data/deprecations/16-2-deprecation-omniauth-facebook.yml b/data/deprecations/16-2-deprecation-omniauth-facebook.yml new file mode 100644 index 00000000000..f0ef0429a9c --- /dev/null +++ b/data/deprecations/16-2-deprecation-omniauth-facebook.yml @@ -0,0 +1,11 @@ +- title: "OmniAuth Facebook is deprecated" # (required) Clearly explain the change, or planned change. For example, "The `confidential` field for a `Note` is deprecated" or "CI/CD job names will be limited to 250 characters." + removal_milestone: "17.0" # (required) The milestone when this feature is planned to be removed + announcement_milestone: "16.2" # (required) The milestone when this feature was first announced as deprecated. + announcement_date: "2023-07-22" # (required) The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_date: "2024-05-22" # (required) The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + breaking_change: true # (required) Change to false if this is not a breaking change. + reporter: hsutor # (required) GitLab username of the person reporting the change + stage: Manage # (required) String value of the stage that the feature was created in. e.g., Growth + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/416000 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + OmniAuth Facebook support will be removed in GitLab 17.0. The last gem release was in 2021 and it is currently unmaintained. The current usage is less than 0.1%. If you use OmniAuth Facebook, switch to a [supported provider](https://docs.gitlab.com/ee/integration/omniauth.html#supported-providers) in advance of support removal. diff --git a/data/deprecations/16-2-registry-size-estimated-graphql-field.yml b/data/deprecations/16-2-registry-size-estimated-graphql-field.yml new file mode 100644 index 00000000000..a0251040203 --- /dev/null +++ b/data/deprecations/16-2-registry-size-estimated-graphql-field.yml @@ -0,0 +1,11 @@ +- title: "GraphQL field `registrySizeEstimated` has been deprecated" # (required) Actionable title. e.g., The `confidential` field for a `Note` is deprecated. Use `internal` instead. + announcement_milestone: "16.2" # (required) The milestone when this feature was first announced as deprecated. + removal_milestone: "17.0" # (required) The milestone when this feature is planned to be removed + breaking_change: true # (required) If this deprecation is a breaking change, set this value to true + reporter: kpalchyk # (required) GitLab username of the person reporting the deprecation + stage: Package # (required) String value of the stage that the feature was created in. e.g., Growth + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/416509 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + For clarity, the GraphQL field `registrySizeEstimated` was renamed to `containerRegistrySizeIsEstimated`, to match its counterpart. + `registrySizeEstimated` was deprecated in GitLab 16.2 and will be removed in GitLab 17.0. + Use `containerRegistrySizeIsEstimated` introduced in GitLab 16.2 instead. diff --git a/data/deprecations/16_2-custom_sign_in_fields.yml b/data/deprecations/16_2-custom_sign_in_fields.yml new file mode 100644 index 00000000000..80184a3c096 --- /dev/null +++ b/data/deprecations/16_2-custom_sign_in_fields.yml @@ -0,0 +1,11 @@ +- title: 'Deprecated parameters related to custom text in the sign-in page' # (required) The name of the feature to be deprecated + announcement_milestone: '16.2' # (required) The milestone when this feature was first announced as deprecated. + announcement_date: '2023-07-22' # (required) The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + removal_milestone: '17.0' # (required) The milestone when this feature is planned to be removed + removal_date: '2024-04-22' # (required) The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post. + breaking_change: true # (required) If this deprecation is a breaking change, set this value to true + reporter: eduardosanz # (required) GitLab username of the person reporting the deprecation + stage: Manage # (required) String value of the stage that the feature was created in. e.g., Growth + issue_url: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/124461 # (required) Link to the deprecation issue in GitLab + body: | # (required) Do not modify this line, instead modify the lines below. + The parameters, `sign_in_text` and `help_text`, are deprecated in the [Settings API](https://docs.gitlab.com/ee/api/settings.html). To add a custom text to the sign-in and sign-up pages, use the `description` field in the [Appearance API](https://docs.gitlab.com/ee/api/appearance.html). diff --git a/data/deprecations/templates/_deprecation_template.md.erb b/data/deprecations/templates/_deprecation_template.md.erb index 1817942eac5..5261806f49a 100644 --- a/data/deprecations/templates/_deprecation_template.md.erb +++ b/data/deprecations/templates/_deprecation_template.md.erb @@ -5,9 +5,9 @@ info: "See the Technical Writers assigned to Development Guidelines: https://abo toc: false --- -# Deprecations by version +# Deprecations and removals by version -These GitLab features are deprecated and no longer recommended for use. +The following GitLab features are deprecated and no longer recommended for use. Each deprecated feature will be removed in a future release. Some features cause breaking changes when they are removed. @@ -24,8 +24,10 @@ and [GraphQL](https://docs.gitlab.com/ee/api/graphql/removed_items.html) depreca - - - -{::options parse_block_html="true" /} -<% if milestones.any? -%> - <%- milestones.each do |milestone| %> -## Removed in <%= milestone %> - <%- entries.select{|entry| entry["removal_milestone"] == milestone}.each do |removal| %> -### <%= removal["title"]%> - -
-- Announced in: GitLab <%= removal["announcement_milestone"]%> -<% if removal["breaking_change"] -%> -- This is a [breaking change](https://docs.gitlab.com/ee/development/deprecation_guidelines/). 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"]%>). -<%- end -%> -
- -<%= removal["body"] -%><%- end -%><%- end -%> -<%- else -%> -Features scheduled for removal will be listed here, sorted by GitLab version. -<% end -%> diff --git a/data/removals/templates/example.yml b/data/removals/templates/example.yml deleted file mode 100644 index c536d8276d9..00000000000 --- a/data/removals/templates/example.yml +++ /dev/null @@ -1,45 +0,0 @@ -# This is a template for announcing a feature removal or other important change. -# -# Please refer to the deprecation guidelines to confirm your understanding of GitLab's definitions. -# https://docs.gitlab.com/ee/development/deprecation_guidelines/#terminology -# -# If this is a breaking change, it must happen in a major release. -# -# For more information please refer to the handbook documentation here: -# https://about.gitlab.com/handbook/marketing/blog/release-posts/#deprecations-and-other-planned-breaking-change-announcements -# -# Please delete this line and above before submitting your merge request. -# -# REQUIRED FIELDS -# -- title: "Feature A is removed." # (required) Clearly explain the change. For example, "The `confidential` field for a `Note` is removed" or "CI/CD job names are limited to 250 characters." - announcement_milestone: "XX.YY" # (required) The milestone when this feature was deprecated. - removal_milestone: "XX.YY" # (required) The milestone when this feature is being removed. - breaking_change: true # (required) Change to false if this is not a breaking change. - reporter: exampleuser # (required) GitLab username of the person reporting the removal - stage: stage # (required) String value of the stage that the feature was created in. e.g., Growth - issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/000000 # (required) Link to the deprecation issue in GitLab - body: | # (required) Do not modify this line, instead modify the lines below. - -# -# OPTIONAL FIELDS -# - tiers: # (optional - may be required in the future) An array of tiers that the feature is available in currently. e.g., [Free, Silver, Gold, Core, Premium, Ultimate] - documentation_url: # (optional) This is a link to the current documentation page - image_url: # (optional) This is a link to a thumbnail image depicting the feature - video_url: # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg diff --git a/data/whats_new/202011230001_13_06.yml b/data/whats_new/202011230001_13_06.yml index 8701a050d4c..d5c3ebc9696 100644 --- a/data/whats_new/202011230001_13_06.yml +++ b/data/whats_new/202011230001_13_06.yml @@ -59,7 +59,7 @@ self-managed: true gitlab-com: true available_in: [Free, Premium, Ultimate] - documentation_link: https://docs.gitlab.com/ee/user/admin_area/settings/project_integration_management.html + documentation_link: https://docs.gitlab.com/ee/administration/settings/project_integration_management.html image_url: https://about.gitlab.com/images/13_6/project-integration-inheriting-settings.png published_at: 2020-11-22 release: 13.6 diff --git a/data/whats_new/202105220001_13_12.yml b/data/whats_new/202105220001_13_12.yml index bcb2da40f63..78faf0dde8d 100644 --- a/data/whats_new/202105220001_13_12.yml +++ b/data/whats_new/202105220001_13_12.yml @@ -121,7 +121,7 @@ self-managed: true gitlab-com: true available_in: [Free, Premium, Ultimate] - documentation_link: https://docs.gitlab.com/ee/user/admin_area/settings/floc.html + documentation_link: https://docs.gitlab.com/ee/administration/settings/floc.html image_url: https://about.gitlab.com/images/growth/enablement.png published_at: 2021-05-22 release: 13.12 diff --git a/data/whats_new/202106220001_14_0.yml b/data/whats_new/202106220001_14_0.yml index 62bb78cecbb..56244eb65c1 100644 --- a/data/whats_new/202106220001_14_0.yml +++ b/data/whats_new/202106220001_14_0.yml @@ -43,12 +43,12 @@ description: | Code Owners are an important piece of the code review process in GitLab. When code owners are clearly identified, contributors can see who should review contributions to a file or repository. The Code Owners feature can also be used to establish a merge request approval process. Now, you can track which teams across your organization are using the Code Owners feature in their development workflow. - If you would like to drive adoption of Code Owners, sort the DevOps Adoption table by the Code Owners column to find teams that haven't yet adopted the feature so you can easily identify which teams need help getting started. Alternatively, find teams that have successfully configured Code Owners and get tips and feedback. The DevOps Adoption table is available at [the group level](https://docs.gitlab.com/ee/user/group/devops_adoption/) and [the instance level](https://docs.gitlab.com/ee/user/admin_area/analytics/dev_ops_report.html#devops-adoption). + If you would like to drive adoption of Code Owners, sort the DevOps Adoption table by the Code Owners column to find teams that haven't yet adopted the feature so you can easily identify which teams need help getting started. Alternatively, find teams that have successfully configured Code Owners and get tips and feedback. The DevOps Adoption table is available at [the group level](https://docs.gitlab.com/ee/user/group/devops_adoption/) and [the instance level](https://docs.gitlab.com/ee/administration/analytics/dev_ops_report.html#devops-adoption). stage: Manage self-managed: true gitlab-com: true available_in: [Ultimate] - documentation_link: https://docs.gitlab.com/ee/user/admin_area/analytics/dev_ops_report#devops-adoption + documentation_link: https://docs.gitlab.com/ee/administration/analytics/dev_ops_report#devops-adoption image_url: https://about.gitlab.com/images/14_0/codeownersadoption.png published_at: 2021-06-22 release: 14.0 diff --git a/data/whats_new/202107220001_14_1.yml b/data/whats_new/202107220001_14_1.yml index 32764b98803..328aed1629e 100644 --- a/data/whats_new/202107220001_14_1.yml +++ b/data/whats_new/202107220001_14_1.yml @@ -47,7 +47,7 @@ self-managed: true gitlab-com: true available_in: [Premium, Ultimate] - documentation_link: 'https://docs.gitlab.com/ee/ci/pipelines/settings.html#coverage-check-approval-rule' + documentation_link: 'https://docs.gitlab.com/ee/ci/testing/code_coverage.html#coverage-check-approval-rule' image_url: https://about.gitlab.com/images/14_1/coverage-mr-approval-rule.png published_at: 2021-07-22 release: 14.1 diff --git a/data/whats_new/202108190001_14_02.yml b/data/whats_new/202108190001_14_02.yml index bb9c8becd06..cac7ae77a2e 100644 --- a/data/whats_new/202108190001_14_02.yml +++ b/data/whats_new/202108190001_14_02.yml @@ -11,7 +11,7 @@ release: 14.2 - name: View historical CI pipeline minute usage description: | - Before GitLab 14.2, the CI pipeline minutes usage on the [Usage Quotas](https://docs.gitlab.com/ee/user/admin_area/settings/continuous_integration.html#shared-runners-pipeline-minutes-quota) page only showed the current month's usage. This data would reset every month and there was no way to view activity from the past months for analyzing historical usage. + Before GitLab 14.2, the CI pipeline minutes usage on the [Usage Quotas](https://docs.gitlab.com/ee/administration/settings/continuous_integration.html#shared-runners-pipeline-minutes-quota) page only showed the current month's usage. This data would reset every month and there was no way to view activity from the past months for analyzing historical usage. Now there are two charts that show historical CI pipeline minutes usage by month or by project, so you can make informed decisions about your pipeline usage. stage: Verify diff --git a/data/whats_new/202202210001_14_08.yml b/data/whats_new/202202210001_14_08.yml index 206fec03359..778529ffa86 100644 --- a/data/whats_new/202202210001_14_08.yml +++ b/data/whats_new/202202210001_14_08.yml @@ -55,7 +55,7 @@ - name: "User impersonation audit events for groups" description: | GitLab now provides audit events on the group audit events page for - [user impersonation](https://docs.gitlab.com/ee/user/admin_area/#user-impersonation) starting and stopping. This was previously + [user impersonation](https://docs.gitlab.com/ee/administration/#user-impersonation) starting and stopping. This was previously only available on a page unavailable to GitLab SaaS customers. We are excited to bring it to the group page which allows both self-managed and SaaS users to view these events! diff --git a/data/whats_new/2022082200001_15_03.yml b/data/whats_new/2022082200001_15_03.yml index b0a2bf3b6e2..a04db2381ad 100644 --- a/data/whats_new/2022082200001_15_03.yml +++ b/data/whats_new/2022082200001_15_03.yml @@ -53,7 +53,7 @@ self-managed: true gitlab-com: false available_in: [Premium, Ultimate] - documentation_link: https://docs.gitlab.com/ee/user/admin_area/settings/sign_up_restrictions.html#password-complexity-requirements + documentation_link: https://docs.gitlab.com/ee/administration/settings/sign_up_restrictions.html#password-complexity-requirements image_url: https://about.gitlab.com/images/15_3/manage-password-complexity-policy.png published_at: 2022-08-22 release: 15.3 diff --git a/data/whats_new/20230220001_15_08.yml b/data/whats_new/20230220001_15_08.yml index 30f1f1ea8d7..605b32025b8 100644 --- a/data/whats_new/20230220001_15_08.yml +++ b/data/whats_new/20230220001_15_08.yml @@ -24,7 +24,7 @@ self-managed: true gitlab-com: false available_in: [Premium, Ultimate] - documentation_link: https://docs.gitlab.com/ee/user/admin_area/settings/scim_setup.html + documentation_link: https://docs.gitlab.com/ee/administration/settings/scim_setup.html image_url: https://about.gitlab.com/images/15_8/manage-scim-token.png published_at: 2023-01-22 release: 15.8 diff --git a/data/whats_new/202306220001_16_1.yml b/data/whats_new/202306220001_16_1.yml new file mode 100644 index 00000000000..cd14713143a --- /dev/null +++ b/data/whats_new/202306220001_16_1.yml @@ -0,0 +1,98 @@ +- name: All new navigation experience + description: | # Do not modify this line, instead modify the lines below. + GitLab 16.1 features an all-new navigation experience! We've defaulted this experience to on for all users. To get started, go to your avatar in the top right of the UI and turn on the **New navigation** toggle. + + The new navigation was designed to solve three key areas of feedback: navigating GitLab can be overwhelming, it can be hard to pick up where you left off, and you can't customize the navigation. + + The new navigation includes a streamlined and improved left sidebar, where you can: + + * Pin 📌 frequently accessed items. + * Completely hide the sidebar and "peek" it back into view. + * Easily switch contexts, search, and view subsets of data with the new **Your Work** and **Explore** options. + * Scan more quickly because of fewer top-level menu items. + + We are proud of the new navigation and can't wait to see what you think. Review a [list of what's changed](https://gitlab.com/groups/gitlab-org/-/epics/9044#whats-different) and read our blog posts about the navigation [vision](https://about.gitlab.com/blog/2023/05/01/gitlab-product-navigation/) and [design](https://about.gitlab.com/blog/2023/05/15/overhauling-the-navigation-is-like-building-a-dream-home/). + + Please try the new navigation and let us know about your experience in [this issue](https://gitlab.com/gitlab-org/gitlab/-/issues/409005). We are already [addressing](https://gitlab.com/gitlab-org/gitlab/-/issues/409005#actions-we-are-taking-from-the-feedback) the feedback and will eventually remove the toggle. + stage: Manage + self-managed: true + gitlab-com: true + available_in: [Free, Premium, Ultimate] + documentation_link: https://docs.gitlab.com/ee/tutorials/left_sidebar/index.html + image_url: https://img.youtube.com/vi/rGTl9_HIpbY/hqdefault.jpg + published_at: 2023-06-22 + release: 16.1 + +- name: Visualize Kubernetes resources in GitLab + description: | # Do not modify this line, instead modify the lines below. + How do you check the status of the applications running in your clusters? The pipeline status and environment pages provide insights about the latest deployment runs. However, previous versions of GitLab lacked insights about the state of your deployments. In GitLab 16.1, you can see an overview of the primary resources in your Kubernetes deployments. + + This feature works with every connected Kubernetes cluster. It doesn't matter if you deploy your workloads with the CI/CD integration or GitOps. To further improve the feature for Flux users, support for showing the synchronization status of an environment is proposed in [issue 391581](https://gitlab.com/gitlab-org/gitlab/-/issues/391581). There are many use cases for which a non-human user might need to authenticate. Previously, depending on the desired scope, users could use personal, project, or group access tokens to meet this need. These tokens were not ideal, due to still being either tied to a human (for personal access tokens), or an unnecessarily privileged role (for group and project access tokens). + stage: Deploy + self-managed: true + gitlab-com: true + available_in: [Free, Premium, Ultimate] + documentation_link: https://docs.gitlab.com/ee/ci/environments/kubernetes_dashboard.html + image_url: https://about.gitlab.com/images/16_1/whats-new-k8s-visualization.png + published_at: 2023-06-22 + release: 16.1 + +- name: Authenticate with service accounts + description: | # Do not modify this line, instead modify the lines below. + There are many use cases for which a non-human user might need to authenticate. Previously, depending on the desired scope, users could use personal, project, or group access tokens to meet this need. These tokens were not ideal, due to still being either tied to a human (for personal access tokens), or an unnecessarily privileged role (for group and project access tokens). + + Service accounts are not tied to a human user, and are more granular in scope. Service account creation and management is API-only. Support for a UI option is proposed in [issue 9965](https://gitlab.com/groups/gitlab-org/-/epics/9965). + stage: Manage + self-managed: true + gitlab-com: true + available_in: [Premium, Ultimate] + documentation_link: https://docs.gitlab.com/ee/api/groups.html#service-accounts + image_url: https://img.youtube.com/vi/oZvjg0SCsqY/hqdefault.jpg + published_at: 2023-06-22 + release: 16.1 + +- name: GitLab Dedicated is now generally available + description: | # Do not modify this line, instead modify the lines below. + GitLab Dedicated is a fully managed, single-tenant SaaS deployment of our comprehensive DevSecOps platform designed to address the needs of customers with stringent compliance requirements. + + Customers in highly-regulated industries are unable to adopt multi-tenant SaaS offerings due to strict compliance requirements like data isolation. With GitLab Dedicated, organizations can access all of the benefits of the DevSecOps platform – including faster releases, better security, and more productive developers – while satisfying compliance requirements such as data residency, isolation, and private networking. + + [Learn more](https://about.gitlab.com/dedicated/) about GitLab Dedicated today. + stage: Platforms + self-managed: true + gitlab-com: false + available_in: [Ultimate] + documentation_link: https://docs.gitlab.com/ee/subscriptions/gitlab_dedicated/ + image_url: https://about.gitlab.com/images/16_1/gitlab-dedicated.png + published_at: 2023-06-22 + release: 16.1 + +- name: Manage job artifacts though the Artifacts page + description: | # Do not modify this line, instead modify the lines below. + Previously, if you wanted to view or manage job artifacts, you had to go to each job's detail page, or use the API. Now, you can view and manage job artifacts through the **Artifacts** page accessed at **Build > Artifacts**. + + Users with at least the Maintainer role can use this new interface to delete artifacts too. You can delete individual artifacts, or bulk delete up to 100 artifacts at a time through either manual selection or checking the **Select all** option at the top of the page. + + Please use the survey at the top of the Artifacts page to share any feedback you have about this new functionality. To view additional UI features under consideration, you can check out the [Build Artifacts page enhancements epic](https://gitlab.com/groups/gitlab-org/-/epics/8311). + stage: Verify + self-managed: true + gitlab-com: true + available_in: [Free, Premium, Ultimate] + documentation_link: https://docs.gitlab.com/ee/ci/jobs/job_artifacts.html#view-all-job-artifacts-in-a-project + image_url: https://about.gitlab.com/images/16_1/artifacts-bulk-delete.png + published_at: 2023-06-22 + release: 16.1 + +- name: Improved CI/CD variables list view + description: | # Do not modify this line, instead modify the lines below. + CI/CD variables are a key part of all pipelines and can be defined in multiple places, including in the project and group settings. To prepare for making bigger improvements that will help users intuitively navigate between variables at different hierarchy, we are starting out with improving the usability and layout of the variable list. + + In GitLab 16.1, you will see the first iteration of these improvements. We have merged the "Type" and "Options" columns into a new **Attributes** column, which better represents these related attributes. We appreciate your feedback on how we can continue to improve the CI/CD variable experience, you are welcome to comment in our [variables improvement epic](https://gitlab.com/groups/gitlab-org/-/epics/10506). + stage: Verify + self-managed: true + gitlab-com: true + available_in: [Free, Premium, Ultimate] + documentation_link: https://docs.gitlab.com/ee/ci/variables/#define-a-cicd-variable-in-the-ui + image_url: https://about.gitlab.com/images/16_1/layout_changes.png + published_at: 2023-06-22 + release: 16.1 -- cgit v1.2.3