The datetime strictness change is the classic quiet upgrade trap. Nothing in the code changes, but inputs that passed yesterday start failing validation after the bump. Reading the soundness fixes before the benchmark numbers is the right order.
Yeah, had that issue. That's why had to keep both datetime and datetime with precision as union. That actually solved things in my use case. But yeah, plenty of users are facing this issue.