will do

Oh that's good then, I was afraid that you found some issue so late into the process.

But still, if you think something is going wrong, let us know.

Oh no, I'm not talking about Codewars updating to newer C# language versions. I'm talking about the C# and .NET framework upgrades in general and THEIR plans to release newer version often.

I would be interested with problems you see caused by the "rapid" C# updates. This method is meant to be used in place where fully automated update is difficult, and is considered for update of C++ kata after C++ 20 gets introduced. If it causes any large scale problems, it would be good to know now, and not after the update :) Until now, none of hundreds of updated C# akta raised any complaint, which I think is good. Maybe some problem was missed, or the updated code is in some way bad, which would be not great.

In this particular case, I do not think that the update to C# 12 is to blame. Mind that Assert.That is compatible with both C# 12 and C# 10 setup, and if the code does not use other C# 12 features, then both language versions will be available, and users who want to use C# 12 language features hae to make sure they use the compatible version. One potential problem is when the default versoin is not switched to C# 12. This happens someties, but it's a CW bug and happened also with fully autoed updates in the past. Republish should fix this and set C# 12 to default.

I understand the confusion, though. All these rapid C# language updates, it's becoming a carousel.

The "B" format specifier is available since .NET 8, which means you need to run tests with C# 12 version selected. The "B" is not supported with C# 10, which uses .NET 6.

It is not a kata issue, you need to use the language version which supports the features you want to use.