So the fix landed as well in 5.10.203 and 6.1.66 in particular, will add a respective closer for this bug with those rebases. This means the update will be in the next upload rebasing at least to those versions (it was too late for the next round of point release for bookworm).
