Julia v1.5.0-beta1 is now available

The Julia developers are pleased to announce that Julia v1.5.0 is now in beta, and binaries for the first beta version, 1.5.0-beta1, are available now. You can get them at https://julialang.org/downloads in the “upcoming release” section for macOS, FreeBSD (x86-64), Windows (32-, 64-bit), glibc Linux (i686, x86-64, AArch64), and making its debut, musl Linux (x86-64). Check out the NEWS file to see what will be new in 1.5.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.5.0 prior to a full release. Note that 1.5 on Travis, AppVeyor (with Appveyor.jl), and Cirrus (with CirrusCI.jl) now points to 1.5.0-beta1.

Let us know in the issue tracker 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.

Happy coding!


5 posts were split to a new topic: Using superscript ⁻¹ as a postfix operator for inv?

Dang. I hardly had time to complain about 1.4.2



I’m getting errors in Travis during the installation step on Ubuntu

Installing Julia
0.01s$ CURL_USER_AGENT="Travis-CI $(curl --version | head -n 1)"
0.00s$ mkdir -p ~/julia
0.38s$ curl -A "$CURL_USER_AGENT" -sSf -L --retry 7 'https://julialang-s3.julialang.org/bin/linux/x64/1.5/julia-1.5-latest-linux-x86_64.tar.gz' | tar -C ~/julia -x -z --strip-components=1 -f -
curl: (22) The requested URL returned error: 404 Not Found
gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
The command "curl -A "$CURL_USER_AGENT" -sSf -L --retry 7 'https://julialang-s3.julialang.org/bin/linux/x64/1.5/julia-1.5-latest-linux-x86_64.tar.gz' | tar -C ~/julia -x -z --strip-components=1 -f -" failed and exited with 2 during .

Presumably this is a problem on Travis’s end, or with 1.5? Tests passed for Mac.

I believe so, since curling that works for me locally. Sometimes their caching can be a little odd. You could give it a bit then try again.

1 Like

Might be an issue with the special caching that we do on Travis and other CI services. @staticfloat

Is this the equivalent of -rc1? We’re using beta now? That’s probably more widely understood than rc, so makes sense to me :slight_smile: :+1:

1 Like

Hasn’t there always been a beta prior to rc?

I don’t know if I’m just lucky, but all the nightly versions recently have been really solid. All would just work!

Bang up job, guys! Thank you very much.


Ah, sorry, i couldn’t remember. :sweat_smile: Might’ve been wrong about that


Pada tanggal 29 Mei 2020 05:25, “Alex Arslan via JuliaLang” <julialang@discoursemail.com> menulis:

peak mem usage reduced. Very nice!


and now - the docker image is ready ! :whale2: :julia:
see the latest tags : https://hub.docker.com/_/julia?tab=tags

$ docker run -it --rm julia:1.5 
   _       _ _(_)_     |  Documentation: https://docs.julialang.org
  (_)     | (_) (_)    |
   _ _   _| |_  __ _   |  Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 1.5.0-beta1.0 (2020-05-28)
 _/ |\__'_|_|_|\__'_|  |  Official https://julialang.org/ release
|__/                   |


Indeed, in general you’re going to need to wait a few hours before CI services in various cloud regions will have the file ready. That may not always be true, but for now it is, because of how we copy from the global S3 bucket that a standard user would download from, to the specialized datacenter-local caches we maintain for each cloud provider.

1 Like

The first official binaries where the current REPL task is the root Task.

julia> Base.roottask == current_task()
1 Like

Not really equivalent. The RCs typically (except 1.4.0 RC1 IIRC) have had more thorough “quality control” than this beta. The choice to release an early beta is to get a longer testing time, even if some of that testing time is on a version of 1.5 that is a bit polished.

Don’t think so. I think we had an alpha for 1.3 (or was that 1.4?).

Ooops... ignore me!

Stefan had said that 1.5 is likely to become the new LTS. Makes sense to have a longer testing phase, if that’s a possibility.


The new inline allocation of structs with pointers in v1.5 is awesome:


Not really; he recently said that 1.6 is likely to become the next LTS:


Ahh - good catch. Sorry for the misinformation!