On macOS 10.14.6 here.
I just built gpg 2.2.21. To my surprise, when I symmetrically encrypt a file I am now hounded by pinentry about (a) the length of my passphrase, (b) how many special characters are in my passphrase. Also, (c) it demands that I enter the passphrase again even though passphrase-repeat 0 is in my gpg.conf.
It seems to me that (c) must be a bug. passphrase-repeat 0 has been in my gpg.conf for at least 8 years and I have never experienced this nag before.
I could workaround (a) and (b) my appending settings for min-passphrase-len and min-passphrase-nonalpha. But since (as far as I can tell) there is no mention of any changes regarding passphrase requirements in the release notes, I suspect that this might be a bug too.