# Julia v1.7.0-beta4 is now available
**URL:** https://discourse.julialang.org/t/julia-v1-7-0-beta4-is-now-available/67382
**Category:** Announcements
**Tags:** release
**Created:** [August 30, 2021, 10:05pm UTC](https://discourse.julialang.org/t/julia-v1-7-0-beta4-is-now-available/67382 "2021-08-30T22:05:05Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@ararslan](https://discourse.julialang.org/u/ararslan)
#### Post date: [August 30, 2021, 10:05pm UTC](https://discourse.julialang.org/t/julia-v1-7-0-beta4-is-now-available/67382/1 "2021-08-30T22:05:05Z")
The Julia developers are pleased to announce that the fourth beta release 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, AArch64, PowerPC), and musl Linux (x86-64). Check out the [NEWS file](https://github.com/JuliaLang/julia/blob/v1.7.0-beta4/NEWS.md) to see what will be new in 1.7.0.
As a beta version, 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, [AppVeyor](https://github.com/JuliaCI/Appveyor.jl), [Cirrus](https://github.com/ararslan/CirrusCI.jl), and [GitHub Actions](https://github.com/julia-actions/setup-julia) now refers to 1.7.0-beta4.
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.
Note to ARM-based Mac users: x86 macOS binaries should still work on ARM-based Macs with Rosetta, but the new AArch64 macOS binaries do not require the compatibility layer.
Note to FreeBSD users: Support for FreeBSD 11 has been dropped, with the minimum supported version now 12.0. As such, Julia v1.7.0-beta4 was built on FreeBSD 12 rather than 11, and is unlikely to work on 11.
---
### Author:  [@ImreSamu](https://discourse.julialang.org/u/ImreSamu)
#### Post date: [August 31, 2021, 3:46am UTC](https://discourse.julialang.org/t/julia-v1-7-0-beta4-is-now-available/67382/2 "2021-08-31T03:46:47Z")
🐋 :julia:
And the Julia `1.7.0-beta4` docker images also ready:
- [Docker Hub - Julia 1.7.0-beta4](https://hub.docker.com/_/julia?tab=tags&page=1&ordering=last_updated&name=1.7.0-beta4)
OS/ARCH
- linux/386
- windows/amd64
- linux/amd64
- linux/arm/v7
- linux/arm64/v8
- linux/ppc64le
---
### Author:  [@mbauman](https://discourse.julialang.org/u/mbauman)
#### Post date: [September 1, 2021, 5:23pm UTC](https://discourse.julialang.org/t/julia-v1-7-0-beta4-is-now-available/67382/3 "2021-09-01T17:23:56Z")
6 posts were split to a new topic: [Warning: Terminal not fully functional on Windows](https://discourse.julialang.org/t/warning-terminal-not-fully-functional-on-windows/67522)
---
### Author:  [@StatisticalMouse](https://discourse.julialang.org/u/StatisticalMouse)
#### Post date: [August 31, 2021, 5:48pm UTC](https://discourse.julialang.org/t/julia-v1-7-0-beta4-is-now-available/67382/6 "2021-08-31T17:48:32Z")
It would probably be best if Debian 11 base was used rather that Debian 10 as [Trivy](https://aquasecurity.github.io/trivy/v0.19.2/) finds quite a lot of vulnerabilities on Debian 10.10.
```julia
julia:1.7.0-beta4 (debian 10.10)
================================
Total: 148 (UNKNOWN: 0, LOW: 108, MEDIUM: 14, HIGH: 22, CRITICAL: 4)
```
(It probably automatically happens anyway, just wanting to point this thing out.)
---
### Author:  [@RaulDurand](https://discourse.julialang.org/u/RaulDurand)
#### Post date: [September 7, 2021, 11:59pm UTC](https://discourse.julialang.org/t/julia-v1-7-0-beta4-is-now-available/67382/7 "2021-09-07T23:59:45Z")
Any estimative for when 1.7 is going to be released?
---
### Author:  [@Palli](https://discourse.julialang.org/u/Palli)
#### Post date: [September 8, 2021, 8:09am UTC](https://discourse.julialang.org/t/julia-v1-7-0-beta4-is-now-available/67382/8 "2021-09-08T08:09:14Z")
We are ~~still waiting~~ for 1.7-RC1 (EDIT: it’s now out, now we’re waiting for 1.7-RC2), and there are [four open issues on the 1.7 milestone](https://github.com/JuliaLang/julia/milestones/1.7) (and you can take a look and help) and " [KristofferC](https://github.com/KristofferC) [force-pushed](https://github.com/JuliaLang/julia/compare/c2c5a83ee1e0941740ce90181337acaaa59acbc0..c85012ae9d38cc24af5700e4b8f222559ae0536c) the backports-release-1.7 branch from [`c2c5a83`](https://github.com/JuliaLang/julia/commit/c2c5a83ee1e0941740ce90181337acaaa59acbc0) to [`c85012a`](https://github.com/JuliaLang/julia/commit/c85012ae9d38cc24af5700e4b8f222559ae0536c) [6 hours ago](https://github.com/JuliaLang/julia/pull/41781#event-5277096575)" (i.e. not yet to the release-1.7 branch).
beta4 was going to be a release candidate possibly, but turned out not to be, i.e. its issue was 1.7-RC1/1.7-beta4.
My guess is we’re going to see 1.6.3, and 1.6.4 first (soon), since the former has been finalized “[KristofferC](https://github.com/KristofferC) merged commit [`11e64d1`](https://github.com/JuliaLang/julia/commit/11e64d1c5712e4e9b50979c22c4f3379c3f31475) into release-1.6 [2 days ago](https://github.com/JuliaLang/julia/pull/41554#event-5266183929)” (while not at the download page) and the latter in the works.
Of the open issues, two are regressions (usually easy to find out why, and then fix), thereof one a performance regression, and that seems to be the only holdup, with the two other issues with fixes available already.
EDIT (now fixed): In addition there are other issues that may not have been put on the 1.7 milestone. Since xoshiro256++ is a new major feature in 1.7, this new issue regarding it from 14 hours ago may delay (I made a PR, a **partial fix** , for that issue): [https://github.com/JuliaLang/julia/issues/42150](https://github.com/JuliaLang/julia/issues/42150)
---
### Author:  [@viralbshah](https://discourse.julialang.org/u/viralbshah)
#### Post date: [September 9, 2021, 1:00pm UTC](https://discourse.julialang.org/t/julia-v1-7-0-beta4-is-now-available/67382/9 "2021-09-09T13:00:43Z")
I want to urge everyone to heavily test the Linear Algebra (esp. BLAS and LAPACK related) capabilities in the run up to 1.7. For those who haven’t followed along, we have a brand new system to pick the BLAS and LAPACK libraries that gives us tremendous flexibility, as discussed in this JuliaCon talk by @giordano and @staticfloat:
[ ](https://www.youtube.com/watch?v=t6hptekOR7s)
The default is just openblas as before and nothing should change compared to 1.6. However, by `using MKL`, you should be able to replace the use of openblas with MKL. See the notes in the MKL.jl package:
> **[GitHub - JuliaLinearAlgebra/MKL.jl: Intel MKL linear algebra backend for Julia](https://github.com/JuliaLinearAlgebra/MKL.jl)**
>
> Intel MKL linear algebra backend for Julia. Contribute to JuliaLinearAlgebra/MKL.jl development by creating an account on GitHub.
Once 1.7 is released, we will start linking various libraries in BinaryBuilder to libblastrampoline, so that this flexibility (to replace BLAS without needing to build a new system image) can be made available to almost anything that links to BLAS and LAPACK.
---
### Author:  [@RoyiAvital](https://discourse.julialang.org/u/RoyiAvital)
#### Post date: [September 9, 2021, 1:17pm UTC](https://discourse.julialang.org/t/julia-v1-7-0-beta4-is-now-available/67382/10 "2021-09-09T13:17:32Z")
What about changing from the `LP64` and `ILP64` API’s?
Will it also be inline with other internal representations of Julia (Basically `BlasInt`)?
---
### Author:  [@ctkelley](https://discourse.julialang.org/u/ctkelley)
#### Post date: [September 9, 2021, 1:38pm UTC](https://discourse.julialang.org/t/julia-v1-7-0-beta4-is-now-available/67382/11 "2021-09-09T13:38:15Z")
Can I test my stuff in CI on the the Apple M1 architecture? If so, how do I do that? Is it as simple as putting
```julia
- AArch64
```
under arch: in my ci.yml file?