Determining lower bound of compat statement

bclyons12
Fri, 19 Jul 2024 17:58:36 +0000
General Usage

Is there a way to test the lower bound compatibility of a package systematically, say by doing a binary search to find the lowest version for which tests pass? When adding a new compat entry to a Project.toml, CompatHelper sets the lower bound to the latest major or 0.x minor release version, so you might get Roots = "2" or Interpolations = "0.15". It’s possible that earlier versions are compatible as well. That’s less likely for a major release (though not impossible), but it’s common for the 0.x minor releases. I want to avoid making my compat entries overly restrictive, which can make large environments impossible to solve.

2 posts - 2 participants