# PkgEval on 'pre' with notifications?

**URL:** <https://discourse.julialang.org/t/pkgeval-on-pre-with-notifications/118859>\
**Category:** Tooling\
**Created:** [August 31, 2024, 4:42pm UTC](https://discourse.julialang.org/t/pkgeval-on-pre-with-notifications/118859 "2024-08-31T16:42: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:** [August 31, 2024, 4:42pm UTC](https://discourse.julialang.org/t/pkgeval-on-pre-with-notifications/118859/1 "2024-08-31T16:42:41Z")

</div>

Wouldn’t it be nice to have PkgEval running on the ‘pre’ releases, and notifying (opt in, of course) authors of failure?

(PkgEval on nightly is good for Julia development but not so much for package authors, as it fails too often)

---

<div class="post-metadata">

**Author:** ![jishnub](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jishnub/32/33620_2.png) [@jishnub](https://discourse.julialang.org/u/jishnub)\
**Post date:** [September 1, 2024, 11:25am UTC](https://discourse.julialang.org/t/pkgeval-on-pre-with-notifications/118859/2 "2024-09-01T11:25:17Z")

</div>

This is run occasionally on the backport branches, but perhaps a more systematic run might help package developers. Since pre releases are much less frequent, we don’t need this to be run regularly, and occasional runs when backport branches are merged to the release branch would notify about breakages prior to the actual release.