Lorenz Walthert

Maybe only `.R` is supported?

I think I found place better suited to request SageMaker features that are wider in scope than just the Python SDK: https://github.com/aws/amazon-sagemaker-feedback. In less than a year, they already shipped...

1. I don't know if switching R version is the problem here. Does it work with R 4.2? I.e. maybe the binary for {assertr} for R 4.2 is not compatible...

With `additional_dependencies`, pre-commit just installs into the renv that you have, without updating any lockfile. So maybe you can clone the {precommit} package, run `renv::restore()`, and then `renv::install('yourpkg@version')` and see...

Ok. Yes, these warnings were expected. Some test files are not parsable on purpose (to test functions). I suggest you `pre-commit clean` in the repo where you want to use...

`renv::purge("[email protected]")` seems a global operation independent of an activated *renv*, so can you run this from any directory? Otherwise from where you have installed the package in (cloned {precommit}).

they need to be installed because running roxygen requires `pkgload::load_all()` as mentioned in #243 and https://github.com/r-lib/roxygen2/issues/771. Hence, we'll probably create a new hook with `language: script` in the future to...

> no MRAN records available from repository URL '/bin/macosx/big-sur-x86_64/contrib/4.3' I don't know if the problem is alwo that MRAN has no binaries built for 4.3 and since it will retire...

My above suggestions: - purge offending package with version from {renv} cache. - `pre-commit clean` to delete pre-commit cache. attempt to commit. If does not work, yes, then you can...

@RHReynolds can you folllow the instructions I put in the [Wiki](https://github.com/lorenzwalthert/precommit/wiki/Packages-are-not-found-after-R-upgrade) to deal with these kinds of errors and tell me if this helped to resolve the problem? Another option...