Replies from 7 May 2024

Great! This will be part of v2.2.0 which aims to be hopefully mid-May but definitely by the end of May - in the meantime, feel free to pin to the commit that fixes it (on our default branch) until the release