Julia v1.2.0 has been released

The Julia developers are pleased to announce the release of Julia v1.2.0, the second minor release in the 1.x series. Binaries are available for Linux, Windows, macOS, and FreeBSD at https://julialang.org/downloads.

As a minor release, v1.2.0 contains no breaking changes, only new features, performance improvements, and marginal, undisruptive changes in behavior. The best reference for the changes in 1.2 is the NEWS file for 1.2.0.

Note that 1.2, like 1.1, does not have long term support. As of this release, 1.1 has been effectively superseded by 1.2, which means there will not likely be any further 1.1.x releases. Our good friend 1.0 is still currently the only long-term support version.

We encourage everyone to give it a try. Packages can test with 1.2.0 on CI by specifying 1.2 on Travis, AppVeyor (with Appveyor.jl), and Cirrus (using CirrusCI.jl). As always, let us know in the issue tracker if you run into any issues.

Happy coding!


The link for the pdf manual for 1.2 at the top of https://docs.julialang.org/en/v1/ is not working. It gives a 404 error.

Fixed now.

1 Like

In the pdf manual, each of the sections under “Julia v1.2 Release Notes” shows up as a separate chapter. Chapter 3 (Language changes), for example, is one line long. Not really a problem, but I think it would make more sense if the Release Notes were all contained in a single chapter.

Sure, the PDF output could really use an overhaul. Feel free to contribute: https://github.com/JuliaDocs/Documenter.jl !


When I upgraded from 1.0 to 1.1, someone gave me these instructions.
Are these instructions still valid for the upgrade of 1.1 to 1.2

Note that if you want to keep the same packages as in 1.0 you 
can copy (or rename if you are no longer using julia 1.0) 
the .julia/environments/v1.0 folder to .julia/environments/v1.1

$ cd ~/.julia
$ cd environments/
$ ls
$ cp -rp v1.0 v1.1
$ ls -l
total 0
drwxr-xr-x  4 ssiew  staff  136 18 Aug  2018 v1.0
drwxr-xr-x  4 ssiew  staff  136 18 Aug  2018 v1.1

Pretty much yes, but of course you would have to modify

cp -rp v1.1 v1.2

if you are upgrading from 1.1.

symlinking everything to a common directory is also an alternative: