legacy compatibility is no longer explicitly tested, people who udpate the R package should also update the hook revision. This is explicitly required for new issues.

Author: lorenzwalthert

.github/workflows/hook-tests-legacy.yml

@@ -35,20 +35,6 @@ This package has five testing workflows:
     `run_test()` and check in the user R profile if it is set, and then
     activate the renv. This is done with `R_PRECOMMIT_HOOK_ENV`.
 
--   Legacy hook testing: It is possible that someone updates the R
-    package {precommit}, but not the hook revision (e.g. with
-    `precommit::autoupdate()`) or vice versa. If the hook revision is
-    updated to `>= 0.2.0`, all hook scripts and {precommit} functions
-    called from the hook script are from the same version of
-    {precommit}, so we don't need to test hook compatibility. If the R
-    package is updated but not the hook revision, old hook scripts are
-    called with while the {precommit} functions in them are from a new
-    package version. Hence, we need compatibility between new packages
-    and old hook scripts, which is exactly what is tested with this
-    workflow. Until there are breaking changes in the *hook script
-    helpers* family of exported functions, there should not be a
-    problem.
-
 -   complete testing: Tests hooks as well as usethis like access
     functionality with latest CRAN packages, on all platforms, with all
     installation methods.