I do appreciate that Prodigy has a low dependency footprint, and that makes me more confident that issues like this will be few and far between, but people make mistakes - that’s why we have tests 
. The more confidence we can have when we’re moving updates, the faster we can move.
Also, the scope of dependencies that can change widens considerably when you look at sub-dependencies - this is a freeze of our environment now (the only change we integrated since 1.8.3 was to update srsly after it was fixed from Cannot load data with db-in on Prodigy 1.8.3 using annotations created with 1.6):
blis==0.2.4
cachetools==3.1.1
certifi==2019.3.9
chardet==3.0.4
cymem==2.0.2
falcon==1.4.1
hug==2.4.8
idna==2.8
jsonschema==2.6.0
murmurhash==1.0.2
numpy==1.16.4
peewee==2.10.2
plac==0.9.6
preshed==2.0.1
prodigy==1.8.3
psycopg2-binary==2.8.2
PyJWT==1.7.1
python-mimeparse==1.6.0
requests==2.22.0
six==1.12.0
spacy==2.1.4
srsly==0.0.7
thinc==7.0.4
toolz==0.9.0
tqdm==4.32.1
urllib3==1.25.3
waitress==1.2.1
wasabi==0.2.2
That said, I understand if you can’t / don’t want to release the testing suites. Just figured it wouldn’t hurt to ask!