You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks to @pratikunterwegs report, I found that to update the renv.lock file, one way is to reuse {sandpaper} functions, at least instead of the renv::init
The project template already has a renv.lock file within the renv/profiles/lesson-requirements path. Using renv::init creates a new renv.lock which I suspect is not appropriate for the repo.
Thanks to @pratikunterwegs report, I found that to update the
renv.lock
file, one way is to reuse{sandpaper}
functions, at least instead of therenv::init
The project template already has a
renv.lock
file within therenv/profiles/lesson-requirements
path. Usingrenv::init
creates a newrenv.lock
which I suspect is not appropriate for the repo.Following the vignette on "building a lesson with package cache", we can follow these family of functions to initialize and update the files that the project already has:
And a mix of them with the
{renv}
to check for status, snapshots, install, and possibly also to restore the environment.The text was updated successfully, but these errors were encountered: