I tended to avoid updating #Rstats because then I had to reinstall a large number of packages (including commercial ones). My perhaps dangerous approach to more frequent updates:

all my R packages live in a folder defined in .Renviron as R_LIBS_USER="~/r-packages". Then I update.packages()

It has never failed though. At the same time, I usually wait a bit before rolling a new version. I tend to be software version conservative.

@ojala I appreciate Rig for managing my R installations. I keep a version of 4.3 just for {ASReml-R} but have the latest R for most of my daily usage since I rarely use {ASReml-R}, myself.
I always run a single version of R. Currently 4.5 and asreml-R works.
@ojala it's not that it doesn't work, I'm sure it does. It's that the rest of the team uses 4.3 and that's what our multi-seat licensing is set up for, I use it so infrequently I haven't tried to get it set up with 4.5 with any serious effort.
@adamhsparks @ojala There's a small and reliable tool rarely mentioned in this setting which I have found very useful - direnv. Just last week I gave a lightning talk outlining how to get up and running with direnv and R, slides are still available https://public.solarchemist.se/slides/dfupdate25 based on my notes https://links.solarchemist.se/shaare/mcCz1g
Simple management of per-project R versions with direnv

@solarchemist @adamhsparks I'm aware of it, but I dislike the existence of multiple versions of R in my computer. My aim is to write code that has minimal dependencies and, hopefully, just runs. My really important stuff is very close to Base.

@solarchemist @adamhsparks I forgot to add a small example, to show going back to Base R for functions I use to read many spectroscopy files.

https://luis.apiolaza.net/2019/04/14/reading-a-folder-with-many-small-files/

Palimpsest — Reading a folder with many small files

Evolving notes, images and sounds by Luis Apiolaza