Rob

We're also seeing this error since this morning, with no changes to any of our GitHub workflows. It looks like it was one of the two recent PRs that may...

We've pinned to `27513cdf512c25b03c3b2d771032a7d3ed8b02c9` – everything after that seems to have issues for us, so it's likely the SDK v3 change that has caused this.