@cclauss we should probably try to get this out quickly as a hot fix. I could merge it, but would need someone to cut the release

Agreed. Who cut the last release?

@ductoanthanh did you cut a release by chance? We might need your help cutting another one with this change in it

@benmccann I cut the last release. My change in #923 was not supposed to be a breaking change therefore I didn't make a major version change. The breaking change was introduced in one of the earliers PRs which was merged.

As for the change in this PR, do you think the version should be bumped to 2.0.3? I am not sure if it is even allowed on the registry to unpublish a package.

Yeah, #923 wasn't breaking and you didn't do anything wrong. It was my fault for missing it in #919

We don't need to unpublish the last release. Just merging this and cutting a 2.0.3 would be perfect

@benmccann Let's merge this one then. What's the latest you need a new release to be published?

Merged. Whenever you get a chance for the release would be great. Thanks!

Looks like this was just released as 2.0.3. Thank you both!