Gábor Csárdi

For `Config/Needs/check` you need to use a local package, i.e. `local::...` or `deps::...` because otherwise we don't know the `Config/Needs` fields, they are not in the CRAN metadata.

It is a bug that is accidentally suppressed, I think. Nevertheless `Config/...` dependency specifications should be ignored for CRAN packages.

Unfortunately this is not feasible to do automatically, because there is no metadata available for older packages. So we would need to download (potentially a lot of) packages and extract...

Btw. if DiagrammeR is not a hard dependency, you can also ignore it (on R 3.4), like this: https://github.com/r-lib/actions/tree/v2-branch/setup-r-dependencies#ignoring-optional-dependencies-that-need-a-newer-r-version

In general I don't like the idea of doing this automatically, because you just don't know what exactly is going to be installed. This is basically what `install.packages()` does, and...

No, there is no such metadata stored anywhere. Well, except for https://crandb.r-pkg.org/ of course. In theory we could use that, but it is far from trivial, because it is too...

Why do you use `dependencies = TRUE` every time? That installs all development dependencies of the package, which you most likely don't need.

I pushed some changed to `v2` that seem to fix this: https://github.com/r-lib/actions/issues/483#issuecomment-1013918319

pkgcache now forces HTTP 1.1 as well, so when that is on CRAN it will solve this issue. Except for the pre-bundled pak binaries of course. For those (and until...

Type .Last.error, that souls show the error.