-
Notifications
You must be signed in to change notification settings - Fork 330
Installation on R < 4.0 fails on evaluate
now requiring R >= 4.0
#1969
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
That version of evaluate hasn't been released yet, so I'm surprised it's causing problems. |
Oh it is in the released version; ooops. |
Having read through that support log, I'm pretty confident the right fix is to ensuring we're requiring 4.0.0 for testthat, which I believe will happen naturally as part of our release process. |
Given that it seems like 3.6 is going to be around for a while, we want to at least reserve the possibility of continuing test some packages on 3.6. That means we should formally declare 3.6 support in testthat and add it to our testing matrix. |
After more time has elapsed it seems like requiring R 4.0.0 caused few problems (especially once we changed our GitHub action to install older versions if necessary). |
Seen in zendesk ticket 106807. Mentioned here: r-lib/evaluate#173 (comment)
Solved by installation of older version using
devtools
Ideally
testthat
installation candidate will install the version ofevaluate
required per the version of R being run, ortestthat
have a requirement of R>=4.0 as well.The text was updated successfully, but these errors were encountered: