Elixir v1.17.0-rc.0 released

[sabiwara]

@nathany

As I’m sure everyone is aware, that flag usually only fails the build if the project itself contains warnings.

This is correct, --warnings-as-errors should only be failing if the warnings is emitting when compiling the project, not its dependencies.

@nathany

Not sure if this is an issue in Elixir 1.17 or not, but warnings related to Absinthe are failing the build of our project with the --warnings-as-errors flag.

In this case, I suspect this is because of meta programming - the library is probably generating code which gets compiled when compiling the project.

Instead I prefer to first run mix deps.compile (without --warnings-as-errors) and then mix compile --warnings-as-errors to get warning-errors only from my application code.

This should be the same as just running mix compile --warnings-as-errors, for the reason mentioned above.