mlsanityData to 14 Oct 2026

Update from Hell: Can Coding Agents Survive Hidden Breakage in Dependency Upgrades?

arXiv 2608.30300 ↗First posted 31 Aug 2026cs.SEcited by 0

On the map: LLM agents and tool use → Software engineering coding agents

Abstract (arXiv)

Modern software systems rely heavily on third-party dependencies, but upgrading those dependencies remains a costly maintenance activity. Dependency upgrades do not always preserve the function signatures, type systems, APIs, or runtime semantics assumed by existing code. Consequently, developers often need to perform source code adaptations to accommodate dependency-induced changes. However, such code-level changes are often not explicitly communicated to project maintainers, posing a significant challenge to software reliability. Meanwhile, coding agents have emerged as a new form of software development tool and are increasingly adopted by developers due to their automation capabilities. In this paper, we introduce DEPBENCH, a benchmark consisting of 203 real-world dependency-upgrade tasks across five package ecosystems spanning five language communities, each involving hidden code-level changes that require source code adaptation. We evaluate mainstream coding agents on DEPBENCH. The best completed configuration solves only 104/203 tasks (51.2%), with substantial variation across agent harnesses, models, and ecosystems, highlighting an important gap between current agent capabilities and real-world software maintenance needs.

Key facts. No citing papers in the map yet (data through 14 Oct 2026). Placed in Software engineering coding agents, one of 16 directions in LLM agents and tool use. Builds on 18 of its 25 references that are in the map. First posted on arXiv 31 Aug 2026.

Builds on

18 of 25 references.

Closest ancestors · 5

Same direction, newest first

  1. 2026SWE-Chain: Benchmarking Coding Agents on Chained Release-Level Package Upgrades14 May
  2. 2026BeyondSWE: Can Current Code Agent Survive Beyond Single-Repo Bug Fixing?3 Mar
  3. 2025FreshBrew: A Benchmark for Evaluating AI Agents on Java Code Migration6 Oct
  4. 2025LLM Agents for Automated Dependency Upgrades3 Oct
  5. 2025GitTaskBench: A Benchmark for Code Agents Solving Real-World Tasks Through Code Repository Leveraging26 Aug

Other references · 13

  1. 2023SWE-bench: Can Language Models Resolve Real-World GitHub Issues?cited by 3,373
  2. 2017Do Developers Update Their Library Dependencies? An Empirical Study on the Impact of Security Advisories on Library Migrationcited by 23
  3. 2022Automating Dependency Updates in Practice: An Exploratory Study on GitHub Dependabotcited by 13
  4. 2025MigrationBench: Repository-Level Code Migration Benchmark from Java 8cited by 11
  5. 2025DI-BENCH: Benchmarking Large Language Models on Dependency Inference with Testable Repositories at Scalecited by 7
  6. 2018On the evolution of technical lag in the npm package dependency networkcited by 5
  7. 2024BUMP: A Benchmark of Reproducible Breaking Dependency Updatescited by 5
  8. 2021Breaking Bad? Semantic Versioning and Impact of Breaking Changes in Maven Centralcited by 3
  9. 2021On the Impact of Security Vulnerabilities in the npm and RubyGems Dependency Networkscited by 2
  10. 2024Breaking-Good: Explaining Breaking Dependency Updates with Build Analysiscited by 2
  11. 2025Byam: Fixing Breaking Dependency Updates with Large Language Modelscited by 2
  12. 2026CI-Repair-Bench: A Repository-Aware Benchmark for Automated Patch Validation via CI Workflowscited by 2
1 more
  1. 2026Breaking Changes in Software Ecosystems: A Systematic Literature Reviewcited by 1

Built on by

Not cited yet.

Similar, not cited

Close in wording, no citation either way

  1. 2026Self-Evolving Coding Agents
  2. 2026Towards a Benchmark for Dependency Decision-Making
  3. 2026RoadmapBench: Evaluating Long-Horizon Agentic Software Development Across Version Upgrades
  4. 2024Evaluating Software Development Agents: Patch Patterns, Code Quality, and Issue Complexity in Real-World GitHub Scenarios
  5. 2026ChainSWE: Benchmarking Coding Agents on Multi-Bug Software Maintenance
  6. 2026Do These Violent Delights Have Violent Ends? Measuring the Post-Merge Fate of Agentic Code
  7. 2026Agentic Generation of AST Transformation Rules for Fixing Breaking Updates
  8. 2026Is Agent Code Less Maintainable Than Human Code?