GitLab 17.11 release notes | GitLab Docs
/ GitLab 17.11 release notes On April 17, 2025, GitLab 17.11 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor. This month’s Notable Contributor: Heidi Berry For 17.11, we’re delighted to recognize Heidi Berry as our Notable Contributor! Heidi has been a standout contributor to the GitLab Terraform Provider and client-go projects.
Over the past several releases, she has consistently delivered highly requested features including the ability to use custom roles with Group SAML links , support for setting branch protection defaults for group , and automatic token rotation for service account tokens . Beyond feature development, Heidi has been instrumental in maintenance activities - helping with issue backlog refinement , updating older tests for improved readability , and enhancing documentation with better examples .
Her contributions to client-go are particularly valuable as this library powers many downstream projects that both customers and GitLab use to interact with GitLab, including the Terraform provider and glab. “If you have ever wanted to try your hand at open source contributing, try out client-go and terraform-provider-GitLab,� says Heidi. “They have great documentation to get you started, and supportive maintainers ready to help.
I have enjoyed using these projects to learn the go language in a practical way.� Heidi was nominated by another community contributor, Patrick Rice , who is an Enterprise Architect at Kingland and member of the GitLab community Core Team. Patrick says: “With over 100 merged contributions so far across the 17 release cycle and more issue comments, Heidi has been a great help to GitLab and Terraform. Thank you so much for your contributions!� “Heidi does phenomenal work,� said Timo Furrer , Senior Backend Engineer in Deploy::Environments at GitLab. “She regularly goes the extra mile and implements the necessary SDK code in client-go.
Heidi not only contributes a lot of code, but also helps with issue triaging. It’s an immense help and it’s the reason community-driven projects like these can sustain.� Heidi is a Lead Software Engineer at The Co-operative Group, where she helps make developer experience efficient, secure and as effortless as possible. Thank you, Heidi, for your tremendous contributions to GitLab! Primary features Customize compliance frameworks with requirements and compliance controls Tier : Ultimate Offering : GitLab.com, GitLab Self-Managed Links : Documentation Previously, compliance frameworks in GitLab could be created as a label to identify that your project has certain compliance requirements or needs additional oversight.
This label could then be used as a scoping mechanism to ensure that security policies could be enforced on all projects within a group. In this release, we are introducing a new way for compliance managers to get more in-depth compliance monitoring in GitLab through ‘requirements’. With requirements, as part of a custom compliance framework, you can define specific requirements from a number of different compliance standards, laws, and regulations that must be followed as an organization.
We are also expanding the number of compliance controls (previously known as compliance checks) that we offer from five to over 50! These 50 out-of-the-box (OOTB) controls can be mapped to the compliance framework requirements. These controls check particular project, security, and merge request settings across your GitLab instance to help you meet requirements under a number of different compliance standards, laws, and regulations such as SOC2, NIST, ISO 27001, and the GitLab CIS Benchmark.
Adherence to these controls is reflected in standard adherence report, which is redesigned to take into account requirements and the mapping of controls to those requirements. In addition to expanding our OOTB controls, we now allow users to map requirements to external controls, which can be for items, programs, or systems that exist outside the GitLab platform. These mappings allow you to use the GitLab compliance centre as the single source of truth when it comes to your compliance monitoring and audit evidence needs.
GitLab Eclipse plugin available in beta Tier : Premium, Ultimate Offering : GitLab.com, GitLab Self-Managed Add-ons : Duo Pro, Duo Enterprise Links : Documentation | Related epic We’re thrilled to announce the beta release of the GitLab Eclipse plugin, now available in the Eclipse Marketplace . This powerful new plugin extends GitLab’s Duo features directly into your Eclipse IDE, giving you seamless access to Duo Chat and AI-powered code suggestions.
As the plugin is currently in beta, we’re actively improving features, including expanding authentication options, and refining the final user experience. Your feedback is invaluable. Please share your thoughts to help us make the GitLab Eclipse plugin even better by adding your feedback in issue 162 . More GitLab Duo features now available on GitLab Duo Self-Hosted Tier : Ultimate Offering : GitLab Self-Managed Add-ons : Duo Enterprise Links : Documentation | Related epic You can now use more GitLab Duo features with GitLab Duo Self-Hosted in your GitLab Self-Managed instance.
The following features are available in beta: Root Cause Analysis Vulnerability Explanation Vulnerability Resolution AI Impact Dashboard Discussion Summary Merge Request Commit Message Merge Request Summary GitLab Duo for the CLI Code Review Summary is also available on GitLab Duo Self-Hosted as an experiment. Extension marketplace for Web IDE on self-managed instances Tier : Free, Premium, Ultimate Offering : GitLab.com, GitLab Self-Managed Links : Documentation We’re thrilled to announce the launch of the extension marketplace in the Web IDE for self-managed users.
With the extension marketplace, you can discover, install, and manage third-party extensions to enhance your development experience. By default, the GitLab instance is configured to use the Open VSX extension registry. To activate this, follow the enable with default extension registry steps. If you want to use your own or custom registry, you also have the option to connect a custom extension registry . This provides you with more flexibility to manage available extensions.
After enabling the extension marketplace, individual users must still opt in to use it. They can do this by going to the Integrations section in their Preferences settings. It’s important to note that some extensions require a local runtime environment and are not compatible with the web-only version. Despite this, you can still choose from thousands of available extensions to boost your productivity and customize your workflow.
GitLab Duo with Amazon Q is generally available Tier : Ultimate Offering : GitLab Self-Managed Links : Documentation | Related epic We’re excited to announce general availability for GitLab Duo with Amazon Q, a joint offering that brings together the comprehensive GitLab AI-powered DevSecOps platform with autonomous Amazon Q AI agents in a single, integrated solution. GitLab Duo with Amazon Q integrates AI agents directly into development workflows, allowing developers to accelerate key tasks without switching tools.
Acting as intelligent assistants within the GitLab DevSecOps platform, these agents automate time-consuming processes like code generation, testing, reviews, and Java modernization, helping teams focus on innovation while maintaining security and quality standards. GitLab Duo with Amazon Q provides major benefits for development teams: Streamline feature development from idea to code: use /q dev , which will convert an issue description directly into merge-ready code in minutes.
Modernize legacy code without the headache: use /q transform to automate the en
The rest of this page is on the live site.