Oct 5, 2024
Available now on GitLab

The latest features available on GitLab SaaS

New features are regularly released to GitLab SaaS (GitLab.com), with a packaged release available for GitLab Self-Managed every month. Read on to learn more about the new features available on GitLab.com. Note that it may take a few days for a feature to become fully available on GitLab.com, due to deployment schedule and potential feature flags.

Additional information on past releases is available; be sure to check out the release for other features we've launched recently. We also have information about upcoming releases if you're interested in seeing what we are doing next.

Preview Key improvements released in GitLab Preview

Enhanced branch rules editing capabilities

Enhanced branch rules editing capabilities

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

In GitLab 15.10, we introduced a consolidated view for branch-related settings and rules.This view provided you with an easy way to understand the configuration of your project across multiple settings.

Building on this feature, you can now directly modify specific branch rules in this view, including branch protections, approval rules, and external status checks configuration. These new capabilities lay the foundation for continued improvements in branch configuration that will allow for greater flexibility in the future.

We encourage you to explore these new capabilities and to provide feedback. You can do this by contributing to our dedicated feedback issue.

Documentation Epic

Preview Other improvements in GitLab Preview

Continuous Vulnerability Scanning on SBOM Changes

Continuous Vulnerability Scanning on SBOM Changes

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

Continuous Vulnerability Scanning includes a trigger for when SBOM changes are detected.

This allows our scanners to provide more timely vulnerability detection in cases when the version of a package is changed or a new package is added. In both of these instances we would trigger Continuous Vulnerability Scanning to identify vulnerabilities associated with the SBOM changes.

We welcome feedback about this feature in this issue: https://gitlab.com/gitlab-org/gitlab/-/issues/482729.

Documentation Issue

Disable password authentication for enterprise users

Disable password authentication for enterprise users

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

Enterprise users can authenticate using a local account with username and password. Now, group Owners can disable password authentication for the group’s enterprise users. If password authentication is disabled, enterprise users can use either the group’s SAML identity provider to authenticate with GitLab web UI, or a personal access token to authenticate with GitLab API and Git using HTTP Basic Authentication.

Documentation Issue

View token associations using API

View token associations using API

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

You can now view which groups, subgroups, and projects a token is associated with. This makes it easier to determine the impact of token expirations or revocations, and to understand where a token is able to be used.

Documentation Issue

Dependency Scanning support for Swift

Dependency Scanning support for Swift

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

Users of Dependency Scanning can now scan projects that are built using Swift. To configure Swift scanning, use the CI/CD Catalog component for either SwiftPM or CocoaPods based projects. Swift scanning is also supported for users of the CI/CD template.

Documentation Issue

Migration process for compliance pipelines to security policies

Migration process for compliance pipelines to security policies

stage-badge
SaaS
Free
Premium
Ultimate
Self-Managed
Free
Premium
Ultimate

In GitLab 17.3, we announced the deprecation of compliance pipelines and its eventual removal by the 18.0 release. Instead of compliance pipelines, you should use the pipeline execution policy type instead, which was released in GitLab 17.2.

To help you migrate your existing compliance pipelines over to the pipeline execution policy type, this release includes a warning banner that:

  • Notifies users about the deprecation of compliance pipelines.
  • Provides a prompted and guided workflow to migrate existing compliance pipelines to the pipeline execution policy type.
Documentation Issue

Deprecations Deprecations

The complete list of all features that are currently deprecated can be viewed in the GitLab documentation. To be notified of upcoming breaking changes, subscribe to our Breaking Changes RSS feed.

Removals and breaking changes Removals and breaking changes

The complete list of all removed features can be viewed in the GitLab documentation. To be notified of upcoming breaking changes, subscribe to our Breaking Changes RSS feed.

Changelog

Please check out the changelog to see all the named changes:

Installing

If you are setting up a new GitLab installation please see the download GitLab page.

Updating

Check out our update page.

GitLab Subscription Plans

See what your team could do with The DevSecOps Platform.

  • Free

    Free-forever features for individual users

  • Premium

    Enhance team productivity and coordination

  • Ultimate

    Organization wide security, compliance, and planning

Try all GitLab features - free for 30 days

Take GitLab for a spin

See what your team could do with The DevSecOps Platform.

Get free trial

Have a question? We're here to help.

Talk to an expert
Edit this page View source