If you see warnings/errors on GitHub Actions related to Matrix incompatibilities for your R package, see this issue for possible workarounds: https://github.com/r-lib/actions/issues/832
GitHub Actions now supports free arm64 macOS runners for open source projects!
I have just updated https://github.com/r-lib/actions to support the new macos-14 runner. Add this runner to your test matrix if you want to test your R package on arm64 macOS 14.
Ie. you need a configure (+ configure.win) file that creates an Rd macro on older R, that rewrites the examples with |>.
You'll also need Biarch: true in DESCRIPTION.
@gaborcsardi@sckottie I understand not using the magrittr pipe in package code, but, since the base pipe doesn't have runtime overhead, do you think it might become more prevelant in tidyverse package code after 4.5? I'm still being careful not to pipe in package code, but I'm not sure there will be a reason not to do so.
@gaborcsardi I use rig, and in Rstudio I set a mirror, but I also use renv, which also controls the CRAN mirrors in use. At the personal computer I think I have it similarly. But I selected rig because is the first it is set.
@gaborcsardi Thanks for the workaround! I also ran into this using {lme4} + the pkgdown workflow last week. Is it worth applying the workaround as a permanent fix, or if I just wait awhile will the issue sort itself out?
The new evercran project (https://github.com/r-hub/evercran#readme) helps you run old (or ancient) versions of R, together with old (or ancient) snapshots of CRAN.