Comprehensive list of items that failed to be imported
Previously, when migrating GitLab projects and groups by direct transfer had completed and some items (such as a merge requests or issues) were not
successfully imported, you could select a Details button on the
page listing imported groups and projects and see related errors there.
However, a list of errors is not helpful to understand how many items in total, and which items in particular, were not imported. Having this
information is crucial to understanding the results of the import process.
In this release, we replaced the Details button with a See failures link. Selecting the See failures link takes you to a new page listing all items that failed
to import for a given group or project. For each item that wasn’t imported, you can see:
- The type of the item. For example, merge request or issue.
- What kind of error occurred.
- The correlation ID, which is useful for debugging purposes.
- The URL of the item on the source instance, if available (items with
- The title of the item on the source instance, if available. For example, the merge request title or the issue title.
GitLab Runner 16.6
We’re also releasing GitLab Runner 16.6 today! GitLab Runner is the lightweight, highly-scalable agent that runs your CI/CD jobs and sends the results back to a GitLab instance. GitLab Runner works in conjunction with GitLab CI/CD, the open-source continuous integration service included with GitLab.
The list of all changes is in the GitLab Runner CHANGELOG.
Upload packages to the Maven repository with basic HTTP authentication
The GitLab Package Registry now supports uploading Maven packages with basic HTTP authentication. Previously, you could use basic HTTP authentication only to download Maven packages. This inconsistency made it difficult for developers to configure and maintain authentication for their project.
Publishing artifacts with
sbt is not supported, but issue 408479 proposes to add this feature.
Container Scanning: Exclude findings which won't be fixed
Container scanning results may include findings which the vendor has evaluated and decided to not fix. To allow
you to focus on actionable findings, you can now exclude such findings. For configuration options please refer to the GitLab documentation.
Include CVSS Vectors in the vulnerability report export
When you export information from the vulnerability report, the CVSS Vector information is now included.
This additional data helps you analyze and triage vulnerabilities outside GitLab.
Previously, the vulnerability report allowed you to filter by a static list of GitLab-supported tool types, followed by a dynamic list of custom scanners. With this release, you can now select tool type grouped by analyzer.
GitLab Silent Mode
When GitLab Silent Mode is enabled, it blocks all major outbound traffic such as notification emails, integrations, webhooks, and mirroring from a GitLab instance. This allows you to perform testing against a GitLab site without generating traffic towards users and other integrations. You can use Silent Mode to test a restored backup or a promoted Geo DR site without impacting your primary GitLab site or your end users.
Hide archived projects in search results by default
Previously, users saw many archived projects in their project search results. This was problematic, especially when archived projects took up many of the top results. We now filter out archived projects by default, and users can select Include archived to see all projects.
Previously, the names of private groups were visible to all users when accessing the Groups tab of a project’s or group’s members page. To enhance security, we are now masking private groups’ name and source from users who are not members of the shared group, shared project, or invited group. Instead, this information will be displayed as Private.
Service accounts have optional expiry dates
GitLab administrators and group Owners can choose if they want to enforce an expiry date for service accounts. Previously, service account tokens had to expire within a year, in line with personal, project, and group access token expiration limits. This allows administrators and group Owners to choose the balance between security and ease of use that best aligns with their goals.
Consistent navigation experience for all users
The 16.0 release introduced a new navigation experience, which became the default for all users on June 2, 2023. In subsequent milestones, many improvements were made based on a wealth of user feedback. The ability to fall back to the old navigation has now been removed. More exciting changes are planned for the navigation, but for now, all users have a consistent navigation experience.
As a recap, with the new GitLab navigation, you can:
- Pin menu items to save your most-used project or group items at the top
- Hide and “peek” the navigation to expose a wider screen
- Easily search for menu items by using keyboard shortcuts
- Continue to use all the themes you had with the previous navigation
- Use better-organized sections that align with a DevOps workflow
Prevent duplicate NuGet packages
You can use the GitLab Package Registry to publish and download your project’s NuGet packages. By default, you can publish the same package name and version multiple times.
However, you might want to prevent duplicate uploads, especially for releases. In this release, GitLab has expanded the group setting for the Package Registry so you can allow or deny duplicate package uploads.
You can adjust this setting with the GitLab API, or from the UI.
Added support for SBT projects using Java 21
Dependency Scanning and License Scanning now support SBT projects using Java 21.
DAST analyzer updates
During the 16.6 release milestone, we enabled the following active checks for browser-based DAST by default:
- Check 94.1 replaces ZAP check 90019 and identifies server-side code injection (PHP).
- Check 94.2 replaces ZAP check 90019 and identifies server-side code injection (Ruby).
- Check 94.3 replaces ZAP check 90019 and identifies server-side code injection (Python).
- Check 943.1 replaces ZAP check 40033 and identifies improper neutralization of special elements in data query logic.
- Check 74.1 replaces ZAP check 90017 and identifies XSLT injection.
Allow compliance teams to prevent pushing and force pushing into protected branches
One of several new settings being added to scan result policies to aide in compliance enforcement of security policies, this control will limit the ability to leverage project-level settings to circumvent policies.
For each existing or new scan result policy, you can enable
Prevent pushing and force pushing to take effect for the branches defined within the policy to prevent users from circumventing the merge request flow to push changes directly to a branch.
Available in SaaS in 16.6. Available for Self-managed behind the feature flag
scan_result_policies_block_force_push and will be enabled by default in 16.7.
Connect to Kubernetes clusters with the GitLab CLI
From GitLab version 16.4, you can connect to a Kubernetes cluster from a local terminal using the agent for Kubernetes and a personal access token. In the initial version, setting up the local cluster configuration required several commands and a long lived access token. In the past month, we worked to streamline and improve the security of the set up process by extending the GitLab CLI.
The GitLab CLI can now list the agent connections available from a GitLab project checkout directory or the specified project. You can set up the connection through a selected agent with a dedicated command. When
kubectl or any other tool needs to authenticate with the cluster, the GitLab CLI generates a temporary, restricted token for the signed-in user.
Group-level audit event streaming to AWS S3
Building on our integrations with external logging or data aggregation tools, you can now select AWS S3 as a destination for audit event streams
for top-level groups. This feature provides relevant information for an easier and more trouble-free integration.
Previously, you had to use custom HTTP headers to try to build a request that AWS S3 would accept. This method was prone to errors and could be difficult to troubleshoot.
Improved handling of unresponsive external status checks
Previously, external status checks on MRs continued to poll the external URL until they received either a successful or failed response.
This could result in some status checks seeming to hang in an unresponsive state.
Now, a 2 minute timeout has been incorporated so that you can manually retry the status check after 2 minutes if you are not getting any
response from the external system.
Real-time Kubernetes status updates in the GitLab UI
In GitLab 16.6, you can use the cluster UI integration on your environment page to determine the status of currently running applications without leaving GitLab. Previously, the status was updated by a one-time request when the UI loaded, which made tracking deployment progress unwieldy. The current version of GitLab upgrades the underlying connection to use the Kubernetes watch API for the Flux reconciliation and Pod statuses, and provides near real-time updates of the cluster state in the GitLab UI.