As long as those deprecation errors a are accompanied with an upgrade guide detailing the deprecations, you can't be blamed for anything.
I'm sure people will upgrade willy-nilly and still call you names, but at least they've had plenty of warning.
Besides, if your program doesn't work on their test environment after updating because it needs some extra config to enable legacy behaviour, their update process will have to slow down (alter config and retry) but no serious downtime will occur.
I'm sure people will upgrade willy-nilly and still call you names, but at least they've had plenty of warning.
Besides, if your program doesn't work on their test environment after updating because it needs some extra config to enable legacy behaviour, their update process will have to slow down (alter config and retry) but no serious downtime will occur.