Closing, based on @arkadiam comment, there were updates of dependency packages that seem to get rid of this behaviour.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.