setup-renv fails with an error

[harisonmg]

Describe the bug
setup-renv fails with this error

Error: Error in eval(quote(*** : object '..version..' not found
Calls: source ... local -> eval.parent -> eval -> eval -> eval -> eval
Execution halted
Error: Process completed with exit code 1.

To Reproduce
Rerun any workflow that uses this action. Below are the logs of the failed action

Run r-lib/actions/setup-renv@v2
Run echo "RENV_PATHS_ROOT=/home/runner/work/_temp/renv" >> $GITHUB_ENV
Run install.packages("renv")
# Bootstrapping renv 0.17.3 --------------------------------------------------
* Downloading renv 0.17.3 ... OK
* Installing renv 0.17.3 ... Done!
* Successfully installed and loaded renv 0.17.3.
ℹ Using R 4.3.1 (lockfile was generated with R 4.2.3)
Retrieving 'https://packagemanager.posit.co/cran/__linux__/jammy/latest/src/contrib/renv_1.0.0.tar.gz' ...
	OK [downloaded 2.1 Mb in 0.31 seconds]
Installing renv [1.0.0] ...
	OK [installed binary in 0.45 seconds]
Moving renv [1.0.0] into the cache ...
	OK [moved to cache in 0.11 seconds]
* Installed 1 package in 1.9 seconds.
The following package(s) have been updated:

	renv [installed version 1.0.0 != loaded version 0.17.3]

Consider restarting the R session and loading the newly-installed packages.

ℹ Using R 4.3.1 (lockfile was generated with R 4.2.3)
Run cat("os-version=", sessionInfo()$running, "\n", file = Sys.getenv("GITHUB_OUTPUT"), sep = "", append = TRUE)
Error: Error in eval(quote(*** : object '..version..' not found
Calls: source ... local -> eval.parent -> eval -> eval -> eval -> eval
Execution halted
Error: Process completed with exit code 1.

Expected behavior
The action should run successfully

Additional context
{renv} recently released version 1.0.0. Could this be the source of problems?

[gaborcsardi]

I think this is fixed in the dev version, to be released soon. You can try it by using r-lib/actions/setup-renv@v2-branch.

[harisonmg]

Your solution works. Thank you @gaborcsardi

[gaborcsardi]

Don't forget to switch it back in a couple of days, after v2 is updated.

[github-actions]

This issue has been automatically locked. If you believe you have found a related problem, please file a new issue and include a link to this issue