Same case for me 
Updated to v1 and 90% of my workflows broke because of this. Downgraded to 0.237.0 and will remain there possibly forever. 
I use this approach very much: in one expression look for 2 or more nodes output. The remaining value corresponds to the node that has been executed previously.
I do not understand why this has been deprecated, it is so useful in so many scenarios. It simplifies the workflows and avoids redundacy very much. I hope that in some future 1.x release this will be available again 
Example of use case:
