This message was deleted.

There should not be breaking changes in non major versions, but then if there is, and we deal with it, we don’t expect a bugfix release to undo all of it.

@cool-egg-852 this actually happened upstream and wasn't called out in their CHANGELOG so it was my bad for not studying the changes enough

Just to add - it is definitely our policy that a breaking change would be in a major version bump and would be called out clearly in a CHANGELOG. In this case, a dependency of ours made an unintentional semver-incompatible breaking change without notice. This was a bug in the dependency's release process which we also unfortunately bled through to our users when we updated to the latest version of that dependency. We will be reviewing our processes around more deeply validating dependencies especially for the most heavily used Pulumi providers.

Thanks, though in this case my issue is more on the revert than the original issue.

if not, then at least the revert should have been note

That's a very good point - we absolutely should have (and should now) noted the breaking change revert in the CHANGELOG. We'll update that now.

Thanks!

As I said, completely my fail here @cool-egg-852 - apologise for not picking up this was the case :/

No problem. Live and learn 🙂