gitlab-org/gitlab-foss v18.7.0

on GitLab

Heading anchor links now announce with the same text as their corresponding heading, improving the experience for
screen reader users. The links also appear after the heading text, providing a cleaner visual presentation.

These changes make it easier for all users to understand and navigate to specific sections of documentation,
issues, and other content.

You can set up your CI/CD pipelines to make use of dynamic input selection when creating new pipelines through the
intuitive web interface.

Now, with dynamic input options, you can configure your pipelines so that input selection options update dynamically
based on previous selections. For example, when you select an input in one dropdown list, it automatically populates
a list of related input options in a second dropdown list.

With CI/CD inputs, you can:

• Trigger pipelines with pre-configured inputs, reducing errors and streamlining deployments.
  
• Enable your users to select different inputs than the defaults from dropdown menus.
  
• Now have cascading dropdown lists where options dynamically update based on previous selections.
  

This dynamic capability enables you to create more intelligent, context-aware input configurations that guide you
through the pipeline creation process, reducing errors and ensuring only valid combinations of inputs are selected.

We're also releasing GitLab Runner 18.7 today!

GitLab Runner is the highly-scalable build 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.

What's New:

• Configurable taskscaler reservation throttling
  
• Enable FF_TIMESTAMPS by default
  

Bug Fixes:

• Shell executor fails on existing Git repository if a relative builds_dir is specified
  
• Authentication failure in GitLab Runner 18.6.0 on subsequent pipeline runs (SSH executor)
  
• Authentication failure in GitLab Runner 18.6.0 on subsequent pipeline runs (shell executor)
  
• Docker 29 API compatibility issues
  
• Variables that reference file variables no longer work in GitLab Runner 18.6.0 with the shell executor
  
• GitLab Runner now supports Windows 11 2025 (25H2)
  
• ECR credential helper is not working with the Docker Autoscaler executor
  
• Job timeouts now properly enforced in GitLab Runner
  

The list of all changes is in the GitLab Runner CHANGELOG.

Teams using parent-child CI/CD pipelines previously had to navigate through multiple pipeline pages to check test
results, code quality reports, and infrastructure changes, disrupting their merge request review workflow.

You can now view and download all reports in a unified view, including unit tests, code quality checks, Terraform
plans, and custom metrics, without leaving the merge request.

This eliminates context switching and accelerates merge request velocity, giving teams the ability to deliver
features faster without compromising quality.