Should we update r-renv-lock workflow given that {admiraldev} did not exist before R version 4.2
#22
Should we update r-renv-lock workflow given that `{admiraldev}` did not exist before R version 4.2
#22
-
|
You can see here that admiradev first version on CRAN is dated of 2022-08-26 08:12:34 UTC. This means that the R version at that point in time was already 4.2.1: https://github.com/r-hub/rversions. Because of that reason this workflow is always going to fail for version 4.1: https://github.com/pharmaverse/sdtm.oak/actions/runs/6897877356. Should we fix this?
|
Beta Was this translation helpful? Give feedback.
Answered by
ramiromagno
Nov 21, 2023
Replies: 1 comment
-
|
This has been done here: 900d3ea. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
ramiromagno
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This has been done here: 900d3ea.