Circuit breaker pattern: Hystrix is dead, what are you using now?

with Hystrix officially dead, my team is trying to figure out what the go-to solution for circuit breaking is these days. we've got a few critical services that could really benefit from more robust fault tolerance, especially when downstream dependencies get flaky. we've looked at libraries like Resilience4j for JVM stuff and Polly for .NET, also gobreaker for our Go services. but then there's also the option of pushing circuit breaking down to the infrastructure layer, maybe via a service mesh if we ever adopt one. i'm leaning towards application-level libraries for more granular control and immediate feedback, but the overhead of integrating and maintaining these across a polyglot environment is real. what's the community's consensus on this? are you sticking to language-specific libraries, or is there a strong push towards infra-level solutions now?