# Julia v1.7.0-rc2 is now available

**URL:** <https://discourse.julialang.org/t/julia-v1-7-0-rc2-is-now-available/70228>\
**Category:** Announcements\
**Tags:** release\
**Created:** [October 22, 2021, 4:50pm UTC](https://discourse.julialang.org/t/julia-v1-7-0-rc2-is-now-available/70228 "2021-10-22T16:50:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ararslan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ararslan/32/3825_2.png) [@ararslan](https://discourse.julialang.org/u/ararslan)\
**Post date:** [October 22, 2021, 4:50pm UTC](https://discourse.julialang.org/t/julia-v1-7-0-rc2-is-now-available/70228/1 "2021-10-22T16:50:25Z")

</div>

The Julia developers are pleased to announce that the second release candidate for Julia v1.7.0 is now available. You can download binaries at [https://julialang.org/downloads](https://julialang.org/downloads) in the “upcoming release” section for macOS (x86-64, AArch64), FreeBSD (x86-64), Windows (32-, 64-bit), glibc Linux (i686, x86-64, ARMv7, AArch64, PowerPC), and musl Linux (x86-64). Check out the [NEWS file](https://github.com/JuliaLang/julia/blob/v1.7.0-rc2/NEWS.md) to see what will be new in 1.7.0 and see [here](https://github.com/JuliaLang/julia/compare/v1.7.0-rc1...v1.7.0-rc2) for a list of commits included since v1.7.0-rc1.

As a release _candidate_, this should **not** be considered production-ready. Rather, it’s intended to give users, especially package developers, a chance to try our their code with 1.7.0 prior to a full release. Note that `1.7` on [Travis](https://docs.travis-ci.com/user/languages/julia/), [AppVeyor](https://github.com/JuliaCI/Appveyor.jl), and [Cirrus](https://github.com/ararslan/CirrusCI.jl) now refers to 1.7.0-rc2. On [GitHub Actions](https://github.com/julia-actions/setup-julia), use `^1.7.0-0`.

Let us know in the [issue tracker](https://github.com/JuliaLang/julia/issues) if you run into any issues. Please note that any bugs you may encounter should be posted there rather than being discussed in this thread to ensure visibility to the developers.