Application Programming Interfaces (APIs) facilitate the integration of third-party dependencies within the code of client applications. However, changes to an API, such as deprecation, modification of parameter names or types, or complete replacement with a new API, can break existing client code. These changes are called breaking dependency updates; It is often tedious for API users to identify the cause of these breaks and update their code accordingly. In this paper, we explore the use of Large Language Models (LLMs) to automate client code updates in response to breaking dependency updates. We evaluate our approach on the BUMP dataset, a benchmark for breaking dependency updates in Java projects. Our approach leverages LLMs with advanced prompts, including information from the build process and from the breaking dependency analysis. We assess effectiveness at three granularity levels: at the build level, the file level, and the individual compilation error level. We experiment with five LLMs: Google Gemini-2.0 Flash, OpenAI GPT4o-mini, OpenAI o3-mini, Alibaba Qwen2.5-32b-instruct, and DeepSeek V3. Our results show that LLMs can automatically repair breaking updates. Among the considered models, OpenAI’s o3-mini is the best, able to completely fix 27% of the builds when using prompts that include contextual information such as the erroneous line, API differences, error messages, and step-by-step reasoning instructions. Also, it fixes 78% of the individual compilation errors. Overall, our findings demonstrate the potential for LLMs to fix compilation errors due to breaking dependency updates, supporting developers in their efforts to stay up-to-date with changes in their dependencies.

@article{ReyesGarcía2057618,
 title = {Byam: Fixing Breaking Dependency Updates with Large Language Models},
 year = {2026},
 doi = {10.1007/s10664-026-10835-1},
 author = {Reyes García, Frank and Mahmoud, May and Bono, Federico and Nadi, Sarah and Baudry, Benoit and Monperrus, Martin},
 url = {http://arxiv.org/pdf/2505.07522},
 institution = {Université de Montréal, Montreal, Canada},
 journal = {Empirical Software Engineering},
 number = {4},
 eid = {113},
 publisher = {Springer Nature},
 volume = {31},
}