I've certainly run into this problem. I used to rely on pristine-tar being set globally and no debian/gbp.conf in my packages and I accidentally pushed a non-pristine-tar new upstream version for one of my packages. Now, it's basically stuck in that state until the next upstream release.
Francois -- https://fmarier.org/
