4 ms·
No, but you do need a single repo if you want to make the API change and update all the dependencies in one fell swoop.
by enneff 13y ago
No, but you do need a single repo if you want to make the API change and update all the dependencies in one fell swoop.
- zaphar 13y agoThis is what facebook means when they say atomic commits.
- zaphar 13y agoNot just make the change in one fell swoop but also rollback the change in one fell swoop if it turns out to have broken something.
- oblio 13y agoDoes this matter that much if you version everything? Commit in library -> successful library build, failed client build. Commit in client -> successful library build, successful client build. In both situations you don't really care about the intermediary broken build - you still have the previous library/client versions and can use those. Once everything is committed & fixed you have the new versions and you can upgrade. The only problem I see if there's a long delay before the second commit. But this can be prevented by a fast CI cycle (always a good idea) and sending notifications for failures across teams (i.e. the library committer is notified that the client build for his commit failed).
- zaphar 13y agoIf you care about how long it takes to make the change in all your code bases and you care that you identified all the code that needed to change did change then it matters.