josevalim

josevalim

Creator of Elixir

Hi everyone,

We have just released the second release candidate for the next Elixir version: v1.7.0-rc.1.

The CHANGELOG and precompiled files are here: Release v1.7.0-rc.1 · elixir-lang/elixir · GitHub

In particular, this release solves a bug in umbrella projects / path dependencies. So if your project failed to compile in the previous RC, please give this one a try. Let us know in the comments if you found any bugs or if everything worked out fine.

You can either compile the v1.7 branch from source OR use the precompiled files, as described in our install page.

Note that you will need {:ex_doc, "~> 0.19-rc"} if you want to generate docs using the release candidate.

Happy coding!

Showing Posts 1 to 10

uberbrodt

uberbrodt

Works for me. Tested with an umbrella project.

kip

kip

ex_cldr Core Team

Whats the guidance on updating libs to use the new @doc metadata tags? When I update a project to 1.7.0-rc.* I get compiler warnings with @since and @deprecated (fine). If however I move to the new @doc since: "new version" I get compiler errors on current and older releases (as expected)

Does this mean I have to use conditional compilation to be backwards compatible without errors and warnings?

NobbZ

NobbZ

A hard-deprecation of the old feature instantly when introducing the replacement?

Wasn’t the rule to soft-deprecate first for ~2 minors and only then hard deprecate the replaced feature?

kip

kip

ex_cldr Core Team

Its not hard deprecated - it just emits compiler warnings. Since this is a lib that others use I try hard to remove all warnings since, to a consumer, it looks like an uncaring developer and smelly code. Hence why I’m picky.

NobbZ

NobbZ

Emitting warnings is a hard deprecation. Not eimitting them but not documenting is soft deprecation.

Ryzey

Ryzey

I have four applications that work together using path dependencies (not using umbrella). The apps were working okay in 1.6.6, but would not start under the 1.7.0-rc.0 release. They are working again with the 1.7.0-rc.1 release. Thank you!

lukaszsamson

lukaszsamson

ElixirLS Core Team

I’ve been using 1.7 branch as my development environment since before rc.0. So far it’s working great (tested on 3 umbrella projects). The only problem I stumbled into was absinthe failing to compile specs (already fixed btw.)

josevalim

josevalim OP

Creator of Elixir

Thanks everyone for the feedback! We shall release the final version tomorrow, so if you haven’t given it a try yet, don’t forget to do it in the next 24 hours. :slight_smile:

dwahyudi

dwahyudi

Gonna use it in my production now, to see if something breaks, lol.

OvermindDL1

OvermindDL1

Still using it in production for one of my play servers with OTP20 without any noticed issues as of yet. :slight_smile:

Where Next? Top

Trending in News Top

Other Trending Topics Top

mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
webofbits
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself. My main conc...
#ai
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews