It’s already fixed, so it’s surprising you are in this situation if you just updated.
The fix is in the release: