- Announced in 15.1
- Announced in 15.0
- Announced in 14.10
-
Announced in 14.9
- Background upload for object storage
- Deprecate support for Debian 9
- GitLab Pages running as daemon
- GitLab self-monitoring project
- GraphQL permissions change for Package settings
- Move
custom_hooks_dirsetting from GitLab Shell to Gitaly - Permissions change for downloading Composer dependencies
- htpasswd Authentication for the Container Registry
- user_email_lookup_limit API field
-
Announced in 14.8
- Configurable Gitaly
per_repositoryelection strategy - Container Network and Host Security
- Dependency Scanning Python 3.9 and 3.6 image deprecation
- Deprecate Geo Admin UI Routes
- Deprecate custom Geo:db:* Rake tasks
- Deprecate feature flag PUSH_RULES_SUPERSEDE_CODE_OWNERS
- Deprecate legacy Gitaly configuration methods
- Elasticsearch 6.8
- External status check API breaking changes
- GraphQL ID and GlobalID compatibility
- OAuth tokens without expiration
- Optional enforcement of PAT expiration
- Optional enforcement of SSH expiration
- Out-of-the-box SAST support for Java 8
- Querying Usage Trends via the
instanceStatisticsMeasurementsGraphQL node - REST API Runner will not accept
statusfilter values ofactiveorpaused - REST API endpoint to list group runners no longer accepts
project_typevalue fortypeargument - REST and GraphQL API Runner usage of
activereplaced bypaused - Request profiling
- Required pipeline configurations in Premium tier
- Retire-JS Dependency Scanning tool
- SAST analyzer consolidation and CI/CD template changes
- SAST support for .NET 2.1
- Secret Detection configuration variables deprecated
- Secure and Protect analyzer images published in new location
- Secure and Protect analyzer major version update
- Support for gRPC-aware proxy deployed between Gitaly and rest of GitLab
- Test coverage project CI/CD setting
- Vulnerability Check
CI_BUILD_*predefined variablesprojectFingerprintinPipelineSecurityReportFindingGraphQLstartediterations API field
- Configurable Gitaly
-
Announced in 14.7
- Container scanning schemas below 14.0.0
- Coverage guided fuzzing schemas below 14.0.0
- DAST schemas below 14.0.0
- Dependency scanning schemas below 14.0.0
- Enforced validation of security report schemas
- Godep support in License Compliance
- Logging in GitLab
- Monitor performance metrics through Prometheus
- Pseudonymizer
- SAST schemas below 14.0.0
- Secret detection schemas below 14.0.0
- Sidekiq metrics and health checks configuration
- Static Site Editor
- Tracing in GitLab
artifacts:reports:coberturakeyword- merged_by API field
- Announced in 14.6
-
Announced in 14.5
- Changing an instance (shared) runner to a project (specific) runner
- Known host required for GitLab Runner SSH executor
- Package pipelines in API payload is paginated
- REST and GraphQL API Runner status will not return
paused - SaaS certificate-based integration with Kubernetes
- Self-managed certificate-based integration with Kubernetes
- Support for SLES 12 SP2
- Update to the Container Registry group-level API
- Value Stream Analytics filtering calculation change
Versionson basePackageTypedefaultMergeCommitMessageWithDescriptionGraphQL API fielddependency_proxy_for_private_groupsfeature flagpipelinesfield from theversionfieldpromote-dbcommand fromgitlab-ctlpromote-to-primary-nodecommand fromgitlab-ctl- openSUSE Leap 15.2 packages
- Announced in 14.3
- Announced in 14.2
- Announced in 14.0
Deprecations by version
In each release, GitLab announces features that are deprecated and no longer recommended for use. Each deprecated feature will be removed in a future release. Some features cause breaking changes when they are removed.
This page contains information related to upcoming products, features, and functionality.
It is important to note that the information presented is for informational purposes only.
Please do not rely on this information for purchasing or planning purposes.
As with all projects, the items mentioned on this page are subject to change or delay.
The development, release, and timing of any products, features, or functionality remain at the
sole discretion of GitLab Inc.
Announced in 15.1
Jira GitHub Enterprise DVCS integration
Planned removal: GitLab 16.0 (2023-05-22)
This is a breaking change.
Review the details carefully before upgrading.
The Jira DVCS Connector (which enables the Jira Development Panel), will no longer support Jira Cloud users starting with GitLab 16.0. The GitLab for Jira App has always been recommended for Jira Cloud users, and it will be required instead of the DVCS connector. If you are a Jira Cloud user, we recommended you begin migrating to the GitLab for Jira App. Any Jira Server and Jira Data Center users will need to confirm they are not using the GitHub Enterprise Connector to enable the GitLab DVCS integration, but they may continue to use the native GitLab DVCS integration (supported in Jira 8.14 and later).