From 72d6e76d2cfd81ca6a5d18536f02fd5116843cc4 Mon Sep 17 00:00:00 2001 From: Marcel Amirault <mamirault@gitlab.com> Date: Thu, 25 Jan 2024 19:37:09 +0900 Subject: [PATCH] Update version history format Update format for ci, integration, app_sec docs --- doc/ci/debugging.md | 2 +- doc/ci/environments/index.md | 2 +- doc/ci/jobs/ci_job_token.md | 6 +++--- doc/ci/pipelines/cicd_minutes.md | 4 ++-- doc/ci/pipelines/downstream_pipelines.md | 2 +- doc/ci/pipelines/index.md | 2 +- doc/ci/pipelines/merge_trains.md | 2 +- doc/ci/pipelines/schedules.md | 2 +- doc/ci/pipelines/settings.md | 2 +- doc/ci/runners/runners_scope.md | 4 ++-- doc/ci/testing/browser_performance_testing.md | 2 +- doc/ci/variables/index.md | 2 +- doc/ci/variables/where_variables_can_be_used.md | 2 +- doc/ci/yaml/artifacts_reports.md | 2 +- doc/ci/yaml/index.md | 6 +++--- doc/ci/yaml/inputs.md | 2 +- doc/integration/advanced_search/elasticsearch.md | 4 ++-- doc/integration/jira/configure.md | 2 +- doc/integration/kerberos.md | 2 +- doc/integration/omniauth.md | 2 +- doc/integration/saml.md | 2 +- doc/topics/autodevops/customize.md | 2 +- doc/topics/autodevops/stages.md | 2 +- doc/user/analytics/value_streams_dashboard.md | 2 +- doc/user/application_security/api_fuzzing/index.md | 2 +- doc/user/application_security/dast/on-demand_scan.md | 2 +- doc/user/application_security/dast_api/index.md | 2 +- .../policies/scan-execution-policies.md | 2 +- .../application_security/policies/scan-result-policies.md | 4 ++-- .../secret_detection/automatic_response.md | 2 +- doc/user/application_security/vulnerabilities/index.md | 2 +- doc/user/application_security/vulnerability_report/index.md | 6 +++--- 32 files changed, 42 insertions(+), 42 deletions(-) diff --git a/doc/ci/debugging.md b/doc/ci/debugging.md index 6e0f3162e2fdf..96dec6a4444cd 100644 --- a/doc/ci/debugging.md +++ b/doc/ci/debugging.md @@ -265,7 +265,7 @@ Ensure that included configuration files do not create a loop of references to e ### `Failed to pull image` messages -> **Allow access to this project with a CI_JOB_TOKEN** setting [renamed to **Limit access _to_ this project**](https://gitlab.com/gitlab-org/gitlab/-/issues/411406) in GitLab 16.3. +> - **Allow access to this project with a CI_JOB_TOKEN** setting [renamed to **Limit access _to_ this project**](https://gitlab.com/gitlab-org/gitlab/-/issues/411406) in GitLab 16.3. A runner might return a `Failed to pull image` message when trying to pull a container image in a CI/CD job. diff --git a/doc/ci/environments/index.md b/doc/ci/environments/index.md index 86525fc449d54..d0dacb5717f32 100644 --- a/doc/ci/environments/index.md +++ b/doc/ci/environments/index.md @@ -797,7 +797,7 @@ GitLab Auto Rollback is turned off by default. To turn it on: ### Web terminals (deprecated) -> [Deprecated](https://gitlab.com/groups/gitlab-org/configure/-/epics/8) in GitLab 14.5. +> - [Deprecated](https://gitlab.com/groups/gitlab-org/configure/-/epics/8) in GitLab 14.5. WARNING: This feature was [deprecated](https://gitlab.com/groups/gitlab-org/configure/-/epics/8) in GitLab 14.5. diff --git a/doc/ci/jobs/ci_job_token.md b/doc/ci/jobs/ci_job_token.md index 8a63bae45d53b..16efa30f32bb7 100644 --- a/doc/ci/jobs/ci_job_token.md +++ b/doc/ci/jobs/ci_job_token.md @@ -139,7 +139,7 @@ Triggering pipelines and fetching Terraform plans is not affected by feature vis ### Disable the job token scope allowlist -> **Allow access to this project with a CI_JOB_TOKEN** setting [renamed to **Limit access _to_ this project**](https://gitlab.com/gitlab-org/gitlab/-/issues/411406) in GitLab 16.3. +> - **Allow access to this project with a CI_JOB_TOKEN** setting [renamed to **Limit access _to_ this project**](https://gitlab.com/gitlab-org/gitlab/-/issues/411406) in GitLab 16.3. WARNING: It is a security risk to disable the allowlist. A malicious user could try to compromise @@ -165,7 +165,7 @@ You can also disable the allowlist [with the API](../../api/graphql/reference/in ### Add a project to the job token scope allowlist -> **Allow access to this project with a CI_JOB_TOKEN** setting [renamed to **Limit access _to_ this project**](https://gitlab.com/gitlab-org/gitlab/-/issues/411406) in GitLab 16.3. +> - **Allow access to this project with a CI_JOB_TOKEN** setting [renamed to **Limit access _to_ this project**](https://gitlab.com/gitlab-org/gitlab/-/issues/411406) in GitLab 16.3. You can add projects to the allowlist for a project. Projects added to the allowlist can make API calls from running pipelines by using the CI/CD job token. @@ -212,7 +212,7 @@ to make an API request to project `B`, then `B` must be added to the allowlist f ### Configure the job token scope -> **Limit CI_JOB_TOKEN access** setting [renamed to **Limit access _from_ this project**](https://gitlab.com/gitlab-org/gitlab/-/issues/411406) in GitLab 16.3. +> - **Limit CI_JOB_TOKEN access** setting [renamed to **Limit access _from_ this project**](https://gitlab.com/gitlab-org/gitlab/-/issues/411406) in GitLab 16.3. Prerequisites: diff --git a/doc/ci/pipelines/cicd_minutes.md b/doc/ci/pipelines/cicd_minutes.md index d0ee50db50f9a..70a0081c4badb 100644 --- a/doc/ci/pipelines/cicd_minutes.md +++ b/doc/ci/pipelines/cicd_minutes.md @@ -106,7 +106,7 @@ Prerequisites: ### View Usage Quota Reports for a group -> Displaying shared runners duration per project [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/355666) in GitLab 15.0. +> - Displaying shared runners duration per project [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/355666) in GitLab 15.0. Prerequisites: @@ -125,7 +125,7 @@ subgroups, sorted in descending order of compute usage. ### View Usage Quota reports for a personal namespace -> Displaying shared runners duration [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/345795) in GitLab 15.0. +> - Displaying shared runners duration [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/345795) in GitLab 15.0. Prerequisites: diff --git a/doc/ci/pipelines/downstream_pipelines.md b/doc/ci/pipelines/downstream_pipelines.md index e3e3d07186013..354ae003d504c 100644 --- a/doc/ci/pipelines/downstream_pipelines.md +++ b/doc/ci/pipelines/downstream_pipelines.md @@ -314,7 +314,7 @@ trigger_pipeline: ## View a downstream pipeline -> Hover behavior for pipeline cards [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/197140/) in GitLab 13.2. +> - Hover behavior for pipeline cards [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/197140/) in GitLab 13.2. In the [pipeline graph view](index.md#view-full-pipeline-graph), downstream pipelines display as a list of cards on the right of the graph. From this view, you can: diff --git a/doc/ci/pipelines/index.md b/doc/ci/pipelines/index.md index b025386676ca6..95cb113d19160 100644 --- a/doc/ci/pipelines/index.md +++ b/doc/ci/pipelines/index.md @@ -412,7 +412,7 @@ GitLab capitalizes the stages' names in the pipeline graphs. ### View full pipeline graph -> Visualization improvements [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/276949) in GitLab 13.11. +> - Visualization improvements [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/276949) in GitLab 13.11. The [pipeline details page](#view-pipelines) displays the full pipeline graph of all the jobs in the pipeline. diff --git a/doc/ci/pipelines/merge_trains.md b/doc/ci/pipelines/merge_trains.md index 543033a845a62..3e3a54dbf5431 100644 --- a/doc/ci/pipelines/merge_trains.md +++ b/doc/ci/pipelines/merge_trains.md @@ -94,7 +94,7 @@ are cancelled. ## Enable merge trains -> `disable_merge_trains` feature flag [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/282477) in GitLab 16.5. +> - `disable_merge_trains` feature flag [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/282477) in GitLab 16.5. Prerequisites: diff --git a/doc/ci/pipelines/schedules.md b/doc/ci/pipelines/schedules.md index df847d9993cbe..ec98983b305da 100644 --- a/doc/ci/pipelines/schedules.md +++ b/doc/ci/pipelines/schedules.md @@ -25,7 +25,7 @@ Otherwise, the pipeline is not created. No error message is displayed. ## Add a pipeline schedule -> Scheduled pipelines for tags [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/23292) in GitLab 14.9. +> - Scheduled pipelines for tags [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/23292) in GitLab 14.9. To add a pipeline schedule: diff --git a/doc/ci/pipelines/settings.md b/doc/ci/pipelines/settings.md index 70370bef7e842..ec0fc4dfc1730 100644 --- a/doc/ci/pipelines/settings.md +++ b/doc/ci/pipelines/settings.md @@ -131,7 +131,7 @@ To change the permissions to cancel pipelines or jobs: ## Specify a custom CI/CD configuration file -> Support for external `.gitlab-ci.yml` locations [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/14376) in GitLab 12.6. +> - Support for external `.gitlab-ci.yml` locations [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/14376) in GitLab 12.6. GitLab expects to find the CI/CD configuration file (`.gitlab-ci.yml`) in the project's root directory. However, you can specify an alternate file name path, including locations outside the project. diff --git a/doc/ci/runners/runners_scope.md b/doc/ci/runners/runners_scope.md index 9b6e56a700841..bb446d545c483 100644 --- a/doc/ci/runners/runners_scope.md +++ b/doc/ci/runners/runners_scope.md @@ -292,7 +292,7 @@ how to [register a runner](https://docs.gitlab.com/runner/register/#register-wit ### View group runners -> Ability for users with the Maintainer role to view group runners [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/384179) in GitLab 16.4. +> - Ability for users with the Maintainer role to view group runners [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/384179) in GitLab 16.4. Prerequisites: @@ -339,7 +339,7 @@ instance. If you pause a group runner that is used by multiple projects, the run ### Delete a group runner -> Multiple runner deletion [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/361721/) in GitLab 15.6. +> - Multiple runner deletion [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/361721/) in GitLab 15.6. Prerequisites: diff --git a/doc/ci/testing/browser_performance_testing.md b/doc/ci/testing/browser_performance_testing.md index 3476afe5dff12..a829e63d02aa8 100644 --- a/doc/ci/testing/browser_performance_testing.md +++ b/doc/ci/testing/browser_performance_testing.md @@ -60,7 +60,7 @@ job ran in the latest pipeline for the Merge request. ## Configuring Browser Performance Testing -> Support for the `SITESPEED_DOCKER_OPTIONS` variable [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/134024) in GitLab 16.6. +> - Support for the `SITESPEED_DOCKER_OPTIONS` variable [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/134024) in GitLab 16.6. This example shows how to run the [sitespeed.io container](https://hub.docker.com/r/sitespeedio/sitespeed.io/) on your code by using GitLab CI/CD and [sitespeed.io](https://www.sitespeed.io) diff --git a/doc/ci/variables/index.md b/doc/ci/variables/index.md index 86443d4270301..33cb34eedb165 100644 --- a/doc/ci/variables/index.md +++ b/doc/ci/variables/index.md @@ -646,7 +646,7 @@ To disable variable expansion for the variable: ## CI/CD variable precedence -> Scan Execution Policies variable precedence was [changed](https://gitlab.com/gitlab-org/gitlab/-/issues/424028) in GitLab 16.7 [with a flag](../../administration/feature_flags.md) named `security_policies_variables_precedence`. Enabled by default. [Feature flag removed in GitLab 16.8](https://gitlab.com/gitlab-org/gitlab/-/issues/435727). +> - Scan Execution Policies variable precedence was [changed](https://gitlab.com/gitlab-org/gitlab/-/issues/424028) in GitLab 16.7 [with a flag](../../administration/feature_flags.md) named `security_policies_variables_precedence`. Enabled by default. [Feature flag removed in GitLab 16.8](https://gitlab.com/gitlab-org/gitlab/-/issues/435727). You can use CI/CD variables with the same name in different places, but the values can overwrite each other. The type of variable and where they are defined determines diff --git a/doc/ci/variables/where_variables_can_be_used.md b/doc/ci/variables/where_variables_can_be_used.md index f61646636d376..6ab22b7149125 100644 --- a/doc/ci/variables/where_variables_can_be_used.md +++ b/doc/ci/variables/where_variables_can_be_used.md @@ -25,7 +25,7 @@ There are two places defined variables can be used. On the: ### `.gitlab-ci.yml` file -> Support for `CI_ENVIRONMENT_*` variables except `CI_ENVIRONMENT_SLUG` [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/128694) in GitLab 16.4. +> - Support for `CI_ENVIRONMENT_*` variables except `CI_ENVIRONMENT_SLUG` [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/128694) in GitLab 16.4. | Definition | Can be expanded? | Expansion place | Description | |:----------------------------------------------------------------------|:-----------------|:-----------------------|:------------| diff --git a/doc/ci/yaml/artifacts_reports.md b/doc/ci/yaml/artifacts_reports.md index 5e5f13bda1352..32901546e4125 100644 --- a/doc/ci/yaml/artifacts_reports.md +++ b/doc/ci/yaml/artifacts_reports.md @@ -151,7 +151,7 @@ GitLab can display the results of coverage report in the merge request ## `artifacts:reports:codequality` -> Support for multiple reports in diff annotations and full pipeline report [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/9014) in 15.7. +> - Support for multiple reports in diff annotations and full pipeline report [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/9014) in 15.7. The `codequality` report collects [code quality issues](../testing/code_quality.md). The collected code quality report uploads to GitLab as an artifact. diff --git a/doc/ci/yaml/index.md b/doc/ci/yaml/index.md index 31ca5c13e1276..b95397bbc735c 100644 --- a/doc/ci/yaml/index.md +++ b/doc/ci/yaml/index.md @@ -86,7 +86,7 @@ or import additional pipeline configuration. ### `default` -> Support for `id_tokens` [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/419750) in GitLab 16.4. +> - Support for `id_tokens` [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/419750) in GitLab 16.4. You can set global defaults for some keywords. Each default keyword is copied to every job that doesn't already have it defined. If the job already has a keyword defined, that default @@ -252,7 +252,7 @@ include: '.gitlab-ci-production.yml' #### `include:project` -> Including multiple files from the same project [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/26793) in GitLab 13.6. [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/271560) in GitLab 13.8. +> - Including multiple files from the same project [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/26793) in GitLab 13.6. [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/271560) in GitLab 13.8. To include files from another private project on the same GitLab instance, use `include:project` and `include:file`. @@ -2196,7 +2196,7 @@ stop_review_app: #### `environment:auto_stop_in` -> CI/CD variable support [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/365140) in GitLab 15.4. +> - CI/CD variable support [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/365140) in GitLab 15.4. The `auto_stop_in` keyword specifies the lifetime of the environment. When an environment expires, GitLab automatically stops it. diff --git a/doc/ci/yaml/inputs.md b/doc/ci/yaml/inputs.md index f24d9dde0d8e9..3e8e071d31e80 100644 --- a/doc/ci/yaml/inputs.md +++ b/doc/ci/yaml/inputs.md @@ -111,7 +111,7 @@ In this example: ## Set input values when using `include` -> `include:with` [renamed to `include:inputs`](https://gitlab.com/gitlab-org/gitlab/-/issues/406780) in GitLab 16.0. +> - `include:with` [renamed to `include:inputs`](https://gitlab.com/gitlab-org/gitlab/-/issues/406780) in GitLab 16.0. Use [`include:inputs`](index.md#includeinputs) to set the values for the parameters when the included configuration is added to the pipeline. diff --git a/doc/integration/advanced_search/elasticsearch.md b/doc/integration/advanced_search/elasticsearch.md index 4d894e8d307e3..1bfec3330bea3 100644 --- a/doc/integration/advanced_search/elasticsearch.md +++ b/doc/integration/advanced_search/elasticsearch.md @@ -17,7 +17,7 @@ advanced search provides faster search response times and [improved search featu ### Elasticsearch version requirements -> Support for Elasticsearch 6.8 [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/350275) in GitLab 15.0. +> - Support for Elasticsearch 6.8 [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/350275) in GitLab 15.0. Advanced search works with the following versions of Elasticsearch. @@ -69,7 +69,7 @@ The search index updates after you: ## Upgrade to a new Elasticsearch major version -> Support for Elasticsearch 6.8 [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/350275) in GitLab 15.0. +> - Support for Elasticsearch 6.8 [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/350275) in GitLab 15.0. You don't have to change the GitLab configuration when you upgrade Elasticsearch. diff --git a/doc/integration/jira/configure.md b/doc/integration/jira/configure.md index 2dac09d3afb1e..ed53787cbb668 100644 --- a/doc/integration/jira/configure.md +++ b/doc/integration/jira/configure.md @@ -14,7 +14,7 @@ The Jira issue integration connects one or more GitLab projects to a Jira instan ## Configure the integration -> Authentication with Jira personal access tokens [introduced](https://gitlab.com/groups/gitlab-org/-/epics/8222) in GitLab 16.0. +> - Authentication with Jira personal access tokens [introduced](https://gitlab.com/groups/gitlab-org/-/epics/8222) in GitLab 16.0. Prerequisites: diff --git a/doc/integration/kerberos.md b/doc/integration/kerberos.md index e593785a9a3b4..751ac96a6b2bb 100644 --- a/doc/integration/kerberos.md +++ b/doc/integration/kerberos.md @@ -105,7 +105,7 @@ set up GitLab to create a new account when a Kerberos user tries to sign in. ### Link a Kerberos account to an existing GitLab account -> Kerberos SPNEGO [renamed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/96335) to Kerberos in GitLab 15.4. +> - Kerberos SPNEGO [renamed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/96335) to Kerberos in GitLab 15.4. If you're an administrator, you can link a Kerberos account to an existing GitLab account. To do so: diff --git a/doc/integration/omniauth.md b/doc/integration/omniauth.md index afda788b8ea76..26797119f3215 100644 --- a/doc/integration/omniauth.md +++ b/doc/integration/omniauth.md @@ -430,7 +430,7 @@ omniauth: ## Bypass two-factor authentication -> Introduced in GitLab 12.3. +> - Introduced in GitLab 12.3. With certain OmniAuth providers, users can sign in without using two-factor authentication (2FA). diff --git a/doc/integration/saml.md b/doc/integration/saml.md index 598458218f014..534ecc359830a 100644 --- a/doc/integration/saml.md +++ b/doc/integration/saml.md @@ -723,7 +723,7 @@ your provider's support. ### Configure assertions -> Microsoft Azure/Entra ID attribute support [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/420766) in GitLab 16.7. +> - Microsoft Azure/Entra ID attribute support [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/420766) in GitLab 16.7. NOTE: The attributes are case-sensitive. diff --git a/doc/topics/autodevops/customize.md b/doc/topics/autodevops/customize.md index 66686e063af8e..c57093f0cd726 100644 --- a/doc/topics/autodevops/customize.md +++ b/doc/topics/autodevops/customize.md @@ -94,7 +94,7 @@ To use only a single custom buildpack, you should provide the project CI/CD vari ## Custom Dockerfiles -> `DOCKERFILE_PATH` [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/35662) in GitLab 13.2. +> - `DOCKERFILE_PATH` [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/35662) in GitLab 13.2. If you have a Dockerfile in the root of your project repository, Auto DevOps builds a Docker image based on the Dockerfile. This can be diff --git a/doc/topics/autodevops/stages.md b/doc/topics/autodevops/stages.md index 056ea2fe8a1a7..b395c36644695 100644 --- a/doc/topics/autodevops/stages.md +++ b/doc/topics/autodevops/stages.md @@ -97,7 +97,7 @@ Read more about defining volumes in the [`pack build` documentation](https://bui ### Auto Build using Herokuish (deprecated) -> [Replaced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/63351) with Cloud Native Buildpacks in GitLab 14.0. +> - [Replaced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/63351) with Cloud Native Buildpacks in GitLab 14.0. WARNING: Support for Herokuish was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/108234) in GitLab 15.8, diff --git a/doc/user/analytics/value_streams_dashboard.md b/doc/user/analytics/value_streams_dashboard.md index 2f7a19193d79c..611c61b453385 100644 --- a/doc/user/analytics/value_streams_dashboard.md +++ b/doc/user/analytics/value_streams_dashboard.md @@ -39,7 +39,7 @@ The Value Streams Dashboard panels has a default configuration, but you can also ### DevSecOps metrics comparison panel -> Contributor count metric [added](https://gitlab.com/gitlab-org/gitlab/-/issues/433353) in GitLab 16.9. +> - Contributor count metric [added](https://gitlab.com/gitlab-org/gitlab/-/issues/433353) in GitLab 16.9. The DevSecOps metrics comparison displays DORA4, vulnerability, and flow metrics for a group or project in the month-to-date, last month, the month before, and the past 180 days. diff --git a/doc/user/application_security/api_fuzzing/index.md b/doc/user/application_security/api_fuzzing/index.md index d45e9149793e3..442a3dbe20851 100644 --- a/doc/user/application_security/api_fuzzing/index.md +++ b/doc/user/application_security/api_fuzzing/index.md @@ -274,7 +274,7 @@ For details of API fuzzing configuration options, see [Available CI/CD variables ### GraphQL Schema -> Support for GraphQL Schema was [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/352780) in GitLab 15.4. +> - Support for GraphQL Schema was [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/352780) in GitLab 15.4. GraphQL is a query language for your API and an alternative to REST APIs. API Fuzzing supports testing GraphQL endpoints multiple ways: diff --git a/doc/user/application_security/dast/on-demand_scan.md b/doc/user/application_security/dast/on-demand_scan.md index 95b02e65efec5..ac192cc03159e 100644 --- a/doc/user/application_security/dast/on-demand_scan.md +++ b/doc/user/application_security/dast/on-demand_scan.md @@ -168,7 +168,7 @@ This data can only be read and decrypted with a valid secrets file. ### Site profile validation -> Meta tag validation [introduced](https://gitlab.com/groups/gitlab-org/-/epics/6460) in GitLab 14.2. +> - Meta tag validation [introduced](https://gitlab.com/groups/gitlab-org/-/epics/6460) in GitLab 14.2. Site profile validation reduces the risk of running an active scan against the wrong website. A site must be validated before an active scan can run against it. Each of the site validation methods are diff --git a/doc/user/application_security/dast_api/index.md b/doc/user/application_security/dast_api/index.md index 43bf96e655d3d..a42427cc03a5f 100644 --- a/doc/user/application_security/dast_api/index.md +++ b/doc/user/application_security/dast_api/index.md @@ -209,7 +209,7 @@ This example is a minimal configuration for DAST API. From here you can: ### GraphQL Schema -> Support for GraphQL Schema was [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/352780) in GitLab 15.4. +> - Support for GraphQL Schema was [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/352780) in GitLab 15.4. GraphQL is a query language for your API and an alternative to REST APIs. DAST API supports testing GraphQL endpoints multiple ways: diff --git a/doc/user/application_security/policies/scan-execution-policies.md b/doc/user/application_security/policies/scan-execution-policies.md index 7b4f880a18492..559817ee92b7b 100644 --- a/doc/user/application_security/policies/scan-execution-policies.md +++ b/doc/user/application_security/policies/scan-execution-policies.md @@ -204,7 +204,7 @@ The keys for a schedule rule are: ## `scan` action type -> Scan Execution Policies variable precedence was [changed](https://gitlab.com/gitlab-org/gitlab/-/issues/424028) in GitLab 16.7 [with a flag](../../../administration/feature_flags.md) named `security_policies_variables_precedence`. Enabled by default. [Feature flag removed in GitLab 16.8](https://gitlab.com/gitlab-org/gitlab/-/issues/435727). +> - Scan Execution Policies variable precedence was [changed](https://gitlab.com/gitlab-org/gitlab/-/issues/424028) in GitLab 16.7 [with a flag](../../../administration/feature_flags.md) named `security_policies_variables_precedence`. Enabled by default. [Feature flag removed in GitLab 16.8](https://gitlab.com/gitlab-org/gitlab/-/issues/435727). This action executes the selected `scan` with additional parameters when conditions for at least one rule in the defined policy are met. diff --git a/doc/user/application_security/policies/scan-result-policies.md b/doc/user/application_security/policies/scan-result-policies.md index 6ab968bdb5466..ab658119d1c1b 100644 --- a/doc/user/application_security/policies/scan-result-policies.md +++ b/doc/user/application_security/policies/scan-result-policies.md @@ -94,7 +94,7 @@ the following sections and tables provide an alternative. ## Scan result policy schema -> The `approval_settings` fields were [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/418752) in GitLab 16.4 [with flags](../../../administration/feature_flags.md) named `scan_result_policies_block_unprotecting_branches`, `scan_result_any_merge_request`, or `scan_result_policies_block_force_push`. See the `approval_settings` section below for more information. +> - The `approval_settings` fields were [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/418752) in GitLab 16.4 [with flags](../../../administration/feature_flags.md) named `scan_result_policies_block_unprotecting_branches`, `scan_result_any_merge_request`, or `scan_result_policies_block_force_push`. See the `approval_settings` section below for more information. | Field | Type | Required | Possible values | Description | |---------------------|--------------------|----------|-----------------|----------------------------------------------------------| @@ -299,7 +299,7 @@ actions: ## Understanding scan result policy approvals -> The branch comparison logic for `scan_finding` was [changed](https://gitlab.com/gitlab-org/gitlab/-/issues/428518) in GitLab 16.8 [with a flag](../../../administration/feature_flags.md) named `scan_result_policy_merge_base_pipeline`. Disabled by default. +> - The branch comparison logic for `scan_finding` was [changed](https://gitlab.com/gitlab-org/gitlab/-/issues/428518) in GitLab 16.8 [with a flag](../../../administration/feature_flags.md) named `scan_result_policy_merge_base_pipeline`. Disabled by default. FLAG: On self-managed GitLab, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../../../administration/feature_flags.md) named `scan_result_policy_merge_base_pipeline`. diff --git a/doc/user/application_security/secret_detection/automatic_response.md b/doc/user/application_security/secret_detection/automatic_response.md index aa3b81583cf19..4789a6f159e8f 100644 --- a/doc/user/application_security/secret_detection/automatic_response.md +++ b/doc/user/application_security/secret_detection/automatic_response.md @@ -36,7 +36,7 @@ GitLab supports automatic response for the following types of secrets: ## Feature availability -> [Enabled for non-default branches](https://gitlab.com/gitlab-org/gitlab/-/issues/299212) in GitLab 15.11. +> - [Enabled for non-default branches](https://gitlab.com/gitlab-org/gitlab/-/issues/299212) in GitLab 15.11. Credentials are only post-processed when Secret Detection finds them: diff --git a/doc/user/application_security/vulnerabilities/index.md b/doc/user/application_security/vulnerabilities/index.md index 6e21294d301f3..ae6cca7150bab 100644 --- a/doc/user/application_security/vulnerabilities/index.md +++ b/doc/user/application_security/vulnerabilities/index.md @@ -161,7 +161,7 @@ When dismissing a vulnerability, one of the following reasons must be chosen to ## Change the status of a vulnerability -> In GitLab 16.4 the ability for `Developers` to change the status of a vulnerability (`admin_vulnerability`) was [deprecated](../../../update/deprecations.md#deprecate-change-vulnerability-status-from-the-developer-role). The `admin_vulnerability` permission will be removed, by default, from all `Developer` roles in GitLab 17.0. +> - In GitLab 16.4 the ability for `Developers` to change the status of a vulnerability (`admin_vulnerability`) was [deprecated](../../../update/deprecations.md#deprecate-change-vulnerability-status-from-the-developer-role). The `admin_vulnerability` permission will be removed, by default, from all `Developer` roles in GitLab 17.0. Prerequisites: diff --git a/doc/user/application_security/vulnerability_report/index.md b/doc/user/application_security/vulnerability_report/index.md index 2dec5cd6df5f7..8e4f8ae7fe545 100644 --- a/doc/user/application_security/vulnerability_report/index.md +++ b/doc/user/application_security/vulnerability_report/index.md @@ -97,7 +97,7 @@ After each filter is selected: ### Tool filter -> Project-level tool filter [introduced](https://gitlab.com/groups/gitlab-org/-/epics/11237) in GitLab 16.6. +> - Project-level tool filter [introduced](https://gitlab.com/groups/gitlab-org/-/epics/11237) in GitLab 16.6. You can filter vulnerabilities by the tool that detected them. By default, the vulnerability report lists vulnerabilities from all tools. When you select a heading, you select all the tools @@ -176,7 +176,7 @@ To view the relevant file, select the filename in the vulnerability's details. ## Change status of vulnerabilities -> Providing a comment and dismissal reason [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/408366) in GitLab 16.0. +> - Providing a comment and dismissal reason [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/408366) in GitLab 16.0. As you triage vulnerabilities you can change their status, including dismissing vulnerabilities. @@ -209,7 +209,7 @@ To sort vulnerabilities by the date each vulnerability was detected, select the ## Export vulnerability details -> Added "Dismissal Reason" as a column in the CSV export [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/434076) in GitLab 16.8. +> - Added "Dismissal Reason" as a column in the CSV export [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/434076) in GitLab 16.8. You can export details of the vulnerabilities listed in the Vulnerability Report. The export format is CSV (comma separated values). All vulnerabilities are included because filters do not -- GitLab