Thanks for bringing this to our attention – I let our packaging team know about the errors.
We generally have automated testing in place for builds and releases, but I’m not familiar with our current release automation set up. Although you are using the testing branch, this should have been an avoidable issue as part of our post-release testing.
hi @Shane_Spencer,
Thank you again for finding this issue. We found the underlying problem and fixed it. We are currently working on process improvements to avoid issues like this.