GitLab 17.2 release notes | GitLab Docs
/ GitLab 17.2 release notes On July 18, 2024, GitLab 17.2 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: Phawin Khongkhasawan Everyone can nominate GitLab’s community contributors ! Show your support for our active candidates or add a new nomination! 🙌 Phawin Khongkhasawan is a Tech Lead at Jitta and started contributing to GitLab in February of 2024.
In just a few months, Phawin has merged over 20 contributions and his contributions have also been featured in 16.11 , 17.0 , and 17.1 . Phawin was first nominated by Magdalena Frankiewicz , Product Manager at GitLab, for improving Webhook related features like the request to Allow triggering of project test webhooks via the API . GitLab engineers Marc Shaw and Jose Ivan Vargas , and GitLab Product Manager Rutvik Shah , highlighted Phawin’s patience in collaboration and iteration, two of GitLab’s core values . “I really appreciate Phawin’s work, patience and perseverance on pushing the feature to Add order by merged_at to the finish line,� says Patrick Bajao , Staff Backend Engineer at GitLab. “It took a couple of milestones before it got merged and deployed, but he didn’t stop and he continued to collaborate with us.� A big thank you to Phawin for showing how new contributors can make an immediate impact and help co-create GitLab.
Primary features Log streaming for Kubernetes pods and containers Tier : Free, Premium, Ultimate Offering : GitLab.com, GitLab Self-Managed Links : Documentation | Related epic In GitLab 16.1, we introduced the Kubernetes pod list and detail views. However, you still had to use third-party tools for an in-depth analysis of your workloads. GitLab now ships with a log streaming view for pods and containers, so you can quickly check and troubleshoot issues across your environments without leaving your application delivery tool.
GitLab Duo disabling input and output logging by default. Tier : Free, Premium, Ultimate Offering : GitLab.com, GitLab Self-Managed Add-ons : GitLab Duo Pro, GitLab Duo Enterprise Links : Documentation | Related epic GitLab is now disabling AI input and output logging for GitLab Duo by default. At GitLab, we aim to ensure that customers have sovereignty over their data. We’ve now disabled input and output logging by default and will only log inputs and outputs with customers’ explicit consent via a GitLab Support ticket.
Block a merge request by requesting changes Tier : Premium, Ultimate Offering : GitLab.com, GitLab Self-Managed Links : Documentation When you perform a review, you can complete it by choosing whether to approve , comment , or request changes ( released in GitLab 16.9 ). While reviewing, you might find changes that should prevent a merge request from merging until they’re resolved, and so you complete your review with request changes .
When requesting changes, GitLab now adds a merge check that prevents merging until the request for changes has been resolved. The request for changes can be resolved when the original user who requested changes re-reviews the merge request and subsequently approves the merge request. If the user who originally requested changes is unable to approve, the request for changes can be Bypassed by anyone with merge permissions, so development can continue.
Leave us feedback about this new feature in issue 455339 . Vulnerability Explanation Tier : Ultimate Offering : GitLab.com, GitLab Self-Managed Add-ons : Duo Enterprise Links : Documentation | Related epic Vulnerability Explanation is now a part of GitLab Duo Chat and is generally available. With Vulnerability Explanation, you can open chat from any SAST vulnerability to better understand the vulnerability, see how it could be exploited, and review a potential fix.
OAuth 2.0 device authorization grant support Tier : Free, Premium, Ultimate Offering : GitLab.com, GitLab Self-Managed Links : Documentation | Related issue GitLab now supports the OAuth 2.0 device authorization grant flow . This flow makes it possible to securely authenticate your GitLab identity from input constrained devices where browser interactions are not an option. This makes the device authorization grant flow ideal for users attempting to use GitLab services from headless servers or other devices with no, or limited, UI.
Thank you John Parent for your contribution! Pipeline execution policy type Tier : Ultimate Offering : GitLab.com, GitLab Self-Managed Links : Documentation | Related epic The pipeline execution policy type is a new type of security policy that allows users to support enforcement of generic CI jobs, scripts, and instructions. The pipeline execution policy type enables security and compliance teams to enforce customized GitLab security scanning templates , GitLab or partner-supported CI templates , 3rd party security scanning templates, custom reporting rules through CI jobs, or custom scripts/rules through GitLab CI.
The pipeline execution policy has two modes: inject and override. The inject mode injects jobs into the project’s CI/CD pipeline. The override mode replaces the project’s CI/CD pipeline configuration. As with all GitLab policies, enforcement can be managed centrally by designated security and compliance team members who create and manage the policies. Learn how to get started by creating your first pipeline execution policy !
Expanded support of custom rulesets in pipeline secret detection Tier : Ultimate Offering : GitLab.com, GitLab Self-Managed Links : Documentation | Related issue We have expanded support of custom rulesets in pipeline secret detection. You can use two new types of passthroughs, git and url , to configure remote rulesets. This makes it easier to manage workflows such as sharing ruleset configurations across multiple projects.
You can also extend the default configuration with a remote ruleset by using one of those new types of passthroughs. The analyzer also now supports: Chaining up to 20 passthroughs into a single configuration to replace predefined rules. Including environment variables in passthroughs. Setting a timeout when loading a passthrough. Validating TOML syntax in ruleset configuration. GitLab Duo Chat and Code Suggestions available in workspaces Tier : Premium, Ultimate Offering : GitLab.com, GitLab Self-Managed Add-ons : Duo Pro, Duo Enterprise Links : Documentation GitLab Duo Chat and Code Suggestions are now available in workspaces!
Whether you’re seeking quick answers or efficient code improvements, Duo Chat and Code Suggestions are designed to boost productivity and streamline your workflow, making remote development in workspaces more efficient and effective than ever. Scale and Deployments Improved sorting and filtering in group overview Tier : Free, Premium, Ultimate Offering : GitLab.com, GitLab Self-Managed Links : Documentation | Related issue We have updated the sorting and filtering functionality of the group overview page.
The search element now stretches across the whole page, allowing you to see your search strings better. We have standardized the sorting options to Name , Created date , Updated date , and Stars . We welcome feedback about these changes in issue 438322 . List groups that a group was invited to using the Groups API Tier : Free, Premium, Ultimate Offering : GitLab.com, GitLab Self-Managed Links : Documentation | Related issue We added a new endpoint to the Groups API to list the groups a group has been invited to.
This functionality complements the endpoint to list the projects that a group has been invited to , so you can now get a complete overview of all the groups and projects that your group has been added to. The endpoint is rate-limited to 60 requests per minute per user. Thank you @imskr for this community contribution! Resolve to-do items, on
The rest of this page is on the live site.