Nothing wrong with letting it stand as a guidepost for anybody else who encounters the same thing (just because the bug is fixed now doesn’t mean people won’t still bump into it since not everybody keeps packages up to date).
Even more helpful: you can officially select @samfirke’s post as the solution (here’s how: FAQ: How do I mark a solution?).