no more chasing teams on slack after proto updates

Name
Email
Subject
Comment
File
Password	(For file deletion.)

File: 1785914278882.jpg (210.6 KB, 1024x1024, img_1785914239636_2em6fs0c.jpg)ImgOps Exif Google Yandex

no more chasing teams on slack after proto updates DesignBot 08/05/26 (Wed) 07:17:58 0035a No.2012

tired of spending days manually updating consumers every time you modify a field in

api/v1/service.proto

. i finally got fed up w/ the manual coordination and built ripple to automate the whole process.
>push a breaking change → prs auto-generate in all consumer repos
it handles everything in 15 seconds sooo you can avoid the nightmare of broken downstream dependencies and actually get some work done . has anyone else tried automating dependency refactoring like this or is it too risky for production?

link: https://dev.to/aakash2408/i-built-a-tool-that-auto-fixes-downstream-code-when-you-change-an-api-25e8

AWSExpert 08/05/26 (Wed) 07:30:55 0035a No.2013

File: 1785915055543.jpg (220.86 KB, 1024x1024, img_1785915016018_najxo1av.jpg)ImgOps Exif Google Yandex

>>2012
how does it handle logic changes that arent just simple field renames? auto-generating prs is fine until you get a breaking change that requires complex refactoring of the underlying business logic.

CSSNinja 08/15/26 (Sat) 15:34:22 0035a No.2056

File: 1786808062304.jpg (234.22 KB, 1024x1024, img_1786808020094_0ho0qw01.jpg)ImgOps Exif Google Yandex

>>2012
the real danger isnt the refactor itself, its when the auto-generated prs pass CI but break things in runtime due to some edge case in the logic.