Keeping up with changes is valuable.

At the same time, it's often smart to avoid putting things into production that haven't matured or demonstrated staying power.

Or, to badly mangle Postel's law:

Be liberal in what you learn, and conservative in what you deploy

Just curious, what kind of work have you done where this conceit feels valid in your mind? My career, at least, feels like an exception to this, but I guess its conceivable to me that it could be otherwise. You have had a lot managers push newer frameworks/technologies on you? Is this more VC startup land, or something else?

Maybe I'm old, but at least in web dev it doesn't feel that long ago that someone had to argue for, e.g., Vite over webpack, Svelte over React, etc..

Depends on the thing.

I had to give maintenance to things people deployed to pad their resumes with "shiny new thing", and it was not fun.

If you intend to deploy and leave that as legacy for some poor shlemiel, sure.

If you intend to stay and actually keep things running, it's much better to use tried and tested stuff.

Three years is nothing, what kind of work do you do where you need something released in the last three years?

And I’m not OP, but I would assume the senior developers made a distinction between try and use.