Formalized propagation and approval of code changes in a tightly coupled environment

A system comprising:

• one or more hardware processors;
• and
• a memory storing instructions that, when executed by the one or more hardware processors, cause the one or more hardware processors to perform operations comprising:
• determining dependencies of packages in a plurality of repositories, each repository including one or more packages;
• identifying a set of compatible versions for the dependencies of the packages;
• creating a new branch in a repository of the plurality of repositories;
• updating a package manifest of the new branch based on the set of compatible versions;
• updating files that reference the package manifest in the new branch;
• validating the new branch based on the updated files;
• publishing a new version of an updated package in the repository in response to the validating being successful;
• generating a machine-readable changelog file that identifies an author of changes to a dependency package of the repository;
• and
• in response to the validating being successful, generating a notification to the author identified in the machine-readable changelog file, the notification indicating that the new branch has been successfully merged into a master branch in the repository.

A machine-storage medium storing instructions that, when executed by one or more processors of a machine, cause the one or more processors to perform operations comprising:

• determining dependencies of packages in a plurality of repositories, each repository including one or more packages;
• identifying a set of compatible versions for the dependencies of the packages;
• creating a new branch in a repository of the plurality of repositories;
• updating a package manifest of the new branch based on the set of compatible versions;
• updating files that reference the package manifest in the new branch;
• validating the new branch based on the updated files;
• publishing a new version of an updated package in the repository in response to the validating being successful;
• generating a machine-readable changelog file that identifies an author of changes to a dependency package of the repository;
• and
• in response to the validating being successful, generating a notification to the author identified in the machine-readable changelog file, the notification indicating that the new branch has been successfully merged into a master branch in the repository.