# Julia v1.4.0 has been released

**URL:** <https://discourse.julialang.org/t/julia-v1-4-0-has-been-released/36324>\
**Category:** Announcements\
**Created:** [March 22, 2020, 12:45am UTC](https://discourse.julialang.org/t/julia-v1-4-0-has-been-released/36324 "2020-03-22T00:45:44Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![dilumaluthge](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dilumaluthge/32/29283_2.png) [@dilumaluthge](https://discourse.julialang.org/u/dilumaluthge)\
**Post date:** [March 22, 2020, 6:26am UTC](https://discourse.julialang.org/t/julia-v1-4-0-has-been-released/36324/6 "2020-03-22T06:26:33Z")

</div>

> [@Albert\_Zevelev](#):
>
> Is there some kind of testing that can be done before a new version of Julia is released to check that, say, the top 20 Julia packages (by github stars) work? And the maintainers can be notified pre-release if there is an issue?

> [@Albert\_Zevelev](#):
>
> That said, it could be nice to test the most frequently used Julia packages before a release…

We already do exactly that. We test all registered Julia packages (registered in the General registry) prior to making a Julia release. We also do this every day on the latest Julia master. See:

1. [ANN: Nanosoldier package evaluation -- with badges!](https://discourse.julialang.org/t/ann-nanosoldier-package-evaluation-with-badges/33339)
2. [GitHub - JuliaCI/NanosoldierReports: A repository for human-readable reports generated by the Nanosoldier.jl CI system.](https://github.com/JuliaCI/NanosoldierReports)
3. [GitHub - JuliaCI/Nanosoldier.jl: A package for running JuliaCI services on MIT's Nanosoldier cluster](https://github.com/JuliaCI/Nanosoldier.jl)
4. [GitHub - JuliaCI/PkgEval.jl: Keeping tabs on the julia ecosystem](https://github.com/JuliaComputing/NewPkgEval.jl)

---

_[View the full topic](https://discourse.julialang.org/t/julia-v1-4-0-has-been-released/36324)._