The proposed workarounds are just workarounds, the actual solution is more complex. We could have produced an internal build (hotfix) today, for example, that you could use for development. It just takes a bit more time to actually fix a problem than to work around it.
So, instead, we chose to release an official version that you can use in production as well and we are planning on doing that tomorrow, just a day after a potential hotfix could have been available.
This is the best way to provide a resolution for this problem, because it will allow all other clients to have an official release and fix, including people that hit the issue years from now (an internal build or hotfix would not have been available after the next official release).
We take such regression bugs very seriously and we want to minimize their impact in the long run as well.
I hope this explains why we chose this path and alleviates your concerns.
Telerik by Progress
Check out the new UI for ASP.NET Core
, the most complete UI suite for ASP.NET Core development on the market, with 60+ tried-and-tested widgets, based on Kendo UI.