The current_entity property was removed in 3.0

Not sure why this came out with the D10 updates. Seems fine to me -- do you have someone you can get to test and mark RTBC?

We noticed it is dangerous to use this property because the entity ID is not always added to the cache keys (eva_entity_view() only adds it if the entity ID is used as view argument).
So if for example you have the same eva view on the same page but for different entities and your code uses the current_entity property to change the output of the view, the view render will only be cached once for the first entity and reused for the other entities.

I feel like we should not add this back because it is not declared, it does not handle cache correctly and could easily be misused.
The correct way to pass the entity ID is to pass it as a view argument (this can easily be enabled in the view settings).