Thanks for the bug report! I’ve fixed this locally now - this problem won’t exist in the next bugfix release :)
