Help us learn about your current experience with the documentation. Take the survey.

Agentic breaking change resolution

  • Tier: Ultimate
  • Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
  • Status: Beta

Agentic breaking change resolution is a foundational flow that:

  • Analyzes failed pipelines on merge requests that bump dependencies.
  • Generates fixes to resolve breaking changes introduced by the dependency update.

When this feature is turned on, pipeline logs and code context from the affected merge request are sent to large language models (LLMs) for analysis. Review your organization’s data policies before you turn on this feature.

In this foundational flow, GitLab Duo:

  • Examines pipeline error logs to identify the root cause of the failure.
  • Analyzes dependency changelogs and release notes to identify breaking changes.
  • Reviews code usage patterns of the updated dependency.
  • Generates and commits code fixes directly to the dependency bump MR branch.
  • Re-runs the pipeline after applying fixes.

Results are based on AI analysis and should be reviewed by a developer before merging.

Prerequisites

Trigger the flow

You can trigger the flow automatically or manually.

Automatic trigger

The flow runs automatically when:

  • A pipeline fails on a dependency bump merge request created by the auto-remediation agent.
  • The feature is enabled for the project.
  • GitLab Duo features are enabled for the project or group.

The analysis runs in the background. When complete, any generated fixes are committed to the merge request branch and the pipeline is re-run.

Manual trigger

To manually trigger agentic breaking change resolution on a merge request (that bumps dependencies) with a failed pipeline:

  1. In the top bar, select Search or go to and find your project.
  2. In the left sidebar, select Code > Merge requests.
  3. Select the dependency bump merge request with a failed pipeline.
  4. In the pipeline widget, select Resolve breaking changes with Duo.

The flow runs in the background. When complete, it commits any generated fixes to the MR branch and re-runs the pipeline.

Provide feedback

Share your feedback in the feedback issue.