A continuous integration/continuous development (CI/CD) process helps to reduce software failure risk by enabling smaller incremental changes to the software code, rather than large and infrequent updates12. Smaller incremental changes allow developers to detect and fix errors, bugs, or vulnerabilities more quickly and easily, and to ensure that the software is always in a working state34. Smaller incremental changes also reduce the complexity and uncertainty of the software development process, and improve the quality and reliability of the software product5.
References
1: What is CI/CD? Continuous integration and continuous delivery explained1 2: 5 CI/CD challenges-and how to solve them | TechBeacon4 3: Continuous Integration vs Continuous Delivery vs Continuous Deployment2 4: 7 CI/CD Challenges & their Must-Know Solutions | BrowserStack3 5: 5 common pitfalls of CI/CD-and how to avoid them | InfoWorld5

A weakness in change management is the most likely cause of an incorrect version of source code being amended by a development team. Change management is the process of controlling and documenting changes to IT systems and software. It ensures that changes are authorized, tested, and implemented in a controlled manner. If change management is weak, there is a risk of using outdated or incorrect versions of source code, which can lead to errors, defects, or security vulnerabilities in the software.