diff options
Diffstat (limited to 'data/removals/16_0')
9 files changed, 37 insertions, 7 deletions
diff --git a/data/removals/16_0/16-0-Security-report-schemas-version-14.yml b/data/removals/16_0/16-0-Security-report-schemas-version-14.yml new file mode 100644 index 00000000000..14d5dd7acd2 --- /dev/null +++ b/data/removals/16_0/16-0-Security-report-schemas-version-14.yml @@ -0,0 +1,11 @@ +- title: "Security report schemas version 14.x.x" + announcement_milestone: "15.3" + removal_milestone: "16.0" + breaking_change: true + reporter: abellucci + stage: Govern + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/366477 + body: | + Version 14.x.x [security report schemas](https://gitlab.com/gitlab-org/security-products/security-report-schemas) have been removed. + Security reports that use schema version 14.x.x will cause an error in the pipeline's **Security** tab. For more information, refer to [security report validation](https://docs.gitlab.com/ee/user/application_security/#security-report-validation). + tiers: [Ultimate] diff --git a/data/removals/16_0/16-0-dast-api-variable-removal.yml b/data/removals/16_0/16-0-dast-api-variable-removal.yml index 15dd4c6d781..1b67eeb0fa7 100644 --- a/data/removals/16_0/16-0-dast-api-variable-removal.yml +++ b/data/removals/16_0/16-0-dast-api-variable-removal.yml @@ -4,7 +4,7 @@ breaking_change: true # (required) Change to false if this is not a breaking change. reporter: derekferguson # (required) GitLab username of the person reporting the removal stage: Secure # (required) String value of the stage that the feature was created in. e.g., Growth - issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/383467 # (required) Link to the deprecation issue in GitLab + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/383467 # (required) Link to the deprecation issue in GitLab body: | # (required) Do not modify this line, instead modify the lines below. The variables `DAST_API_HOST_OVERRIDE` and `DAST_API_SPECIFICATION` have been removed from use for DAST API scans. diff --git a/data/removals/16_0/16-0-grafana-chart.yml b/data/removals/16_0/16-0-grafana-chart.yml index 012d5043a98..3251f477bb0 100644 --- a/data/removals/16_0/16-0-grafana-chart.yml +++ b/data/removals/16_0/16-0-grafana-chart.yml @@ -15,5 +15,5 @@ In your new Grafana instance, you can [configure the GitLab provided Prometheus as a data source](https://docs.gitlab.com/ee/administration/monitoring/performance/grafana_configuration.html#integration-with-gitlab-ui) and [connect Grafana to the GitLab UI](https://docs.gitlab.com/ee/administration/monitoring/performance/grafana_configuration.html#integration-with-gitlab-ui). - 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] + 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/administration/monitoring/performance/grafana_configuration.html diff --git a/data/removals/16_0/16-0-limit-ci-job-token.yml b/data/removals/16_0/16-0-limit-ci-job-token.yml index 9f262f9c772..1409677233c 100644 --- a/data/removals/16_0/16-0-limit-ci-job-token.yml +++ b/data/removals/16_0/16-0-limit-ci-job-token.yml @@ -2,7 +2,7 @@ announcement_milestone: "15.9" # (required) The milestone when this feature was first announced as deprecated. removal_milestone: "16.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: jreporter # (required) GitLab username of the person reporting the deprecation + reporter: jreporter # (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/395708 # (required) Link to the deprecation issue in GitLab body: | # (required) Do not modify this line, instead modify the lines below. diff --git a/data/removals/16_0/16-0-non-expiring-access-tokens.yml b/data/removals/16_0/16-0-non-expiring-access-tokens.yml new file mode 100644 index 00000000000..5ef7df3a131 --- /dev/null +++ b/data/removals/16_0/16-0-non-expiring-access-tokens.yml @@ -0,0 +1,19 @@ +- title: "Non-expiring access tokens no longer supported" + announcement_milestone: "15.4" # (required) The milestone when this feature was deprecated. + removal_milestone: "16.0" # (required) The milestone when this feature is being removed. + breaking_change: true # (required) Change to false if this is not a breaking change. + reporter: jessieay # (required) GitLab username of the person reporting the removal + 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/369123 + body: | # (required) Do not modify this line, instead modify the lines below. + Currently, you can create access tokens that have no expiration date. These access tokens are valid indefinitely, which presents a security risk if the access token is + divulged. Because expiring access tokens are better, from GitLab 15.4 we [populate a default expiration date](https://gitlab.com/gitlab-org/gitlab/-/issues/348660). + + In GitLab 16.0, any personal, project, or group access token that does not have an expiration date will automatically have an expiration date set at 365 days later than the current date. +# +# 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/removals/16_0/16-0-postgresql-12.yml b/data/removals/16_0/16-0-postgresql-12.yml index 9aa8102154b..9c860af7dbc 100644 --- a/data/removals/16_0/16-0-postgresql-12.yml +++ b/data/removals/16_0/16-0-postgresql-12.yml @@ -13,5 +13,5 @@ to PostgreSQL 13. - Using an externally-provided PostgreSQL 12, you must upgrade to PostgreSQL 13 or later to meet the [minimum version requirements](https://docs.gitlab.com/ee/install/requirements.html#postgresql-requirements). - 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] + 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/administration/package_information/postgresql_versions.html diff --git a/data/removals/16_0/16.0-config-fields-runner-helm-chart.yml b/data/removals/16_0/16.0-config-fields-runner-helm-chart.yml index 47067eda63d..63c50842a0d 100644 --- a/data/removals/16_0/16.0-config-fields-runner-helm-chart.yml +++ b/data/removals/16_0/16.0-config-fields-runner-helm-chart.yml @@ -4,7 +4,7 @@ breaking_change: false # (required) Change to false if this is not a breaking change. reporter: DarrenEastman # (required) GitLab username of the person reporting the removal 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/379064 # (required) Link to the deprecation issue in GitLab + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/379064 # (required) Link to the deprecation issue in GitLab body: | # (required) Do not modify this line, instead modify the lines below. In GitLab 13.6 and later, users can [specify any runner configuration in the GitLab Runner Helm chart](https://docs.gitlab.com/runner/install/kubernetes.html). When this features was released, we deprecated the fields in the GitLab Helm Chart configuration specific to the runner. As of v1.0 of the GitLab Runner Helm chart (GitLab 16.0), the following fields have been removed and are no longer supported: diff --git a/data/removals/16_0/16.0-eol-windows-server-2004-and-20H2.yml b/data/removals/16_0/16.0-eol-windows-server-2004-and-20H2.yml index 9b47beed41b..267304f6a13 100644 --- a/data/removals/16_0/16.0-eol-windows-server-2004-and-20H2.yml +++ b/data/removals/16_0/16.0-eol-windows-server-2004-and-20H2.yml @@ -4,6 +4,6 @@ breaking_change: false # (required) Change to false if this is not a breaking change. reporter: DarrenEastman # (required) GitLab username of the person reporting the removal 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-runner/-/issues/31001 # (required) Link to the deprecation issue in GitLab + issue_url: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/31001 # (required) Link to the deprecation issue in GitLab body: | # (required) Do not modify this line, instead modify the lines below. As of GitLab 16.0, GitLab Runner images based on Windows Server 2004 and 20H2 will not be provided as these operating systems are end-of-life. diff --git a/data/removals/16_0/16.0-runner-api-does-not-return-paused-active.yml b/data/removals/16_0/16.0-runner-api-does-not-return-paused-active.yml index 17ab36d36d2..7da64404eb3 100644 --- a/data/removals/16_0/16.0-runner-api-does-not-return-paused-active.yml +++ b/data/removals/16_0/16.0-runner-api-does-not-return-paused-active.yml @@ -4,7 +4,7 @@ breaking_change: true # (required) Change to false if this is not a breaking change. reporter: DarrenEastman # (required) GitLab username of the person reporting the removal 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/344648 # (required) Link to the deprecation issue in GitLab + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/344648 # (required) Link to the deprecation issue in GitLab body: | # (required) Do not modify this line, instead modify the lines below. In GitLab 16.0 and later, the GraphQL query for runners will no longer return the statuses `PAUSED` and `ACTIVE`. |