Closed sarink closed 1 year ago
@sarink thanks again for reporting this & taking the initiative to make a pull request! It's much appreciated.
This issue ended up being a bit more complex and requiring a bigger change than this to ensure users don't see anything unexpected. I've charted a path to a migration and described the error in detail here:
In the mean time, I plan to release a new version with a fix that shouldn't cause any unwanted resource deletions or misbehavior. This is the pull request to implement that:
Resolves #8