The correct course of action is to either reverse/fix the code change to the library you depend on, or if your code is clearly using the library wrong and can be easily fixed, to do that. Not to let the whole ecosystem slowly spiral out of control.
Either way, the point is that it will force the issue to be resolved, quickly, and the code base to move forward.
The tools/libraries you depend on are themselves dependent on other libraries and tools. They may have done changes that are necessary to continue working, which you are not picking up if you stay behind. They will do IPC and RPC and always rely on their infrastructure being current.
>In a monorepo world, you don't have a choice. You've been forcefully migrated
Yes, and that's good, because:
> and migrate only when you want to, and when you're feeling confident about it.
... does not help in moving the code forward.
If your change will break others, you need to coordinate with those others so that the transition happens gracefully, not let them live on what amounts to unsupported (and slowly more incompatible) code.
