From 95647969eecf199cf9eea3bf4fb622ae37b0cd7d Mon Sep 17 00:00:00 2001 From: James Black Date: Thu, 15 Feb 2024 16:46:57 +0100 Subject: [PATCH] posit package manager --- content/cicdworkflows-minimum/posts/r-cmd-check/r-cmd-check.qmd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/cicdworkflows-minimum/posts/r-cmd-check/r-cmd-check.qmd b/content/cicdworkflows-minimum/posts/r-cmd-check/r-cmd-check.qmd index 5b6c541..b2d5662 100644 --- a/content/cicdworkflows-minimum/posts/r-cmd-check/r-cmd-check.qmd +++ b/content/cicdworkflows-minimum/posts/r-cmd-check/r-cmd-check.qmd @@ -22,7 +22,7 @@ toc: true `R CMD Check` has [around 50 checks](https://r-pkgs.org/R-CMD-check.html), but the general jist is it will check your package is fit to install, and as part of that process run the unit tests. In many companies, you will be running potentially multiple versions of R in parrallel. To reflect that, this gh-action is updated to run across the last 3 R major versions, -using a snapshot from the Posit Public Manager that reflects a relevant time frame for when that R version was latest. +using a snapshot from the Posit Public Package Manager that reflects a relevant time frame for when that R version was latest. If you have dependencies on other pharmaverse packages, it's likely you will also want to run `R CMD Check` using CRAN today + the bleading edge of the pharmaverse (which may be pre-CRAN) via pointing at their r-universe. If this is the case, please see the advanced usage below.