You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CRAN checks are failing. There is no functional deficit, it's just that I set my self a reminder to switch to Python3 tests and installation methods for pre-commit conda. This happened in #191. To be fixed until 2020-10-15 .
We'll stick to the release process outlined in help(precommit:::release_gh). I.e. we'll do a first GitHub release with precommit:::release_gh(), ask users to precommit::autoupdate() and test it. Then, do a CRAN release process with precommit:::release_gh(is_cran = TRUE). To follow sem versioning, we'll wait with merging #203 into master.
The text was updated successfully, but these errors were encountered:
lorenzwalthert
changed the title
new CRAN submission because of pinned python versions
New CRAN submission required because of pinned python versions
Oct 3, 2020
CRAN checks are failing. There is no functional deficit, it's just that I set my self a reminder to switch to Python3 tests and installation methods for pre-commit conda. This happened in #191. To be fixed until 2020-10-15 .
https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-debian-clang/precommit-00check.html
We'll stick to the release process outlined in
help(precommit:::release_gh)
. I.e. we'll do a first GitHub release withprecommit:::release_gh()
, ask users toprecommit::autoupdate()
and test it. Then, do a CRAN release process withprecommit:::release_gh(is_cran = TRUE)
. To follow sem versioning, we'll wait with merging #203 into master.The text was updated successfully, but these errors were encountered: