Nope, the bug was present in multiple stable versions. From the Github issue comments:

I can reproduce the bug on 1.94, 1.95, 1.96 and nightly. (1.93 seems to be the latest version without the bug present)