Hi,
From your followup, I think I see two things going on.
Let’s talk about what’s in the new code. Did something in your code get marked deprecated? Did maybe a library get upgraded (and the new version includes new deprecations)? That would legitimately cause old uses of that newly deprecated code to have “new” deprecation issues raised on them. There’s a little more in this guide
We get occasional reports of this (and we’ve seen it occasionally ourselves), but it’s as hard to track down as bigfoot. If you spot any pattern at all here, we’d love to have the details.
Yeah… that’s been toned down in subsequent versions. Sorry 'bout that.
Ann