# Better ways to deal with CompatHelper and compatibility upgrades

**URL:** <https://discourse.julialang.org/t/better-ways-to-deal-with-compathelper-and-compatibility-upgrades/88677>\
**Category:** Performance\
**Created:** [October 13, 2022, 4:22pm UTC](https://discourse.julialang.org/t/better-ways-to-deal-with-compathelper-and-compatibility-upgrades/88677 "2022-10-13T16:22:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![lmiq](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lmiq/32/18314_2.png) [@lmiq](https://discourse.julialang.org/u/lmiq)\
**Post date:** [October 13, 2022, 4:22pm UTC](https://discourse.julialang.org/t/better-ways-to-deal-with-compathelper-and-compatibility-upgrades/88677/1 "2022-10-13T16:22:41Z")

</div>

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).

---

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [July 18, 2023, 7:47am UTC](https://discourse.julialang.org/t/better-ways-to-deal-with-compathelper-and-compatibility-upgrades/88677/2 "2023-07-18T07:47:17Z")

</div>

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

> **[Alexander Plavin / CompatHelperLocal.jl · GitLab](https://gitlab.com/aplavin/compathelperlocal.jl)**
>
> GitLab.com