Do remember to add a Breaks+Replaces on the old SONAME when the new one gets in.
AFAIK, thete is no need for Breaks+Replaces unless both old and new packages contain conflicting files.
Indeed, please don't add Beaks/Replaces soname bumps. They are actively harmful to the transition.
If you have conflicting files, please take this occasion already to move them out to some -common binary package, so that the previous and new library packages are coinstallable.
> Or do I simply revert the SONAME and pray no one notices the binary difference. The last option is easiest, but of course not the best.
We should never break ABI, so this last option should never be done.
+1
That would be a grave Policy violation that can very easily get your package kicked out of testing, so....