Dependency Scanning auto-remediation (beta) does not respect language output instructions defined in AGENTS.md
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
The Dependency Scanning auto-remediation feature (currently in beta) does not respect language output instructions defined in AGENTS.md. Even when AGENTS.md explicitly and emphatically instructs all AI-generated output — including all items created by flows — to be in a specific language (e.g. Japanese), the feature produces merge request content in English.
This was reproduced on GitLab.com.
In beta, dependency scanning auto-remediation supports two independently configurable capabilities:
- Dependency version bumps: GitLab opens merge requests that update the vulnerable dependency.
- Agentic breaking-change resolution: When a version bump causes a pipeline failure due to a breaking change, GitLab Duo attempts to resolve it.
The behavior differs between the two capabilities:
- Dependency version bumps: Creates the MR in English no matter what language is specified in
AGENTS.md. - Agentic breaking-change resolution: This capability does leave a comment in the MR in Japanese (i.e. it appears to respect the
AGENTS.mdlanguage instruction), which is inconsistent with the version bump behavior.
Note / open question: The Dependency version bumps capability may not be agentic (i.e. it may not use AI at all — it likely just opens a templated MR that updates the dependency version). If that is the case, it would explain why it does not read or respect
AGENTS.md, sinceAGENTS.mdonly governs AI-driven flows. This needs to be confirmed by the team. If version bumps are indeed non-agentic, then:
- The English-only MR content is expected behavior rather than a bug, and
- The real issue is the inconsistency and lack of documentation — users reasonably expect
AGENTS.mdlanguage settings to apply to all auto-remediation output, and the fact that agentic breaking-change resolution does respect it (Japanese comment) makes the mixed-language result confusing.
Steps to Reproduce
-
Add a strong, explicit language instruction to
AGENTS.md— e.g.:"All output must be in Japanese. This includes all items created by flows, such as MR titles, descriptions, and commit messages. Do not use English under any circumstances."
-
Enable Dependency Scanning auto-remediation (beta) with both capabilities:
- Dependency version bumps
- Agentic breaking-change resolution
-
Trigger a dependency version bump MR on a vulnerable dependency.
-
Cause / observe a version bump that triggers a pipeline failure so the agentic breaking-change resolution runs.
-
Observe the generated MR title, description, body, and any Duo comments.
Expected Behavior
Any AI-driven auto-remediation output should read and consistently respect AGENTS.md instructions — including language settings — and generate all artifacts (MR title, description, body, comments, commit messages) in the specified language. If a capability is intentionally non-agentic, that should be clearly documented so users understand why its output is not localized.
Actual Behavior
- Dependency version bumps generate all MR content (title and body) in English despite the explicit Japanese instruction in
AGENTS.md. (May be expected if this capability is non-agentic — see note above.) - Agentic breaking-change resolution leaves a comment in the MR in Japanese, respecting the instruction — inconsistent with the version bump behavior.
Impact
Teams using AGENTS.md to enforce language or output standards cannot rely on Dependency Scanning auto-remediation to comply with those standards. The inconsistency between the two capabilities (one respects the instruction, the other does not) is confusing and undermines the purpose of AGENTS.md as a project-level instruction source for AI flows — especially if the difference is due to one capability being non-agentic but this is not surfaced to users.
Additional Context
- Confirmed on GitLab.com.
- Related to #606773, which reported the same class of problem for the SAST Vulnerability Resolution Flow (
resolve_sast_vulnerability). - Workaround: manually update the MR title and description after the version bump MR is created.