Agentic breaking change resolution flow

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

Version history

  • Introduced in GitLab 19.2 as an beta feature with a feature flag named enable_dependency_bump_breaking_changes and dependency_bump_web_search.

The agentic breaking change resolution flow automatically analyzes pipeline failures on dependency bump merge requests and generates code fixes to resolve breaking changes introduced by the dependency update.

When a dependency bump merge request has a failed pipeline, GitLab Duo analyzes the failure and attempts to generate fixes. The flow examines:

  • Pipeline error logs to identify the root cause of the failure.
  • Dependency changelogs and release notes to identify breaking changes.
  • Code usage patterns of the updated dependency to determine what needs to change.

After generating fixes, the flow commits them directly to the dependency bump merge request branch and re-runs the pipeline.

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

Prerequisites

Run agentic breaking change resolution

The flow runs automatically when a pipeline fails on a dependency bump merge request created by the auto-remediation agent, and the feature is enabled for the project.

You can also trigger the flow manually:

  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.

Related topics