As usual, we’ll update glibc in the archive when the new 2.37 will come, which should happen on Thursday, with the upload hopefully on Friday.
As a direct consequence, the autopkgtest queues will blow up, and most arch:any packages uploaded after glibc will be stuck waiting for it to migrate as they’ll have picked up the new version symbols.
Looking at the (incomplete) changelog I don’t expect too much breakage. We’ve done a test rebuilt of the archive back in December, and I was only able to detect one build failure that seemed clearly glibc-related, which I’m currently investigating.
In the mean time, you can use my PPA to test your packages against a very recent snapshot (with the exception of the armhf architecture which is currently FTBFS).