Better ways to deal with CompatHelper and compatibility upgrades

General Usage Performance
1

After some time of innactivity, the CompatHelper bot stops working. Of course this is not an issue for large projects that are very active, but for smaller packages it is.

Thus, I would like to know:

  1. Is there a way to run locally the CompatHelper in a series of packages, such that I can write a script to run periodically in my machine?

  2. Wouldn’t it be better if CompatHelper worked the other way around: that is, one a package releases a breaking change, make pull requests (or at least open an issua) to the packages that depend on it (JuliaHub know already which are these packages, so that part seems solved).

2

This is a very late reply, but I just found out about

2 Likes