I noticed this too, and my users are reporting incorrect dates in some areas of our app. It seems to allow me to continue without selecting a TZID, but my app uses Date references in a LOT of areas so I’m hoping it doesn’t affect anything. Would be great to get clarification on this.
I also have noticed this and I have submitted a bug report. I think the more people who submit a big report the more awareness it gets for the team to fix. I think this bug could be pretty detrimental.
For my case, I use dynamic timezones in parts of my web app and so when this bug started my dynamic timezone was still selected but the field for for Timezone ID (which used to appear when selecting static timezone) was red so instinctively I picked UTC in it just to test what was going on and now I can not clear that field. Which means the logic chooses UTC first instead of my dynamic timezone which is causing incorrect dates.
I would recommend NOT filling in these red fields if you see them, just leave them empty as they don’t show as issues in the issue checker.
I have submitted a bug report and encourage others to do so too as this needs to be fixed asap.