root
/
gitlab-ce
mirror of https://gitlab.com/free-releases/gitlab-ce.git
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity

Add latest changes from gitlab-org/gitlab@master

This commit is contained in:
GitLab Bot 2025-02-10 09:11:53 +00:00
parent 6e4dc73031
commit 8e037a9a2d
267 changed files with 1265 additions and 1278 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
GITLAB_KAS_VERSION
View File

@ -1 +1 @@
3fa1c11d8b075732507775876c9de1c291cdc761
b2f80dfca03da7372da03c61b212c0923e415187

2
app/assets/javascripts/clusters_list/components/clusters_empty_state.vue
View File

@ -14,7 +14,7 @@ export default {
PromoPageLink,
},
inject: ['emptyStateHelpText', 'clustersEmptyStateImage'],
clustersHelpUrl: helpPagePath('user/infrastructure/clusters/index', {
clustersHelpUrl: helpPagePath('user/infrastructure/clusters/_index', {
anchor: 'certificate-based-kubernetes-integration-deprecated',
}),
blogPostPath: 'blog/2021/11/15/deprecating-the-cert-based-kubernetes-integration/',

2
app/assets/javascripts/organizations/new/components/app.vue
View File

@ -28,7 +28,7 @@ export default {
},
computed: {
organizationsHelpPagePath() {
return helpPagePath('user/organization/index');
return helpPagePath('user/organization/_index');
},
},
methods: {

2
app/assets/javascripts/organizations/settings/general/components/visibility_level.vue
View File

@ -56,7 +56,7 @@ export default {
<template #group(visibilityLevel)-label-description>
{{ $options.fields.visibilityLevel.labelDescription }}
<help-page-link
href="user/organization/index"
href="user/organization/_index"
anchor="view-an-organizations-visibility-level"
>{{ $options.i18n.learnMore }}</help-page-link
>.

4
app/assets/javascripts/organizations/shared/components/new_edit_form.vue
View File

@ -44,7 +44,7 @@ export default {
charactersOverLimit: (char) => n__('%d character over limit', '%d characters over limit', char),
},
formId: 'organization-form',
markdownDocsPath: helpPagePath('user/organization/index', {
markdownDocsPath: helpPagePath('user/organization/_index', {
anchor: 'supported-markdown-for-organization-description',
}),
restrictedToolBarItems: RESTRICTED_TOOLBAR_ITEMS_BASIC_EDITING_ONLY,
@ -263,7 +263,7 @@ export default {
<template #group(visibilityLevel)-label-description>
{{ fields.visibilityLevel.labelDescription.text }}
<help-page-link
href="user/organization/index"
href="user/organization/_index"
anchor="view-an-organizations-visibility-level"
>{{ fields.visibilityLevel.labelDescription.linkText }}</help-page-link
>.

2
app/assets/javascripts/packages_and_registries/container_registry/explorer/components/list_page/group_empty_state.vue
View File

@ -10,7 +10,7 @@ export default {
GlLink,
},
inject: ['config'],
containerRegistryHelpUrl: helpPagePath('user/packages/container_registry/index'),
containerRegistryHelpUrl: helpPagePath('user/packages/container_registry/_index'),
};
</script>
<template>

2
app/assets/javascripts/packages_and_registries/container_registry/explorer/components/list_page/project_empty_state.vue
View File

@ -36,7 +36,7 @@ export default {
'ContainerRegistry|You can add an image to this registry with the following commands:',
),
},
containerRegistryHelpUrl: helpPagePath('user/packages/container_registry/index'),
containerRegistryHelpUrl: helpPagePath('user/packages/container_registry/_index'),
twoFactorAuthHelpUrl: helpPagePath('user/profile/account/two_factor_authentication'),
personalAccessTokensHelpUrl: helpPagePath('user/profile/personal_access_tokens'),
};

2
app/assets/javascripts/packages_and_registries/container_registry/explorer/pages/list.vue
View File

@ -236,7 +236,7 @@ export default {
}
},
},
containerRegistryHelpUrl: helpPagePath('user/packages/container_registry/index'),
containerRegistryHelpUrl: helpPagePath('user/packages/container_registry/_index'),
dockerConnectionErrorHelpUrl: helpPagePath(
'user/packages/container_registry/troubleshoot_container_registry',
{

2
app/assets/javascripts/packages_and_registries/dependency_proxy/constants.js
View File

@ -4,7 +4,7 @@ export const GRAPHQL_PAGE_SIZE = 20;
export const MANIFEST_PENDING_DESTRUCTION_STATUS = 'PENDING_DESTRUCTION';
export const DEPENDENCY_PROXY_HELP_PAGE_PATH = helpPagePath(
'user/packages/dependency_proxy/index',
'user/packages/dependency_proxy/_index',
{
anchor: 'store-a-docker-image-in-dependency-proxy-cache',
},

2
app/assets/javascripts/packages_and_registries/settings/group/constants.js
View File

@ -83,7 +83,7 @@ export const MAVEN_FORWARDING_FIELDS = {
// Parameters
export const DEPENDENCY_PROXY_DOCS_PATH = helpPagePath('user/packages/dependency_proxy/index');
export const DEPENDENCY_PROXY_DOCS_PATH = helpPagePath('user/packages/dependency_proxy/_index');
export const REQUEST_FORWARDING_HELP_PAGE_PATH = helpPagePath(
'user/packages/package_registry/supported_functionality',
{ anchor: 'deleting-packages' },

2
app/assets/javascripts/packages_and_registries/settings/project/components/container_registry_section.vue
View File

@ -33,7 +33,7 @@ export default {
);
},
},
containerRegistryHelpPath: helpPagePath('user/packages/container_registry/index.md'),
containerRegistryHelpPath: helpPagePath('user/packages/container_registry/_index.md'),
};
</script>

2
app/assets/javascripts/super_sidebar/components/organization_switcher.vue
View File

@ -26,7 +26,7 @@ export default {
),
learnMore: __('Learn more'),
},
switchingOrganizationsDocsPath: helpPagePath('user/organization/index.md', {
switchingOrganizationsDocsPath: helpPagePath('user/organization/_index.md', {
anchor: 'switch-organizations',
}),
components: { GlDisclosureDropdown, GlAvatar, GlIcon, GlLoadingIcon, GlLink },

2
app/assets/javascripts/usage_quotas/storage/namespace/components/container_registry_usage.vue
View File

@ -49,7 +49,7 @@ export default {
<template #left-secondary-text>
<span>
{{ $options.i18n.containerRegistryDescription }}
<help-page-link href="user/packages/container_registry/index">
<help-page-link href="user/packages/container_registry/_index">
{{ __('More information') }}
</help-page-link>
</span>

2
app/assets/javascripts/usage_quotas/storage/namespace/components/dependency_proxy_usage.vue
View File

@ -53,7 +53,7 @@ export default {
<template #left-secondary-text>
<div data-testid="dependency-proxy-description">
{{ description }}
<help-page-link href="user/packages/dependency_proxy/index">
<help-page-link href="user/packages/dependency_proxy/_index">
{{ __('More information') }}
</help-page-link>
</div>

4
app/helpers/projects_helper.rb
View File

@ -460,7 +460,7 @@ module ProjectsHelper
allowedVisibilityOptions: project_allowed_visibility_levels(project),
visibilityHelpPath: help_page_path('user/public_access.md'),
registryAvailable: Gitlab.config.registry.enabled,
registryHelpPath: help_page_path('user/packages/container_registry/index.md'),
registryHelpPath: help_page_path('user/packages/container_registry/_index.md'),
lfsAvailable: Gitlab.config.lfs.enabled,
lfsHelpPath: help_page_path('topics/git/lfs/_index.md'),
lfsObjectsExist: project.lfs_objects.exists?,
@ -475,7 +475,7 @@ module ProjectsHelper
environmentsHelpPath: help_page_path('ci/environments/_index.md'),
featureFlagsHelpPath: help_page_path('operations/feature_flags.md'),
releasesHelpPath: help_page_path('user/project/releases/index.md'),
infrastructureHelpPath: help_page_path('user/infrastructure/index.md')
infrastructureHelpPath: help_page_path('user/infrastructure/_index.md')
}
end

2
app/presenters/instance_clusterable_presenter.rb
View File

@ -60,7 +60,7 @@ class InstanceClusterablePresenter < ClusterablePresenter
override :learn_more_link
def learn_more_link
ApplicationController.helpers.link_to(s_('ClusterIntegration|Learn more about instance Kubernetes clusters'), help_page_path('user/instance/clusters/index.md'), target: '_blank', rel: 'noopener noreferrer')
ApplicationController.helpers.link_to(s_('ClusterIntegration|Learn more about instance Kubernetes clusters'), help_page_path('user/instance/clusters/_index.md'), target: '_blank', rel: 'noopener noreferrer')
end
end

2
app/views/clusters/clusters/show.html.haml
View File

@ -12,7 +12,7 @@
cluster_status: @cluster.status_name,
cluster_status_reason: @cluster.status_reason,
provider_type: @cluster.provider_type,
help_path: help_page_path('user/infrastructure/clusters/index.md'),
help_path: help_page_path('user/infrastructure/clusters/_index.md'),
environments_help_path: help_page_path('ci/environments/_index.md', anchor: 'create-a-static-environment'),
clusters_help_path: help_page_path('user/project/clusters/deploy_to_cluster.md'),
deploy_boards_help_path: help_page_path('user/project/deploy_boards.md', anchor: 'enabling-deploy-boards'),

8
data/deprecations/14-0-nfs-fot-git-repository-storage.yml
View File

@ -7,11 +7,11 @@
Gitaly Cluster offers tremendous benefits for our customers such as:
- [Variable replication factors](https://docs.gitlab.com/ee/administration/gitaly/index.html#replication-factor).
- [Strong consistency](https://docs.gitlab.com/ee/administration/gitaly/index.html#strong-consistency).
- [Distributed read capabilities](https://docs.gitlab.com/ee/administration/gitaly/index.html#distributed-reads).
- [Variable replication factors](https://docs.gitlab.com/ee/administration/gitaly/#replication-factor).
- [Strong consistency](https://docs.gitlab.com/ee/administration/gitaly/#strong-consistency).
- [Distributed read capabilities](https://docs.gitlab.com/ee/administration/gitaly/#distributed-reads).
We encourage customers currently using NFS for Git repositories to plan their migration by reviewing our documentation on [migrating to Gitaly Cluster](https://docs.gitlab.com/ee/administration/gitaly/index.html#migrate-to-gitaly-cluster).
We encourage customers currently using NFS for Git repositories to plan their migration by reviewing our documentation on [migrating to Gitaly Cluster](https://docs.gitlab.com/ee/administration/gitaly/#migrate-to-gitaly-cluster).
reporter: mjwood
stage: create

2
data/deprecations/14-10-old-search-migration-removal.yml
View File

@ -6,7 +6,7 @@
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.
[upgrade documentation](https://docs.gitlab.com/ee/update/#upgrading-to-a-new-major-version) for details.
stage: enablement
tiers: premium, ultimate
issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/359133

2
data/deprecations/14-5-deprecation-versions-packagetype.yml
View File

@ -3,7 +3,7 @@
removal_milestone: "15.0" # The milestone when this feature is planned to be removed
breaking_change: true
body: | # Do not modify this line, instead modify the lines below.
As part of the work to create a [Package Registry GraphQL API](https://gitlab.com/groups/gitlab-org/-/epics/6318), the Package group deprecated the `Version` type for the basic `PackageType` type and moved it to [`PackageDetailsType`](https://docs.gitlab.com/ee/api/graphql/reference/index.html#packagedetailstype).
As part of the work to create a [Package Registry GraphQL API](https://gitlab.com/groups/gitlab-org/-/epics/6318), the Package group deprecated the `Version` type for the basic `PackageType` type and moved it to [`PackageDetailsType`](https://docs.gitlab.com/ee/api/graphql/reference/#packagedetailstype).
In milestone 15.0, we will completely remove `Version` from `PackageType`.
stage: package

6
data/deprecations/14-7-deprecate-static-site-editor.yml
View File

@ -2,13 +2,13 @@
announcement_milestone: "14.7" # The milestone when this feature was first announced as deprecated.
removal_milestone: "15.0" # The milestone when this feature is planned to be removed
body: | # Do not modify this line, instead modify the lines below.
The Static Site Editor will no longer be available starting in GitLab 15.0. Improvements to the Markdown editing experience across GitLab will deliver similiar benefit but with a wider reach. Incoming requests to the Static Site Editor will be redirected to the [Web IDE](https://docs.gitlab.com/ee/user/project/web_ide/index.html).
The Static Site Editor will no longer be available starting in GitLab 15.0. Improvements to the Markdown editing experience across GitLab will deliver similiar benefit but with a wider reach. Incoming requests to the Static Site Editor will be redirected to the [Web IDE](https://docs.gitlab.com/ee/user/project/web_ide/).
Current users of the Static Site Editor can view the [documentation](https://docs.gitlab.com/ee/user/project/web_ide/index.html) for more information, including how to remove the configuration files from existing projects.
Current users of the Static Site Editor can view the [documentation](https://docs.gitlab.com/ee/user/project/web_ide/) for more information, including how to remove the configuration files from existing projects.
# The following items are not published on the docs page, but may be used in the future.
stage: Create # (optional - may be required in the future) String value of the stage that the feature was created in. e.g., Growth
tiers: [Free, Premium, Ultimate] # (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]
issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/347137 # (optional) This is a link to the deprecation issue in GitLab
documentation_url: https://docs.gitlab.com/ee/user/project/web_ide/index.html # (optional) This is a link to the current documentation page
documentation_url: https://docs.gitlab.com/ee/user/project/web_ide/ # (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

2
data/deprecations/14-7-sidekiq-metrics-health-check-donfig.yml
View File

@ -12,7 +12,7 @@
to explicitly set separate ports for metrics and health-checks.
The newly introduced settings for `sidekiq['health_checks_*']`
should always be set in `gitlab.rb`.
For more information, check the documentation for [configuring Sidekiq](https://docs.gitlab.com/ee/administration/sidekiq/index.html).
For more information, check the documentation for [configuring Sidekiq](https://docs.gitlab.com/ee/administration/sidekiq/).
These changes also require updates in either Prometheus to scrape the new endpoint or k8s health-checks to target the new
health-check port to work properly, otherwise either metrics or health-checks will disappear.

2
data/deprecations/14-8-compliance-required-pipeline-configuration-premium.yml
View File

@ -9,6 +9,6 @@
This change to move the feature to GitLab Ultimate tier is intended to help our features better align with our [pricing philosophy](https://handbook.gitlab.com/handbook/company/pricing/#three-tiers) as we see demand for this feature originating primarily from executives.
This change will also help GitLab remain consistent in its tiering strategy with the other related Ultimate-tier features of:
[Security policies](https://docs.gitlab.com/ee/user/application_security/policies/) and [compliance framework pipelines](https://docs.gitlab.com/ee/user/project/settings/index.html#compliance-pipeline-configuration).
[Security policies](https://docs.gitlab.com/ee/user/application_security/policies/) and [compliance framework pipelines](https://docs.gitlab.com/ee/user/project/settings/#compliance-pipeline-configuration).
# The following items are not published on the docs page, but may be used in the future.
stage: "Manage"

2
data/deprecations/14-8-deprecate-projectFingerprint-from-PipelineSecurityReportFinding-GraphQL.yml
View File

@ -4,7 +4,7 @@
breaking_change: true # If this deprecation is a breaking change, set this value to true
reporter: matt_wilson # GitLab username of the person reporting the deprecation
body: | # Do not modify this line, instead modify the lines below.
The `projectFingerprint` field in the [`PipelineSecurityReportFinding`](https://docs.gitlab.com/ee/api/graphql/reference/index.html#pipelinesecurityreportfinding)
The `projectFingerprint` field in the [`PipelineSecurityReportFinding`](https://docs.gitlab.com/ee/api/graphql/reference/#pipelinesecurityreportfinding)
GraphQL object is being deprecated. This field contains a "fingerprint" of security findings used to determine uniqueness.
The method for calculating fingerprints has changed, resulting in different values. Going forward, the new values will be
exposed in the UUID field. Data previously available in the `projectFingerprint` field will eventually be removed entirely.

2
data/deprecations/14-8-graphql-runner-active.yml
View File

@ -35,7 +35,7 @@
# like [Free, Silver, Gold, Core, Premium, Ultimate]
tiers:
# Links to documentation and thumbnail image
documentation_url: https://docs.gitlab.com/ee/api/graphql/reference/index.html#cirunner
documentation_url: https://docs.gitlab.com/ee/api/graphql/reference/#cirunner
image_url:
# Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
video_url:

2
data/deprecations/14-8-iteration-started-field.yml
View File

@ -5,7 +5,7 @@
removal_date: "2022-05-22" # 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.
breaking_change: true # If this deprecation is a breaking change, set this value to true
body: | # Do not modify this line, instead modify the lines below.
The `started` iteration state in the [iterations GraphQL API](https://docs.gitlab.com/ee/api/graphql/reference/index.html#iterationstate)
The `started` iteration state in the [iterations GraphQL API](https://docs.gitlab.com/ee/api/graphql/reference/#iterationstate)
and [iterations REST API](https://docs.gitlab.com/ee/api/iterations.html#list-project-iterations) is deprecated.
The GraphQL API version will be removed in GitLab 16.0. This state is being replaced with the `current` state (already available)

4
data/deprecations/14-8-request-profiling.yml
View File

@ -4,7 +4,7 @@
breaking_change: true
reporter: iroussos
body: | # Do not modify this line, instead modify the lines below.
[Request profiling](https://docs.gitlab.com/ee/administration/monitoring/performance/index.html) is deprecated in GitLab 14.8 and scheduled for removal in GitLab 15.0.
[Request profiling](https://docs.gitlab.com/ee/administration/monitoring/performance/) is deprecated in GitLab 14.8 and scheduled for removal in GitLab 15.0.
We're working on [consolidating our profiling tools](https://gitlab.com/groups/gitlab-org/-/epics/7327) and making them more easily accessible.
We [evaluated](https://gitlab.com/gitlab-org/gitlab/-/issues/350152) the use of this feature and we found that it is not widely used.
@ -14,4 +14,4 @@
stage: Monitor
tiers: [Free, Premium, Ultimate]
issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/352488
documentation_url: https://docs.gitlab.com/ee/administration/monitoring/performance/index.html
documentation_url: https://docs.gitlab.com/ee/administration/monitoring/performance/

2
data/deprecations/14-8-sast-secret-analyzer-image.yml
View File

@ -15,7 +15,7 @@
- For Container Scanning, the default image address is already updated. There is no `SECURE_ANALYZERS_PREFIX` variable for Container Scanning.
In a future release, we will stop publishing images to `registry.gitlab.com/gitlab-org/security-products/analyzers`.
Once this happens, you must take action if you manually pull images and push them into a separate registry. This is commonly the case for [offline deployments](https://docs.gitlab.com/ee/user/application_security/offline_deployments/index.html).
Once this happens, you must take action if you manually pull images and push them into a separate registry. This is commonly the case for [offline deployments](https://docs.gitlab.com/ee/user/application_security/offline_deployments/).
Otherwise, you won't receive further updates.
See the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/352564) for more details.

2
data/deprecations/15-0-instance-statistics-graphql-node-removal.yml
View File

@ -8,4 +8,4 @@
stage: Foundations
tiers: [FREE]
issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/332323
documentation_url: https://docs.gitlab.com/ee/api/graphql/reference/index.html#queryusagetrendsmeasurements
documentation_url: https://docs.gitlab.com/ee/api/graphql/reference/#queryusagetrendsmeasurements

2
data/deprecations/15-3-vulnerabilityFindingDismiss-mutation.yml
View File

@ -15,6 +15,6 @@
#
end_of_support_milestone: # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
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/api/graphql/reference/index.html#mutationvulnerabilityfindingdismiss
documentation_url: https://docs.gitlab.com/ee/api/graphql/reference/#mutationvulnerabilityfindingdismiss
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

2
data/deprecations/15-5-confidential-field-on-notes.yml
View File

@ -7,4 +7,4 @@
issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/371485
body: |
The `confidential` field for a `Note` will be deprecated and renamed to `internal`.
documentation_url: https://docs.gitlab.com/ee/api/graphql/reference/index.html#note
documentation_url: https://docs.gitlab.com/ee/api/graphql/reference/#note

2
data/deprecations/15-5-vulnerabilityFindingDismiss-mutation.yml
View File

@ -8,4 +8,4 @@
body: |
The `VulnerabilityFindingDismiss` GraphQL mutation is being deprecated and will be removed in GitLab 16.0. This mutation was not used often as the Vulnerability Finding ID was not available to users (this field was [deprecated in 15.3](https://docs.gitlab.com/ee/update/deprecations.html#use-of-id-field-in-vulnerabilityfindingdismiss-mutation)). Users should instead use `VulnerabilityDismiss` to dismiss vulnerabilities in the Vulnerability Report or `SecurityFindingDismiss` for security findings in the CI Pipeline Security tab.
tiers: "Ultimate"
documentation_url: https://docs.gitlab.com/ee/api/graphql/reference/index.html#mutationvulnerabilityfindingdismiss
documentation_url: https://docs.gitlab.com/ee/api/graphql/reference/#mutationvulnerabilityfindingdismiss

2
data/deprecations/15-7-deprecate-api-v4-runner-registration-token-reset-endpoints.yml
View File

@ -24,7 +24,7 @@
as part of the new [GitLab Runner token architecture](https://docs.gitlab.com/ee/ci/runners/new_creation_workflow.html).
The work is planned in [this epic](https://gitlab.com/groups/gitlab-org/-/epics/7633).
This new architecture introduces a new method for registering runners and will eliminate the legacy
[runner registration token](https://docs.gitlab.com/ee/security/tokens/index.html#runner-registration-tokens-deprecated).
[runner registration token](https://docs.gitlab.com/ee/security/tokens/#runner-registration-tokens-deprecated).
From GitLab 18.0 and later, the runner registration methods implemented by the new GitLab Runner token architecture will be the only supported methods.
end_of_support_milestone: # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
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]

2
data/deprecations/15-7-deprecate-kas-metrics-port-in-gitlab-chart.yml
View File

@ -14,6 +14,6 @@
# OTHER OPTIONAL FIELDS
#
tiers: [Core, Premium, Ultimate] # (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/charts/charts/gitlab/kas/index.html # (optional) This is a link to the current documentation page
documentation_url: https://docs.gitlab.com/charts/charts/gitlab/kas/ # (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

2
data/deprecations/15-8-kas-private-tls.yml
View File

@ -12,5 +12,5 @@
Because the new values provide a streamlined, comprehensive method to enable TLS for KAS, you should use `global.kas.tls.*` instead of `gitlab.kas.privateApi.tls.*`. The `gitlab.kas.privateApi.tls.*` For more information, see:
- The [merge request](https://gitlab.com/gitlab-org/charts/gitlab/-/merge_requests/2888) that introduces the `global.kas.tls.*` values.
- The [deprecated `gitlab.kas.privateApi.tls.*` documentation](https://docs.gitlab.com/charts/charts/gitlab/kas/index.html#enable-tls-communication-through-the-gitlabkasprivateapi-attributes-deprecated).
- The [deprecated `gitlab.kas.privateApi.tls.*` documentation](https://docs.gitlab.com/charts/charts/gitlab/kas/#enable-tls-communication-through-the-gitlabkasprivateapi-attributes-deprecated).
- The [new `global.kas.tls.*` documentation](https://docs.gitlab.com/charts/charts/globals.html#tls-settings-1).

2
data/deprecations/15-9-JWT-OIDC.yml
View File

@ -17,7 +17,7 @@
- `CI_JOB_JWT_V1`
- `CI_JOB_JWT_V2`
To prepare for this change, configure your pipelines to use [ID tokens](https://docs.gitlab.com/ee/ci/yaml/index.html#id_tokens)
To prepare for this change, configure your pipelines to use [ID tokens](https://docs.gitlab.com/ee/ci/yaml/#id_tokens)
instead of the deprecated tokens. For OIDC compliance, the `iss` claim now uses
the fully qualified domain name, for example `https://example.com`, previously
introduced with the `CI_JOB_JWT_V2` token.

2
data/deprecations/15-9-ci-builds-column-validations.yml
View File

@ -11,7 +11,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/372770 # (required) Link to the deprecation issue in GitLab
body: | # (required) Do not modify this line, instead modify the lines below.
While CI/CD [job names](https://docs.gitlab.com/ee/ci/jobs/index.html#job-name) have a strict 255 character limit, other CI/CD parameters do not yet have validations ensuring they also stay under the limit.
While CI/CD [job names](https://docs.gitlab.com/ee/ci/jobs/#job-name) have a strict 255 character limit, other CI/CD parameters do not yet have validations ensuring they also stay under the limit.
In GitLab 16.0, validation will be added to strictly limit the following to 255 characters as well:

2
data/deprecations/15-9-deprecate-external-field-in-graphql-release-asset-link.yml
View File

@ -6,7 +6,7 @@
breaking_change: true
reporter: ahmed.hemdan
body: |
In the [GraphQL API](https://docs.gitlab.com/ee/api/graphql/), the `external` field of [`ReleaseAssetLink` type](https://docs.gitlab.com/ee/api/graphql/reference/index.html#releaseassetlink) was used to indicate whether a [release link](https://docs.gitlab.com/ee/user/project/releases/release_fields.html#links) is internal or external to your GitLab instance.
In the [GraphQL API](https://docs.gitlab.com/ee/api/graphql/), the `external` field of [`ReleaseAssetLink` type](https://docs.gitlab.com/ee/api/graphql/reference/#releaseassetlink) was used to indicate whether a [release link](https://docs.gitlab.com/ee/user/project/releases/release_fields.html#links) is internal or external to your GitLab instance.
As of GitLab 15.9, we treat all release links as external, and therefore, this field is deprecated in GitLab 15.9, and will be removed in GitLab 16.0.
To avoid any disruptions to your workflow, please stop using the `external` field because it will be removed and will not be replaced.
stage: Release

2
data/deprecations/16-0-CiRunner-projects-default-sort.yml
View File

@ -22,6 +22,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/api/graphql/reference/index.html#cirunnerprojects # (optional) This is a link to the current documentation page
documentation_url: https://docs.gitlab.com/ee/api/graphql/reference/#cirunnerprojects # (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

2
data/deprecations/16-0-graphql-RunnerMembershipFilter-renamed.yml
View File

@ -19,6 +19,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/api/graphql/reference/index.html#cirunnermembershipfilter # (optional) This is a link to the current documentation page
documentation_url: https://docs.gitlab.com/ee/api/graphql/reference/#cirunnermembershipfilter # (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

2
data/deprecations/16-3-runner-terminationgracepriodseconds.yml
View File

@ -6,7 +6,7 @@
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-runner/-/issues/28165" # (required) Link to the deprecation issue in GitLab
body: | # (required) Do not modify this line, instead modify the lines below.
The GitLab Runner Kubernetes executor setting, `terminationGracePeriodSeconds`, is deprecated and will be removed in GitLab 17.0. To manage the cleanup and termination of GitLab Runner worker pods on Kubernetes, customers should instead configure `cleanupGracePeriodSeconds` and `podTerminationGracePeriodSeconds`. For information about how to use the `cleanupGracePeriodSeconds` and `podTerminationGracePeriodSeconds`, see the [GitLab Runner Executor documentation](https://docs.gitlab.com/runner/executors/kubernetes/index.html#other-configtoml-settings).
The GitLab Runner Kubernetes executor setting, `terminationGracePeriodSeconds`, is deprecated and will be removed in GitLab 17.0. To manage the cleanup and termination of GitLab Runner worker pods on Kubernetes, customers should instead configure `cleanupGracePeriodSeconds` and `podTerminationGracePeriodSeconds`. For information about how to use the `cleanupGracePeriodSeconds` and `podTerminationGracePeriodSeconds`, see the [GitLab Runner Executor documentation](https://docs.gitlab.com/runner/executors/kubernetes/#other-configtoml-settings).
#
# OPTIONAL END OF SUPPORT FIELDS

2
data/deprecations/16-5-offset-pagination.yml
View File

@ -6,4 +6,4 @@
stage: govern # (required) String value of the stage that the feature was created in. e.g., Growth
issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/426547 # (required) Link to the deprecation issue in GitLab
body: | # (required) Do not modify this line, instead modify the lines below.
Offset pagination for the `/users` REST API is deprecated in GitLab 16.5, and will be removed in GitLab 17.0. Use [keyset pagination](https://docs.gitlab.com/ee/api/rest/index.html#keyset-based-pagination) instead.
Offset pagination for the `/users` REST API is deprecated in GitLab 16.5, and will be removed in GitLab 17.0. Use [keyset pagination](https://docs.gitlab.com/ee/api/rest/#keyset-based-pagination) instead.

2
data/deprecations/17-4-secure-container-registries.yml
View File

@ -26,4 +26,4 @@
Offline deployments should review the [specific scanner instructions](https://docs.gitlab.com/ee/user/application_security/offline_deployments/#specific-scanner-instructions)
to ensure the correct locations are being used to mirror the required scanner images.
tiers: [Free, Premium, Ultimate]
documentation_url: https://docs.gitlab.com/ee/user/application_security/index.html#vulnerability-scanner-maintenance
documentation_url: https://docs.gitlab.com/ee/user/application_security/#vulnerability-scanner-maintenance

2
data/deprecations/17-7-RunnersRegistrationTokenReset-mutation.yml
View File

@ -20,7 +20,7 @@
as part of the new [GitLab Runner token architecture](https://docs.gitlab.com/ee/ci/runners/new_creation_workflow.html).
For details, see [epic 7633](https://gitlab.com/groups/gitlab-org/-/epics/7633).
This new architecture introduces a new method for registering runners and eliminates the legacy
[runner registration token](https://docs.gitlab.com/ee/security/tokens/index.html#runner-registration-tokens-deprecated).
[runner registration token](https://docs.gitlab.com/ee/security/tokens/#runner-registration-tokens-deprecated).
In GitLab 18.0, only the runner registration methods implemented in the new GitLab Runner token architecture will be supported.
#
# When support for this feature ends, in XX.YY milestone format.

2
data/deprecations/17-7-deprecate-SPPgraphqlmutation.yml
View File

@ -17,4 +17,4 @@
- Stop using the old mutation name `setPreReceiveSecretDetection`. Instead, use the name `setSecretPushProtection`.
- Change any references to the field `pre_receive_secret_detection_enabled` to `secret_push_protection_enabled`.
documentation_url: https://docs.gitlab.com/ee/api/graphql/reference/index.html#mutationsetsecretpushprotection
documentation_url: https://docs.gitlab.com/ee/api/graphql/reference/#mutationsetsecretpushprotection

2
data/deprecations/17-9-remove-duoProAssignedUsersCount-graphql-field.yml
View File

@ -12,5 +12,5 @@
resolution_role: Admin # Can be one of: [Admin, Owner, Maintainer, Developer]
manual_task: false # Can be true or false. Use this to denote whether a resolution action must be performed manually (true), or if it can be automated by using the API or other automation (false).
body: | # (required) Don't change this line.
In 18.0 we are removing the `duoProAssignedUsersCount` GraphQL field. Users may experience issues if they are using this field with the [`aiMetrics` API](https://docs.gitlab.com/ee/api/graphql/reference/index.html#aimetrics), and instead they can use the `duoAssignedUsersCount`. This removal is part of the [fix to count both GitLab Duo Pro and Duo seats assigned users](https://gitlab.com/gitlab-org/gitlab/-/issues/485510).
In 18.0 we are removing the `duoProAssignedUsersCount` GraphQL field. Users may experience issues if they are using this field with the [`aiMetrics` API](https://docs.gitlab.com/ee/api/graphql/reference/#aimetrics), and instead they can use the `duoAssignedUsersCount`. This removal is part of the [fix to count both GitLab Duo Pro and Duo seats assigned users](https://gitlab.com/gitlab-org/gitlab/-/issues/485510).
tiers: ultimate

2
data/deprecations/templates/_deprecation_template.md.erb
View File

@ -13,7 +13,7 @@ The following GitLab features are deprecated and no longer recommended for use.
- Some features cause breaking changes when they are removed.
- On GitLab.com, deprecated features can be removed at any time during the month leading up to the release.
- To view documentation for a removed feature, see the [GitLab Docs archive](https://docs.gitlab.com/archives/).
- For GraphQL API deprecations, you should [verify your API calls work without the deprecated items](https://docs.gitlab.com/ee/api/graphql/index.html#verify-against-the-future-breaking-change-schema).
- For GraphQL API deprecations, you should [verify your API calls work without the deprecated items](https://docs.gitlab.com/ee/api/graphql/#verify-against-the-future-breaking-change-schema).
For advanced searching and filtering of this deprecation information, try
[a tool built by our Customer Success team](https://gitlab-com.gitlab.io/cs-tools/gitlab-cs-tools/what-is-new-since/?tab=deprecations).

6
data/whats_new/202008180001_12_10.yml
View File

@ -8,7 +8,7 @@
self-managed: true
gitlab-com: true
available_in: [Ultimate]
documentation_link: https://docs.gitlab.com/ee/user/project/requirements/index.html
documentation_link: https://docs.gitlab.com/ee/user/project/requirements/
image_url: https://docs.gitlab.com/ee/user/project/requirements/img/requirements_list_v13_5.png
published_at: 2020-04-22
release: 12.10
@ -21,7 +21,7 @@
self-managed: true
gitlab-com: true
available_in: [Free, Premium, Ultimate]
documentation_link: https://docs.gitlab.com/ee/ci/examples/authenticating-with-hashicorp-vault/index.html
documentation_link: https://docs.gitlab.com/ee/ci/examples/authenticating-with-hashicorp-vault/
image_url: https://about.gitlab.com/images/12_10/jwt-vault-1.png
published_at: 2020-04-22
release: 12.10
@ -36,7 +36,7 @@
self-managed: true
gitlab-com: true
available_in: [Ultimate]
documentation_link: https://docs.gitlab.com/ee/user/project/issues/index.html#health-status
documentation_link: https://docs.gitlab.com/ee/user/project/issues/#health-status
image_url: https://about.gitlab.com/images/12_10/epic-health-status.png
published_at: 2020-04-22
release: 12.10

2
data/whats_new/202008180002_13_0.yml
View File

@ -21,7 +21,7 @@
self-managed: true
gitlab-com: true
available_in: [Free, Premium, Ultimate]
documentation_link: https://docs.gitlab.com/ee/topics/autodevops/index.html#aws-ecs
documentation_link: https://docs.gitlab.com/ee/topics/autodevops/#aws-ecs
image_url: https://docs.gitlab.com/ee/ci/img/ecs_dashboard_v12_9.png
published_at: 2020-05-22
release: 13.0

4
data/whats_new/202008180003_13_01.yml
View File

@ -8,7 +8,7 @@
self-managed: true
gitlab-com: true
available_in: [Free, Premium, Ultimate]
documentation_link: https://docs.gitlab.com/ee/operations/incident_management/index.html
documentation_link: https://docs.gitlab.com/ee/operations/incident_management/
image_url: https://about.gitlab.com/images/13_1/alert_management.png
published_at: 2020-06-22
release: 13.1
@ -43,7 +43,7 @@
self-managed: true
gitlab-com: true
available_in: [Free, Premium, Ultimate]
documentation_link: https://docs.gitlab.com/ee/user/discussions/index.html#merge-request-reviews
documentation_link: https://docs.gitlab.com/ee/user/discussions/#merge-request-reviews
image_url: https://about.gitlab.com/images/13_1/batch_comments.png
published_at: 2020-06-22
release: 13.1

4
data/whats_new/202010230001_13_05.yml
View File

@ -12,7 +12,7 @@
self-managed: true
gitlab-com: true
available_in: [Premium, Ultimate]
documentation_link: https://docs.gitlab.com/ee/user/project/wiki/index.html
documentation_link: https://docs.gitlab.com/ee/user/project/wiki/
image_url: https://about.gitlab.com/images/13_5/cdybenko-group-wiki.png
published_at: 2020-10-22
release: 13.5
@ -53,7 +53,7 @@
self-managed: true
gitlab-com: true
available_in: [Free, Premium, Ultimate]
documentation_link: https://docs.gitlab.com/ee/ci/runners/index.html#disable-shared-runners
documentation_link: https://docs.gitlab.com/ee/ci/runners/#disable-shared-runners
image_url: https://about.gitlab.com/images/13_5/enable_shared_runners_v2.png
published_at: 2020-10-22
release: 13.5

2
data/whats_new/202011230001_13_06.yml
View File

@ -40,7 +40,7 @@
self-managed: true
gitlab-com: true
available_in: [Premium, Ultimate]
documentation_link: https://docs.gitlab.com/ee/user/group/repositories_analytics/index.html#latest-project-test-coverage-list
documentation_link: https://docs.gitlab.com/ee/user/group/repositories_analytics/#latest-project-test-coverage-list
image_url: https://about.gitlab.com/images/13_6/display_selected_coverage_projects_example.png
published_at: 2020-11-22
release: 13.6

4
data/whats_new/202101140001_13_08.yml
View File

@ -8,7 +8,7 @@
self-managed: true
gitlab-com: true
available_in: [Free, Premium, Ultimate]
documentation_link: https://docs.gitlab.com/ee/ci/pipeline_editor/index.html
documentation_link: https://docs.gitlab.com/ee/ci/pipeline_editor/
image_url: https://img.youtube.com/vi/MQpSyvMpsHA/hqdefault.jpg
published_at: 2021-01-22
release: 13.8
@ -76,7 +76,7 @@
self-managed: true
gitlab-com: false
available_in: [Free, Premium, Ultimate]
documentation_link: https://docs.gitlab.com/charts/charts/gitlab/gitlab-pages/index.html
documentation_link: https://docs.gitlab.com/charts/charts/gitlab/gitlab-pages/
image_url: https://about.gitlab.com/images/home/kubernetes.png
published_at: 2021-01-22
release: 13.8

8
data/whats_new/202102180001_13_09.yml
View File

@ -7,7 +7,7 @@
self-managed: true
gitlab-com: true
available_in: [Free, Premium, Ultimate]
documentation_link: https://docs.gitlab.com/ee/ci/yaml/index.html#reference-tags
documentation_link: https://docs.gitlab.com/ee/ci/yaml/#reference-tags
image_url: https://about.gitlab.com/images/13_9/reference.png
published_at: 2021-02-22
release: 13.9
@ -31,7 +31,7 @@
self-managed: true
gitlab-com: true
available_in: [Free, Premium, Ultimate]
documentation_link: https://docs.gitlab.com/ee/ci/examples/authenticating-with-hashicorp-vault/index.html
documentation_link: https://docs.gitlab.com/ee/ci/examples/authenticating-with-hashicorp-vault/
image_url: https://about.gitlab.com/images/icons/get-a-license.svg
published_at: 2021-02-22
release: 13.9
@ -74,14 +74,14 @@
description: |
Systems administrators occasionally perform maintenance operations on their GitLab instance to keep it performing optimally. Administrators want to offer the highest level of access to their users while these operations are taking place. For example, you may want to perform a [failover test to a secondary site](https://docs.gitlab.com/ee/administration/geo/disaster_recovery/planned_failover.html) as part of the company's business continuity plan. Prior to the failover, you want to pause changes for a short period to ensure the secondary is fully synchronized. Until GitLab 13.8, you could [restrict users from logging in](https://docs.gitlab.com/omnibus/maintenance/#restrict-users-from-logging-into-gitlab), but this would block the entire UI and would render GitLab inaccessible to users.
GitLab 13.9 introduces [maintenance mode](https://docs.gitlab.com/ee/administration/maintenance_mode/index.html), where write operations are disabled at the application level. This means that GitLab is effectively in a read-only state for all non-administrative users (administrators are still able to edit application settings and [background jobs continue](https://docs.gitlab.com/ee/administration/maintenance_mode/index.html#background-jobs)). Regular users are able to log in to GitLab, view the interface and perform other read-only operations, such as `git clone` or `git pull`. Using maintenance mode, systems administrators can perform maintenance operations, such as failing over to a secondary site, with minimal disruption to regular users.
GitLab 13.9 introduces [maintenance mode](https://docs.gitlab.com/ee/administration/maintenance_mode/), where write operations are disabled at the application level. This means that GitLab is effectively in a read-only state for all non-administrative users (administrators are still able to edit application settings and [background jobs continue](https://docs.gitlab.com/ee/administration/maintenance_mode/#background-jobs)). Regular users are able to log in to GitLab, view the interface and perform other read-only operations, such as `git clone` or `git pull`. Using maintenance mode, systems administrators can perform maintenance operations, such as failing over to a secondary site, with minimal disruption to regular users.
Note that GitLab already [supports zero-downtime updates](https://docs.gitlab.com/omnibus/update/#zero-downtime-updates) and enabling maintenance mode is not required to keep your instance up-to-date.
stage: Enablement
self-managed: true
gitlab-com: false
available_in: [Premium, Ultimate]
documentation_link: https://docs.gitlab.com/ee/administration/maintenance_mode/index.html
documentation_link: https://docs.gitlab.com/ee/administration/maintenance_mode/
image_url: https://about.gitlab.com/images/13_9/maintenance_mode.png
published_at: 2021-02-22
release: 13.9

2
data/whats_new/202104220001_13_11.yml
View File

@ -48,7 +48,7 @@
self-managed: true
gitlab-com: true
available_in: [Free, Premium, Ultimate]
documentation_link: https://docs.gitlab.com/ee/ci/yaml/index.html#multiple-caches
documentation_link: https://docs.gitlab.com/ee/ci/yaml/#multiple-caches
image_url: https://about.gitlab.com/images/13_11/cache.png
published_at: 2021-04-22
release: 13.11

4
data/whats_new/202105220001_13_12.yml
View File

@ -35,7 +35,7 @@
self-managed: true
gitlab-com: true
available_in: [Free, Premium, Ultimate]
documentation_link: https://docs.gitlab.com/ee/ci/yaml/index.html#artifactsexpire_in
documentation_link: https://docs.gitlab.com/ee/ci/yaml/#artifactsexpire_in
image_url: https://about.gitlab.com/images/growth/verify.png
published_at: 2021-05-22
release: 13.12
@ -56,7 +56,7 @@
release: 13.12
- name: Configuration tool for Secret Detection
description: |
Following in the footsteps of the [GitLab SAST configuration tool](https://docs.gitlab.com/ee/user/application_security/sast/index.html#configure-sast-in-the-ui) we are adding support for Secret Detection on the Security Configuration page. We believe that [security is a team effort](https://about.gitlab.com/direction/secure/#security-is-a-team-effort) and this configuration experience makes it easier for non-CI experts to get started with [GitLab Secret Detection](https://docs.gitlab.com/ee/user/application_security/secret_detection/). The tool helps a user create a merge request to enable Secret Detection scanning while leveraging best configuration practices like using the GitLab-managed [`SAST.gitlab-ci.yml` template](https://gitlab.com/gitlab-org/gitlab/blob/master/lib/gitlab/ci/templates/Security/SAST.gitlab-ci.yml). The Configuration tool can create a new `.gitlab-ci.yml` file if one does not exist or update existing simple GitLab CI files, allowing the tool to be used with projects that already have GitLab CI setup.
Following in the footsteps of the [GitLab SAST configuration tool](https://docs.gitlab.com/ee/user/application_security/sast/#configure-sast-in-the-ui) we are adding support for Secret Detection on the Security Configuration page. We believe that [security is a team effort](https://about.gitlab.com/direction/secure/#security-is-a-team-effort) and this configuration experience makes it easier for non-CI experts to get started with [GitLab Secret Detection](https://docs.gitlab.com/ee/user/application_security/secret_detection/). The tool helps a user create a merge request to enable Secret Detection scanning while leveraging best configuration practices like using the GitLab-managed [`SAST.gitlab-ci.yml` template](https://gitlab.com/gitlab-org/gitlab/blob/master/lib/gitlab/ci/templates/Security/SAST.gitlab-ci.yml). The Configuration tool can create a new `.gitlab-ci.yml` file if one does not exist or update existing simple GitLab CI files, allowing the tool to be used with projects that already have GitLab CI setup.
stage: secure
self-managed: true
gitlab-com: true

6
data/whats_new/202106220001_14_0.yml
View File

@ -124,7 +124,7 @@
release: 14.0
- name: Change an issue's type
description: |
In some cases, you may wish to change an issue's type. For example, you may want to escalate an issue to an [incident](https://docs.gitlab.com/ee/operations/incident_management/index.html) to ensure that your team handles the problem properly. To change an issue's type, edit the issue and select an issue type from the **Issue type** selector menu.
In some cases, you may wish to change an issue's type. For example, you may want to escalate an issue to an [incident](https://docs.gitlab.com/ee/operations/incident_management/) to ensure that your team handles the problem properly. To change an issue's type, edit the issue and select an issue type from the **Issue type** selector menu.
stage: Monitor
self-managed: true
gitlab-com: true
@ -150,12 +150,12 @@
description: |
Terraform modules play a central role in building standard infrastructure components throughout an organization. Up to GitLab 13.12, GitLab users had to use either a third-party Terraform module registry, local modules, or Git-based modules. While these options work well, they do not help with the distribution of the modules and they lack proper versioning support, which introduces risks for module users. GitLab 14.0 extends our [Infrastructure-as-Code offerings](https://docs.gitlab.com/ee/user/infrastructure/) with a Terraform module registry. Now, you can use the Terraform module registry built into GitLab to discover Terraform modules with semantic versioning support for upgrades and maintenance. Moreover, you can publish modules easily using GitLab CI/CD.
While following Terraform's best practices, we recommend developing each Terraform module in a dedicated GitLab project. To simplify the transition to the registry, users can host and publish multiple modules from a single GitLab repository. You can learn more about publishing and consuming a new module [in our documentation](https://docs.gitlab.com/ee/user/packages/terraform_module_registry/index.html).
While following Terraform's best practices, we recommend developing each Terraform module in a dedicated GitLab project. To simplify the transition to the registry, users can host and publish multiple modules from a single GitLab repository. You can learn more about publishing and consuming a new module [in our documentation](https://docs.gitlab.com/ee/user/packages/terraform_module_registry/).
stage: Configure
self-managed: true
gitlab-com: true
available_in: [Free, Premium, Ultimate]
documentation_link: https://docs.gitlab.com/ee/user/packages/terraform_module_registry/index.html
documentation_link: https://docs.gitlab.com/ee/user/packages/terraform_module_registry/
image_url: https://about.gitlab.com/images/14_0/terraform-module-registry.png
published_at: 2021-06-22
release: 14.0

6
data/whats_new/202107220001_14_1.yml
View File

@ -12,7 +12,7 @@
- name: Track use of security scanning across multiple teams
description: |
Track which groups across your organization have enabled SAST and DAST scanning. This is helpful for verifying compliance with organizational requirements, responding to audit requests, and tracking progress on company initiatives to make applications more secure. To track adoption, go to the **Sec** tab in DevOps Adoption either at the group level or instance level.
To see groups that have enabled fuzz testing and dependency scanning, use [the DevOps API](https://docs.gitlab.com/ee/api/graphql/reference/index.html#devopsadoptionsnapshot). Fuzz testing and dependency scanning will be added to the DevOps Adoption UI in an upcoming release.
To see groups that have enabled fuzz testing and dependency scanning, use [the DevOps API](https://docs.gitlab.com/ee/api/graphql/reference/#devopsadoptionsnapshot). Fuzz testing and dependency scanning will be added to the DevOps Adoption UI in an upcoming release.
stage: Foundations
self-managed: true
gitlab-com: true
@ -53,12 +53,12 @@
release: 14.1
- name: Registration Features
description: |
[Registration Features](https://docs.gitlab.com/ee/development/service_ping/index.html#registration-features-program) introduces the ability for free, self-managed users running GitLab EE to access paid features by registering with GitLab and sharing activity data via [Service Ping](https://docs.gitlab.com/ee/development/service_ping/index.html#what-is-service-ping). The first feature introduced is [email from GitLab](https://docs.gitlab.com/ee/tools/email.html), enabling instance administrators to email users within their instance.
[Registration Features](https://docs.gitlab.com/ee/development/service_ping/#registration-features-program) introduces the ability for free, self-managed users running GitLab EE to access paid features by registering with GitLab and sharing activity data via [Service Ping](https://docs.gitlab.com/ee/development/service_ping/#what-is-service-ping). The first feature introduced is [email from GitLab](https://docs.gitlab.com/ee/tools/email.html), enabling instance administrators to email users within their instance.
stage: Growth
self-managed: true
gitlab-com: false
available_in: [Free]
documentation_link: 'https://docs.gitlab.com/ee/development/service_ping/index.html#registration-features-program'
documentation_link: 'https://docs.gitlab.com/ee/development/service_ping/#registration-features-program'
image_url: https://about.gitlab.com/images/14_1/registration-features.png
published_at: 2021-07-22
release: 14.1

2
data/whats_new/202108190001_14_02.yml
View File

@ -18,7 +18,7 @@
self-managed: true
gitlab-com: true
available_in: [Free, Premium, Ultimate]
documentation_link: 'https://docs.gitlab.com/ee/subscriptions/gitlab_com/index.html#ci-pipeline-minutes'
documentation_link: 'https://docs.gitlab.com/ee/subscriptions/gitlab_com/#ci-pipeline-minutes'
image_url: https://about.gitlab.com/images/14_2/CI_minutes_usage_graph.png
published_at: 2021-08-22
release: 14.2

6
data/whats_new/202109200001_14_03.yml
View File

@ -24,7 +24,7 @@
release: 14.3
- name: Group-level permissions for Protected Environments
description: |
In this release, we are introducing group-level protected environments, based on the [deployment tier](https://docs.gitlab.com/ee/ci/environments/index.html#deployment-tier-of-environments) as the identifier. This enables operators to responsibly lock down deployments to higher tier environments without unnecessarily preventing developers from doing their work as the maintainers of their individual projects.
In this release, we are introducing group-level protected environments, based on the [deployment tier](https://docs.gitlab.com/ee/ci/environments/#deployment-tier-of-environments) as the identifier. This enables operators to responsibly lock down deployments to higher tier environments without unnecessarily preventing developers from doing their work as the maintainers of their individual projects.
stage: Release
self-managed: true
gitlab-com: true
@ -59,9 +59,9 @@
release: 14.3
- name: Add GitLab CI/CD configuration conditionally with `include`
description: |
[`include`](https://docs.gitlab.com/ee/ci/yaml/index.html#include) is one of the most popular keywords to use when writing a full CI/CD pipeline. If you are building larger pipelines, you are probably using the `include` keyword to bring external YAML configuration into your pipeline.
[`include`](https://docs.gitlab.com/ee/ci/yaml/#include) is one of the most popular keywords to use when writing a full CI/CD pipeline. If you are building larger pipelines, you are probably using the `include` keyword to bring external YAML configuration into your pipeline.
In this release, we are expanding the power of the keyword so you can use `include` with [`rules`](https://docs.gitlab.com/ee/ci/yaml/index.html#include) conditions. Now, you can decide when external CI/CD configuration should or shouldn't be included. This will help you write a standardized pipeline with the ability to dynamically modify itself based on the conditions you choose.
In this release, we are expanding the power of the keyword so you can use `include` with [`rules`](https://docs.gitlab.com/ee/ci/yaml/#include) conditions. Now, you can decide when external CI/CD configuration should or shouldn't be included. This will help you write a standardized pipeline with the ability to dynamically modify itself based on the conditions you choose.
stage: Verify
self-managed: true
gitlab-com: true

2
data/whats_new/2021102000001_14_04.yml
View File

@ -5,7 +5,7 @@
self-managed: true
gitlab-com: true
available_in: [Ultimate]
documentation_link: 'https://docs.gitlab.com/ee/user/application_security/dast/index.html#schedule-an-on-demand-scan'
documentation_link: 'https://docs.gitlab.com/ee/user/application_security/dast/#schedule-an-on-demand-scan'
image_url: https://about.gitlab.com/images/14_4/dast_on_demand_schedule.png
published_at: 2021-10-22
release: 14.4

2
data/whats_new/2021111800001_14_05.yml
View File

@ -11,7 +11,7 @@
release: 14.5
- name: Add personal README to profile
description: |
You can now add a README section to your GitLab profile! This is a great way to tell others about, your interests, how you work, or anything else you want! To add a README section, create a new public project with the same name as your user account and add a new [README file](https://docs.gitlab.com/ee/user/project/repository/index.html#readme-and-index-files). The contents of that file are automatically shown on your GitLab profile.
You can now add a README section to your GitLab profile! This is a great way to tell others about, your interests, how you work, or anything else you want! To add a README section, create a new public project with the same name as your user account and add a new [README file](https://docs.gitlab.com/ee/user/project/repository/#readme-and-index-files). The contents of that file are automatically shown on your GitLab profile.
stage: Foundations
self-managed: true
gitlab-com: true

2
data/whats_new/202201200001_14_07.yml
View File

@ -5,7 +5,7 @@
self-managed: true
gitlab-com: false
available_in: [Free, Premium, Ultimate]
documentation_link: 'https://docs.gitlab.com/runner/install/index.html#fips-compliant-gitlab-runner'
documentation_link: 'https://docs.gitlab.com/runner/install/#fips-compliant-gitlab-runner'
image_url: https://about.gitlab.com/images/growth/verify.png
published_at: 2022-01-22
release: 14.7

4
data/whats_new/202202210001_14_08.yml
View File

@ -19,7 +19,7 @@
self-managed: true
gitlab-com: true
available_in: [Free, Premium, Ultimate]
documentation_link: 'https://docs.gitlab.com/ee/ci/pipeline_editor/index.html#validate-ci-configuration'
documentation_link: 'https://docs.gitlab.com/ee/ci/pipeline_editor/#validate-ci-configuration'
image_url: 'https://about.gitlab.com/images/growth/verify.png'
published_at: 2022-02-22
release: 14.8
@ -85,7 +85,7 @@
self-managed: true
gitlab-com: true
available_in: [Premium, Ultimate]
documentation_link: 'https://docs.gitlab.com/ee/user/group/roadmap/index.html#roadmap-settings'
documentation_link: 'https://docs.gitlab.com/ee/user/group/roadmap/#roadmap-settings'
image_url: 'https://about.gitlab.com/images/14_8/rp_roadmap_settings.png'
published_at: 2022-02-22
release: 14.8

2
data/whats_new/202205220001_15_0.yml
View File

@ -52,7 +52,7 @@
self-managed: true # Boolean value (true or false)
gitlab-com: true # Boolean value (true or false)
available_in: [Free, Premium, Ultimate] # Array of strings. The Array brackets are required here. e.g., [Free, Starter, Premium, Ultimate]
documentation_link: https://docs.gitlab.com/ee/user/discussions/index.html#add-an-internal-note # This is the documentation URL, but can be a URL to a video if there is one
documentation_link: https://docs.gitlab.com/ee/user/discussions/#add-an-internal-note # This is the documentation URL, but can be a URL to a video if there is one
image_url: https://about.gitlab.com/images/15_0/add_internal_note_v15_0.png # This should be a full URL, generally taken from the release post content. If a video, use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
published_at: 2022-05-22 # YYYY-MM-DD
release: 15.0 # XX.Y

2
data/whats_new/202209220001_15_04.yml
View File

@ -38,7 +38,7 @@
self-managed: false # Boolean value (true or false)
gitlab-com: true # Boolean value (true or false)
available_in: [Premium, Ultimate] # Array of strings. The Array brackets are required here. e.g., [Free, Premium, Ultimate]
documentation_link: 'https://docs.gitlab.com/ee/user/group/saml_sso/index.html#bypass-user-verification-with-verified-domains' # This is the documentation URL, but can be a URL to a video if there is one
documentation_link: 'https://docs.gitlab.com/ee/user/group/saml_sso/#bypass-user-verification-with-verified-domains' # This is the documentation URL, but can be a URL to a video if there is one
image_url: https://about.gitlab.com/images/15_4/domain-verification.png # This should be a full URL, generally taken from the release post content. If a video, use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
published_at: 2022-09-22 # YYYY-MM-DD
release: 15.4 # XX.Y

4
data/whats_new/202210220001_15_5.yml
View File

@ -1,11 +1,11 @@
- name: "Deploy apps to Google Cloud with GitLab Cloud Seed"
description: |
Cloud Seed allows GitLab and Google Cloud customers to migrate to the cloud using a single platform, consolidating their tech stack without slowing down their cloud adoption process. Cloud Seed is built into the GitLab web UI and leverages CI/CD pipeline capabilities. It is specifically tailored to offer a frictionless developer experience for consuming Google Cloud services, supporting [Service Accounts](https://docs.gitlab.com/ee/cloud_seed/index.html#set-up-deployment-credentials), [Regions](https://docs.gitlab.com/ee/cloud_seed/index.html#configure-your-preferred-gcp-region), [Cloud Run](https://docs.gitlab.com/ee/cloud_seed/index.html#deploy-to-google-cloud-run), and [Cloud SQL](https://docs.gitlab.com/ee/cloud_seed/index.html#provision-cloud-sql-databases).
Cloud Seed allows GitLab and Google Cloud customers to migrate to the cloud using a single platform, consolidating their tech stack without slowing down their cloud adoption process. Cloud Seed is built into the GitLab web UI and leverages CI/CD pipeline capabilities. It is specifically tailored to offer a frictionless developer experience for consuming Google Cloud services, supporting [Service Accounts](https://docs.gitlab.com/ee/cloud_seed/#set-up-deployment-credentials), [Regions](https://docs.gitlab.com/ee/cloud_seed/#configure-your-preferred-gcp-region), [Cloud Run](https://docs.gitlab.com/ee/cloud_seed/#deploy-to-google-cloud-run), and [Cloud SQL](https://docs.gitlab.com/ee/cloud_seed/#provision-cloud-sql-databases).
stage: Release
self-managed: true
gitlab-com: true
available_in: [Free, Premium, Ultimate]
documentation_link: 'https://docs.gitlab.com/ee/cloud_seed/index.html'
documentation_link: 'https://docs.gitlab.com/ee/cloud_seed/'
image_url: 'https://img.youtube.com/vi/zDMGCyAgCPY/hqdefault.jpg'
published_at: 2022-10-22
release: 15.5

6
data/whats_new/202212200001_15_07.yml
View File

@ -92,14 +92,14 @@
release: 15.7
- name: "Select predefined CI/CD variables values from a dropdown list"
description: | # Do not modify this line, instead modify the lines below.
Previously, you could [pre-fill CI/CD variables in the "Run pipeline" page](https://docs.gitlab.com/ee/ci/pipelines/index.html#prefill-variables-in-manual-pipelines), with a specific value. Unfortunately, if you had multiple options for the variable's value, you still had to manually input the option you wanted. This was an error-prone process because you could easily input an invalid value, or just mistype it.
Previously, you could [pre-fill CI/CD variables in the "Run pipeline" page](https://docs.gitlab.com/ee/ci/pipelines/#prefill-variables-in-manual-pipelines), with a specific value. Unfortunately, if you had multiple options for the variable's value, you still had to manually input the option you wanted. This was an error-prone process because you could easily input an invalid value, or just mistype it.
In this release, we've added the ability to set a list of values which are surfaced in a drop-down list in the "Run pipeline" page. Now you can define the exact list of values that are valid for each CI/CD variable when running a pipeline manually, greatly simplifying your workflow when using manually-triggered pipelines.
stage: configure
self-managed: true
gitlab-com: true
available_in: [Free, Premium, Ultimate]
documentation_link: https://docs.gitlab.com/ee/ci/pipelines/index.html#prefill-variables-in-manual-pipelines
documentation_link: https://docs.gitlab.com/ee/ci/pipelines/#prefill-variables-in-manual-pipelines
image_url: https://about.gitlab.com/images/15_7/prefill.png
published_at: 2022-12-22
release: 15.7
@ -123,7 +123,7 @@
self-managed: true
gitlab-com: true
available_in: [Free, Premium, Ultimate]
documentation_link: https://docs.gitlab.com/ee/ci/jobs/index.html#specifying-variables-when-running-manual-jobs
documentation_link: https://docs.gitlab.com/ee/ci/jobs/#specifying-variables-when-running-manual-jobs
image_url: https://img.youtube.com/vi/YTM_BYL3gXI/hqdefault.jpg
published_at: 2022-12-22
release: 15.7

4
data/whats_new/202305220001_16_0.yml
View File

@ -124,12 +124,12 @@
After the GitLab Agent for Kubernetes is configured and [the dependencies are installed](https://docs.gitlab.com/ee/user/workspace/#prerequisites) in your self-hosted cluster or cloud platform of choice, you can define your development environment in a `.devfile.yaml` file and store it in a public project. Then, you and any other developers with access to the agent can create a workspace based on the `.devfile.yaml` file and edit directly in the embedded Web IDE. You'll have full terminal access to the container, allowing you to work more efficiently. When you're done, or if something goes wrong, you can shut down the workspace and start a fresh, new workspace for your next development task.
This short video walks you through the lifecycle of a workspace in the current Beta. Learn more about workspaces in the [documentation](https://docs.gitlab.com/ee/user/workspace/index.html) and let us know what you think in the [feedback issue](https://gitlab.com/gitlab-org/gitlab/-/issues/410031).
This short video walks you through the lifecycle of a workspace in the current Beta. Learn more about workspaces in the [documentation](https://docs.gitlab.com/ee/user/workspace/) and let us know what you think in the [feedback issue](https://gitlab.com/gitlab-org/gitlab/-/issues/410031).
stage: Create
self-managed: true
gitlab-com: true
available_in: [Premium, Ultimate]
documentation_link: https://docs.gitlab.com/ee/user/workspace/index.html
documentation_link: https://docs.gitlab.com/ee/user/workspace/
image_url: https://img.youtube.com/vi/yjweL075Cdo/hqdefault.jpg
published_at: 2023-05-22
release: 16.0

2
data/whats_new/202306220001_16_1.yml
View File

@ -18,7 +18,7 @@
self-managed: true
gitlab-com: true
available_in: [Free, Premium, Ultimate]
documentation_link: https://docs.gitlab.com/ee/tutorials/left_sidebar/index.html
documentation_link: https://docs.gitlab.com/ee/tutorials/left_sidebar/
image_url: https://img.youtube.com/vi/rGTl9_HIpbY/hqdefault.jpg
published_at: 2023-06-22
release: 16.1

2
data/whats_new/202309220001_16_4.yml
View File

@ -59,7 +59,7 @@
available_in: [Free, Premium, Ultimate]
self-managed: true
gitlab-com: true
documentation_link: 'https://docs.gitlab.com/ee/ci/yaml/index.html#id_tokens'
documentation_link: 'https://docs.gitlab.com/ee/ci/yaml/#id_tokens'
image_url: 'https://about.gitlab.com/images/16_4/id_tokens_img.png'
published_at: 2023-09-22
release: 16.4

2
data/whats_new/202312210001_16_7.yml
View File

@ -4,7 +4,7 @@
GitLab Duo Code Suggestions helps teams create software faster and more efficiently, by completing lines of code and defining and generating logic for functions.
Code Suggestions is built with privacy as a critical foundation. Private, non-public customer code stored in GitLab is not used as training data. Learn about [data usage](https://docs.gitlab.com/ee/user/project/repository/code_suggestions/_index.html#code-suggestions-data-usage) when using Code Suggestions.
Code Suggestions is built with privacy as a critical foundation. Private, non-public customer code stored in GitLab is not used as training data. Learn about [data usage](https://docs.gitlab.com/ee/user/project/repository/code_suggestions/#code-suggestions-data-usage) when using Code Suggestions.
In the general release, we've made [Code Suggestions available across several IDEs](https://docs.gitlab.com/ee/user/project/repository/code_suggestions/#supported-editor-extensions). Code Suggestions is also now more intuitive and responsive.

2
data/whats_new/202401180001_16_8.yml
View File

@ -63,7 +63,7 @@
self-managed: true
gitlab-com: true
available_in: [Ultimate]
documentation_link: https://docs.gitlab.com/ee/user/group/issues_analytics/index.html
documentation_link: https://docs.gitlab.com/ee/user/group/issues_analytics/
image_url: https://about.gitlab.com/images/16_8/closed_issues_analytics.png
published_at: 2024-01-18
release: 16.8

4
data/whats_new/202402130001_16_9.yml
View File

@ -63,14 +63,14 @@
- name: Expanded options for auto-canceling pipelines
description: |
Currently, to use the [auto-cancel redundant pipeline feature](https://docs.gitlab.com/ee/ci/pipelines/settings.html#auto-cancel-redundant-pipelines), you must set jobs that can be canceled as [`interruptible: true`](https://docs.gitlab.com/ee/ci/yaml/index.html#interruptible) to determine whether or not a pipeline can be canceled. But this only applies to jobs that are actively running when GitLab tries to cancel the pipeline. Any jobs that have not yet started (are in "pending" status) are also considered safe to cancel, regardless of their `interruptible` configuration.
Currently, to use the [auto-cancel redundant pipeline feature](https://docs.gitlab.com/ee/ci/pipelines/settings.html#auto-cancel-redundant-pipelines), you must set jobs that can be canceled as [`interruptible: true`](https://docs.gitlab.com/ee/ci/yaml/#interruptible) to determine whether or not a pipeline can be canceled. But this only applies to jobs that are actively running when GitLab tries to cancel the pipeline. Any jobs that have not yet started (are in "pending" status) are also considered safe to cancel, regardless of their `interruptible` configuration.
This lack of flexibility hinders users who want more control over which exact jobs can be canceled by the auto-cancel pipeline feature. To address this limitation, we are pleased to announce the introduction of the `auto_cancel:on_new_commit` keywords with more granular control over job cancellation. If the legacy behavior did not work for you, you now have the option to configure the pipeline to only cancel jobs that are explicitly set with `interruptible: true`, even if they haven't started yet. You can also set jobs to never be automatically canceled.
stage: verify
self-managed: true
gitlab-com: true
available_in: [Free, Premium, Ultimate]
documentation_link: https://docs.gitlab.com/ee/ci/yaml/index.html#workflowauto_cancelon_new_commit
documentation_link: https://docs.gitlab.com/ee/ci/yaml/#workflowauto_cancelon_new_commit
image_url: https://about.gitlab.com/images/16_9/interruptible.png
published_at: 2024-02-15
release: 16.9

2
data/whats_new/202403210001_16_10.yml
View File

@ -33,7 +33,7 @@
self-managed: true
gitlab-com: true
available_in: [Free, Premium, Ultimate]
documentation_link: https://docs.gitlab.com/ee/user/project/wiki/index.html#wiki-page-templates
documentation_link: https://docs.gitlab.com/ee/user/project/wiki/#wiki-page-templates
image_url: https://about.gitlab.com/images/16_10/wiki_templates.gif
published_at: 2024-03-21
release: 16.10

2
data/whats_new/202404160001_16_11.yml
View File

@ -53,7 +53,7 @@
self-managed: true
gitlab-com: true
available_in: [Premium, Ultimate]
documentation_link: https://docs.gitlab.com/ee/editor_extensions/jetbrains_ide/index.html
documentation_link: https://docs.gitlab.com/ee/editor_extensions/jetbrains_ide/
image_url: https://about.gitlab.com/images/16_11/create-duo-chat-in-jetbrains.png
published_at: 2024-04-18
release: 16.11

2
data/whats_new/20240620001_17_1.yml
View File

@ -38,7 +38,7 @@
Need to bypass secret push protection for testing? When you skip secret push detection, GitLab logs an audit event so you can investigate.
Secret push protection is available on GitLab.com and for Dedicated customers as a [Beta](https://docs.gitlab.com/ee/policy/experiment-beta-support.html#beta) feature and can be enabled on a [per project basis](https://docs.gitlab.com/ee/user/application_security/secret_detection/secret_push_protection/index.html#enable-secret-push-protection-in-a-project). You can help us improve secret push protection by providing feedback in [issue 467408](https://gitlab.com/gitlab-org/gitlab/-/issues/467408).
Secret push protection is available on GitLab.com and for Dedicated customers as a [Beta](https://docs.gitlab.com/ee/policy/experiment-beta-support.html#beta) feature and can be enabled on a [per project basis](https://docs.gitlab.com/ee/user/application_security/secret_detection/secret_push_protection/#enable-secret-push-protection-in-a-project). You can help us improve secret push protection by providing feedback in [issue 467408](https://gitlab.com/gitlab-org/gitlab/-/issues/467408).
stage: secure
self-managed: false
gitlab-com: true

2
data/whats_new/202407180001_17_02.yml
View File

@ -25,7 +25,7 @@
self-managed: true # Boolean value (true or false)
gitlab-com: true # Boolean value (true or false)
available_in: [Free, Premium, Ultimate] # Array of strings. The Array brackets are required here. e.g., [Free, Premium, Ultimate]
documentation_link: https://docs.gitlab.com/ee/user/packages/terraform_module_registry/index.html#view-terraform-modules # This is the documentation URL, but can be a URL to a video if there is one
documentation_link: https://docs.gitlab.com/ee/user/packages/terraform_module_registry/#view-terraform-modules # This is the documentation URL, but can be a URL to a video if there is one
image_url: https://img.youtube.com/vi/SWRwW4pS7Gk/hqdefault.jpg # This should be a full URL, generally taken from the release post content. If a video, use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg
published_at: 2024-07-18 # YYYY-MM-DD
release: 17.2 # XX.Y

2
data/whats_new/202409190001_17_04.yml
View File

@ -31,7 +31,7 @@
self-managed: true
gitlab-com: true
available_in: [Free, Premium, Ultimate]
documentation_link: https://docs.gitlab.com/ee/user/project/web_ide/index.html#extension-marketplace
documentation_link: https://docs.gitlab.com/ee/user/project/web_ide/#extension-marketplace
image_url: https://about.gitlab.com/images/17_4/extensions-marketplace.png
published_at: 2024-09-19
release: 17.4

2
data/whats_new/202412190001_17_07.yml
View File

@ -65,7 +65,7 @@
self-managed: true
gitlab-com: true
available_in: ["Premium", "Ultimate"]
documentation_link: https://docs.gitlab.com/ee/api/graphql/reference/index.html#queryprojectsusingcomponents
documentation_link: https://docs.gitlab.com/ee/api/graphql/reference/#queryprojectsusingcomponents
image_url: https://about.gitlab.com/images/17_7/catalog.png
published_at: 2024-12-19
release: 17.7

12
db/docs/ml_model_metadata.yml
View File

@ -8,14 +8,6 @@ gitlab_schema: gitlab_main_cell
description: A Model Metadata record holds extra information about the model
introduced_by_url: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/134443
milestone: 16.6
desired_sharding_key:
project_id:
references: projects
backfill_via:
parent:
foreign_key: model_id
table: ml_models
sharding_key: project_id
belongs_to: model
desired_sharding_key_migration_job_name: BackfillMlModelMetadataProjectId
table_size: small
sharding_key:
project_id: projects

14
db/post_migrate/20250131091751_add_ml_model_metadata_project_id_not_null_constraint.rb Normal file
View File

@ -0,0 +1,14 @@
# frozen_string_literal: true
class AddMlModelMetadataProjectIdNotNullConstraint < Gitlab::Database::Migration[2.2]
disable_ddl_transaction!
milestone '17.9'
def up
add_not_null_constraint :ml_model_metadata, :project_id
end
def down
remove_not_null_constraint :ml_model_metadata, :project_id
end
end

1
db/schema_migrations/20250131091751 Normal file
View File

@ -0,0 +1 @@
e29c1333bba56955916ee34f0a606f4335104843c183fc425f1da5fad31f0435

3
db/structure.sql
View File

@ -16553,7 +16553,8 @@ CREATE TABLE ml_model_metadata (
value text NOT NULL,
project_id bigint,
CONSTRAINT check_26d3322153 CHECK ((char_length(value) <= 5000)),
CONSTRAINT check_36240c80a7 CHECK ((char_length(name) <= 255))
CONSTRAINT check_36240c80a7 CHECK ((char_length(name) <= 255)),
CONSTRAINT check_9a8615c7cc CHECK ((project_id IS NOT NULL))
);
CREATE SEQUENCE ml_model_metadata_id_seq

6
doc/administration/backup_restore/troubleshooting_backup_gitlab.md
View File

@ -17,7 +17,7 @@ that contain required, sensitive information. If the key is lost, GitLab can't
decrypt those columns, preventing access to the following items:
- [CI/CD variables](../../ci/variables/_index.md)
- [Kubernetes / GCP integration](../../user/infrastructure/clusters/index.md)
- [Kubernetes / GCP integration](../../user/infrastructure/clusters/_index.md)
- [Custom Pages domains](../../user/project/pages/custom_domains_ssl_tls_certification/index.md)
- [Project error tracking](../../operations/error_tracking.md)
- [Runner authentication](../../ci/runners/_index.md)
@ -205,7 +205,7 @@ You should verify that the secrets are the root cause before deleting any data.
## Container registry is not restored
If you restore a backup from an environment that uses the [container registry](../../user/packages/container_registry/index.md)
If you restore a backup from an environment that uses the [container registry](../../user/packages/container_registry/_index.md)
to a newly installed environment where the container registry is not enabled, the container registry is not restored.
To also restore the container registry, you need to [enable it](../packages/container_registry.md#enable-the-container-registry) in the new
@ -213,7 +213,7 @@ environment before you restore the backup.
## Container registry push failures after restoring from a backup
If you use the [container registry](../../user/packages/container_registry/index.md),
If you use the [container registry](../../user/packages/container_registry/_index.md),
pushes to the registry may fail after restoring your backup on a Linux package (Omnibus)
instance after restoring the registry data.

4
doc/administration/dedicated/hosted_runners.md
View File

@ -68,9 +68,9 @@ If you use images from the Docker Hub container registry, you might run into [ra
To avoid rate limits, instead use:
- Images stored in the [GitLab container registry](../../user/packages/container_registry/index.md).
- Images stored in the [GitLab container registry](../../user/packages/container_registry/_index.md).
- Images stored in other public registries with no rate limits.
- The [dependency proxy](../../user/packages/dependency_proxy/index.md), acting as a pull-through cache.
- The [dependency proxy](../../user/packages/dependency_proxy/_index.md), acting as a pull-through cache.
### Docker in Docker support

2
doc/administration/geo/replication/datatypes.md
View File

@ -208,7 +208,7 @@ successfully, you must replicate their data using some other means.
| [Alert Metric Images](../../../operations/incident_management/alerts.md#metrics-tab) | **Yes** (15.5) | **Yes** (15.5) | **Yes** (15.5) | [**Yes** (16.4)<sup>3</sup>](https://gitlab.com/groups/gitlab-org/-/epics/8056) | Replication/Verification is handled via the Uploads data type. |
| [Server-side Git hooks](../../server_hooks.md) | [Not planned](https://gitlab.com/groups/gitlab-org/-/epics/1867) | No | Not applicable | Not applicable | Not planned because of current implementation complexity, low customer interest, and availability of alternatives to hooks. |
| [Elasticsearch integration](../../../integration/advanced_search/elasticsearch.md) | [Not planned](https://gitlab.com/gitlab-org/gitlab/-/issues/1186) | No | No | No | Not planned because further product discovery is required and Elasticsearch (ES) clusters can be rebuilt. Secondaries use the same ES cluster as the primary. |
| [Dependency Proxy Images](../../../user/packages/dependency_proxy/index.md) | [**Yes** (15.7)](https://gitlab.com/groups/gitlab-org/-/epics/8833) | [**Yes** (15.7)](https://gitlab.com/groups/gitlab-org/-/epics/8833) | [**Yes** (15.7)](https://gitlab.com/groups/gitlab-org/-/epics/8833) | [**Yes** (16.4)<sup>3</sup>](https://gitlab.com/groups/gitlab-org/-/epics/8056) | |
| [Dependency Proxy Images](../../../user/packages/dependency_proxy/_index.md) | [**Yes** (15.7)](https://gitlab.com/groups/gitlab-org/-/epics/8833) | [**Yes** (15.7)](https://gitlab.com/groups/gitlab-org/-/epics/8833) | [**Yes** (15.7)](https://gitlab.com/groups/gitlab-org/-/epics/8833) | [**Yes** (16.4)<sup>3</sup>](https://gitlab.com/groups/gitlab-org/-/epics/8056) | |
| [Vulnerability Export](../../../user/application_security/vulnerability_report/index.md#export-vulnerability-details) | [Not planned](https://gitlab.com/groups/gitlab-org/-/epics/3111) | No | No | No | Not planned because they are ephemeral and sensitive information. They can be regenerated on demand. |
| Packages NPM metadata cache | [Not planned](https://gitlab.com/gitlab-org/gitlab/-/issues/408278) | No | No | No | Not planned because it would not notably improve disaster recovery capabilities nor response times at secondary sites. |

2
doc/administration/geo/setup/two_single_node_sites.md
View File

@ -570,7 +570,7 @@ You must manually replicate the secret file across all of your secondary sites,
1. Select **Geo > Sites**.
1. Select **Add site**.
![Add secondary site](../replication/img/adding_a_secondary_v15_8.png)
![Form to add a new site with three input fields: Name, External URL, and Internal URL (optional).](../replication/img/adding_a_secondary_v15_8.png)
1. In **Name**, enter the value for `gitlab_rails['geo_node_name']` in
`/etc/gitlab/gitlab.rb`. The values must match exactly.

6
doc/administration/gitaly/concurrency_limiting.md
View File

@ -17,7 +17,7 @@ Enabling limits on your environment should be done with caution and only
in select circumstances, such as to protect against unexpected traffic.
When reached, limits _do_ result in disconnects that negatively impact users.
For consistent and stable performance, you should first explore other options such as
adjusting node specifications, and [reviewing large repositories](../../user/project/repository/monorepos/index.md) or workloads.
adjusting node specifications, and [reviewing large repositories](../../user/project/repository/monorepos/_index.md) or workloads.
## Limit RPC concurrency
@ -29,7 +29,7 @@ When cloning or pulling repositories, various RPCs run in the background. In par
These RPCs can consume a large amount of resources, which can have a significant impact in situations such as:
- Unexpectedly high traffic.
- Running against [large repositories](../../user/project/repository/monorepos/index.md) that don't follow best practices.
- Running against [large repositories](../../user/project/repository/monorepos/_index.md) that don't follow best practices.
You can limit these processes from overwhelming your Gitaly server in these scenarios using the concurrency limits in the Gitaly configuration file. For
example:
@ -93,7 +93,7 @@ number of in-flight pack-object processes per remote IP address.
WARNING:
Only enable these limits on your environment with caution and only in select circumstances, such as to protect against unexpected traffic. When reached, these limits
disconnect users. For consistent and stable performance, you should first explore other options such as adjusting node specifications, and
[reviewing large repositories](../../user/project/repository/monorepos/index.md) or workloads.
[reviewing large repositories](../../user/project/repository/monorepos/_index.md) or workloads.
Example configuration:

2
doc/administration/gitaly/configure_gitaly.md
View File

@ -588,7 +588,7 @@ Enabling limits on your environment should be done with caution and only
in select circumstances, such as to protect against unexpected traffic.
When reached, limits _do_ result in disconnects that negatively impact users.
For consistent and stable performance, you should first explore other options such as
adjusting node specifications, and [reviewing large repositories](../../user/project/repository/monorepos/index.md) or workloads.
adjusting node specifications, and [reviewing large repositories](../../user/project/repository/monorepos/_index.md) or workloads.
When enabling cgroups for memory, you should ensure that no swap is configured on the Gitaly nodes as
processes may switch to using that instead of being terminated. This situation could lead to notably compromised

2
doc/administration/gitaly/kubernetes.md
View File

@ -112,7 +112,7 @@ gitlab:
### Address resource contention and saturation
Gitaly service resource usage can be unpredictable because of the indeterminable nature of Git operations. Not all repositories are the same and size
heavily influences performance and resource usage, especially for [monorepos](../../user/project/repository/monorepos/index.md).
heavily influences performance and resource usage, especially for [monorepos](../../user/project/repository/monorepos/_index.md).
In Kubernetes, uncontrolled resource usage can lead to Out Of Memory (OOM) events, which forces the platform to terminate the pod and kill all its processes.
Pod termination raises two important concerns:

13
doc/administration/gitlab_duo_self_hosted/configure_duo_features.md
View File

@ -120,16 +120,3 @@ Configure the GitLab Duo feature to send queries to the configured self-hosted m
1. Select **Self-hosted models**.
1. Select the **AI-powered features** tab.
1. For the feature you want to configure, from the dropdown list, choose the self-hosted model you want to use. For example, `Mistral`.
### Configure the feature to use GitLab AI Vendor models
Prerequisites:
- You must use an [online license](https://about.gitlab.com/pricing/licensing-faq/cloud-licensing/#what-is-cloud-licensing).
Configure the GitLab Duo feature to send queries to the Cloud Connector and use the GitLab AI Vendor model:
1. On the left sidebar, at the bottom, select **Admin**.
1. Select **Self-hosted models**.
1. Select the **AI-powered features** tab.
1. For the feature you want to configure, from the dropdown list, select **GitLab AI Vendor**.

2
doc/administration/instance_limits.md
View File

@ -1117,7 +1117,7 @@ When asking for versions of a given NuGet package name, the GitLab package regis
## Dependency Proxy Limits
The maximum file size for an image cached in the
[Dependency Proxy](../user/packages/dependency_proxy/index.md)
[Dependency Proxy](../user/packages/dependency_proxy/_index.md)
varies by file type:
- Image blob: 5 GB

2
doc/administration/integration/terminal.md
View File

@ -22,7 +22,7 @@ On GitLab Self-Managed, by default this feature is not available. To make it ava
---
With the introduction of the [Kubernetes integration](../../user/infrastructure/clusters/index.md),
With the introduction of the [Kubernetes integration](../../user/infrastructure/clusters/_index.md),
GitLab can store and use credentials for a Kubernetes cluster.
GitLab uses these credentials to provide access to
[web terminals](../../ci/environments/_index.md#web-terminals-deprecated) for environments.

4
doc/administration/packages/container_registry.md
View File

@ -25,7 +25,7 @@ For more details about the Distribution Registry:
- [Deploy a registry server](https://distribution.github.io/distribution/about/deploying/)
This document is the administrator's guide. To learn how to use the GitLab Container
Registry, see the [user documentation](../../user/packages/container_registry/index.md).
Registry, see the [user documentation](../../user/packages/container_registry/_index.md).
## Enable the container registry
@ -851,7 +851,7 @@ auth:
Without these entries, the registry logins cannot authenticate with GitLab.
GitLab also remains unaware of
[nested image names](../../user/packages/container_registry/index.md#naming-convention-for-your-container-images)
[nested image names](../../user/packages/container_registry/_index.md#naming-convention-for-your-container-images)
under the project hierarchy, like
`registry.example.com/group/project/image-name:tag` or
`registry.example.com/group/project/my/image-name:tag`, and only recognizes

2
doc/administration/packages/dependency_proxy.md
View File

@ -15,7 +15,7 @@ DETAILS:
GitLab can be used as a dependency proxy for your frequently-accessed upstream images.
This is the administration documentation. If you want to learn how to use the
dependency proxies, see the [user guide](../../user/packages/dependency_proxy/index.md).
dependency proxies, see the [user guide](../../user/packages/dependency_proxy/_index.md).
The GitLab Dependency Proxy:

10
doc/administration/reference_architectures/_index.md
View File

@ -341,7 +341,7 @@ See [Recommended cloud providers and services](#recommended-cloud-providers-and-
The architectures were tested with repositories of varying sizes that follow best practices.
**However, [large monorepos](../../user/project/repository/monorepos/index.md) (several gigabytes or more) can significantly impact the performance of Git and in turn the environment itself.**
**However, [large monorepos](../../user/project/repository/monorepos/_index.md) (several gigabytes or more) can significantly impact the performance of Git and in turn the environment itself.**
Their presence and how they are used can put a significant strain on the entire system from Gitaly to the underlying infrastructure.
The performance implications are largely software in nature. Additional hardware resources lead to diminishing returns.
@ -352,12 +352,12 @@ If this applies to you, we strongly recommend you follow the linked documentatio
Large monorepos come with notable cost. If you have such a repository,
follow these guidance to ensure good performance and to keep costs in check:
- [Optimize the large monorepo](../../user/project/repository/monorepos/index.md#optimize-gitlab-settings). Using features such as
[LFS](../../user/project/repository/monorepos/index.md#use-lfs-for-large-blobs) to not store binaries, and other approaches for reducing repository size, can
- [Optimize the large monorepo](../../user/project/repository/monorepos/_index.md#optimize-gitlab-settings). Using features such as
[LFS](../../user/project/repository/monorepos/_index.md#use-lfs-for-large-blobs) to not store binaries, and other approaches for reducing repository size, can
dramatically improve performance and reduce costs.
- Depending on the monorepo, increased environment specifications may be required to compensate. Gitaly might require additional resources along with Praefect, GitLab Rails, and Load Balancers. This depends on the monorepo itself and its usage.
- When the monorepo is significantly large (20 gigabytes or more), further additional strategies may be required such as even further increased specifications or in some cases, a separate Gitaly backend for the monorepo alone.
- Network and disk bandwidth is another potential consideration with large monorepos. In very heavy cases, bandwidth saturation is possible if there's a high amount of concurrent clones (such as with CI). [Reduce full clones wherever possible](../../user/project/repository/monorepos/index.md#reduce-concurrent-clones-in-cicd) in this scenario. Otherwise, additional environment specifications may be required to increase bandwidth. This differs based on cloud providers.
- Network and disk bandwidth is another potential consideration with large monorepos. In very heavy cases, bandwidth saturation is possible if there's a high amount of concurrent clones (such as with CI). [Reduce full clones wherever possible](../../user/project/repository/monorepos/_index.md#reduce-concurrent-clones-in-cicd) in this scenario. Otherwise, additional environment specifications may be required to increase bandwidth. This differs based on cloud providers.
### Additional workloads
@ -368,7 +368,7 @@ However, additional workloads can multiply the impact of operations by triggerin
You may need to adjust the suggested specifications to compensate if you use:
- Security software on the nodes.
- Hundreds of concurrent CI jobs for [large repositories](../../user/project/repository/monorepos/index.md).
- Hundreds of concurrent CI jobs for [large repositories](../../user/project/repository/monorepos/_index.md).
- Custom scripts that [run at high frequency](../logs/log_parsing.md#print-top-api-user-agents).
- [Integrations](../../integration/_index.md) in many large projects.
- [Server hooks](../server_hooks.md).

2
doc/administration/terraform_state.md
View File

@ -9,7 +9,7 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab Self-Managed
GitLab can be used as a backend for [Terraform](../user/infrastructure/index.md) state
GitLab can be used as a backend for [Terraform](../user/infrastructure/_index.md) state
files. The files are encrypted before being stored. This feature is enabled by default.
The storage location of these files defaults to:

2
doc/api/bulk_imports.md
View File

@ -46,7 +46,7 @@ POST /bulk_imports
| `entities[source_full_path]` | String | yes | Source full path of the entity to import. For example, `gitlab-org/gitlab`. |
| `entities[destination_slug]` | String | yes | Destination slug for the entity. GitLab uses the slug as the URL path to the entity. The name of the imported entity is copied from the name of the source entity and not the slug. |
| `entities[destination_name]` | String | no | Deprecated: Use `destination_slug` instead. Destination slug for the entity. |
| `entities[destination_namespace]` | String | yes | Full path of the destination group [namespace](../user/namespace/index.md) for the entity. Must be an existing group in the destination instance. |
| `entities[destination_namespace]` | String | yes | Full path of the destination group [namespace](../user/namespace/_index.md) for the entity. Must be an existing group in the destination instance. |
| `entities[migrate_projects]` | Boolean | no | Also import all nested projects of the group (if `source_type` is `group_entity`). Defaults to `true`. |
| `entities[migrate_memberships]` | Boolean | no | Import user memberships. Defaults to `true`. |

4
doc/api/container_registry.md
View File

@ -9,7 +9,7 @@ DETAILS:
**Tier:** Free, Premium, Ultimate
**Offering:** GitLab.com, GitLab Self-Managed, GitLab Dedicated
Use these API endpoints to work with the [GitLab container registry](../user/packages/container_registry/index.md).
Use these API endpoints to work with the [GitLab container registry](../user/packages/container_registry/_index.md).
You can authenticate with these endpoints from a CI/CD job by passing the [`$CI_JOB_TOKEN`](../ci/jobs/ci_job_token.md)
variable as the `JOB-TOKEN` header. The job token only has access to the container registry
@ -38,7 +38,7 @@ Descriptions of the possible values for `container_registry_access_level`:
to **enabled**.
- **disabled**: The container registry is disabled.
See the [container registry visibility permissions](../user/packages/container_registry/index.md#container-registry-visibility-permissions)
See the [container registry visibility permissions](../user/packages/container_registry/_index.md#container-registry-visibility-permissions)
for more details about the permissions that this setting grants to users.
```shell

Some files were not shown because too many files have changed in this diff Show More