Dependencies not discovered when specified using target::tar_option_set()

[garciamikep]

Neither renv::dependencies() nor renv::hydrate() are detecting packages specified with targets::tar_option_set(packages = ...) in a targets workflow. See here for a simple example: https://github.com/garciamikep/renv-target-issue.

This seems consistent with the renv documentation. Given that both targets and renv aim to enhance reproducibility, should automatic dependency discovery be supported for this workflow?

[kevinushey]

Thanks! Should now be supported in the development version of renv.

[garciamikep]

Excellent, thank you for the quick turnaround! The development version is now working for me for this workflow.

[mattwarkentin]

@garciamikep I'm late to the party here, but we (Will and I) had implemented targets::tar_renv() a while ago for exactly this reason - to provide native {renv} support for {targets} users by exposing these "hidden" package dependencies in a way that would be picked up by {renv}'s heuristics.

This update to {renv} is great and will work for simple cases, but there are still "hidden" package dependencies that are picked up by targets::tar_renv() that won't be detected by {renv}.