You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure this is enough to trivially reproduce the issue. There isn't anything special about the global deprecation matcher. It should be easy to triage in your application if the deprecation handler code path is being hit at all.
It seems all of the deprecation messages generated here, which we can collectively refer to as "build time deprecations", aren't silenced / thrown if referenced in the deprecation workflow file.
This seems like a timing issue in tests. Have both of these in the config file.
The text was updated successfully, but these errors were encountered: