heroku-buildpack-elixir
heroku-buildpack-elixir copied to clipboard
Issues upgrading to Heroku 22
I'm trying to spin up a review app to test upgrading from Heroku 20 to the Heroku 22 stack.
I get the following error:
-----> Checking Erlang and Elixir versions
Will use the following versions:
* Stack heroku-22
* Erlang 24.3.3
* Elixir v1.13.4
Sorry, Erlang 24.3.3 isn't supported yet. For a list of supported versions, please see https://github.com/HashNuke/heroku-buildpack-elixir#version-support
When I follow the link it shows that Erlang 24.3.3 should be supported in Heroku 22 https://repo.hex.pm/builds/otp/ubuntu-22.04/builds.txt
Here is my full elixir_buildpack.config
# Elixir version
elixir_version=1.13.4
# Erlang version
# https://github.com/HashNuke/heroku-buildpack-elixir-otp-builds/blob/master/otp-versions
erlang_version=24.3.3
# Recompile Sentry to get latest source code
hook_pre_compile="mix sentry_recompile"
# Build Assets
hook_post_compile="mix assets.deploy"
EDIT: Switching from the release buildpack to the bleeding edge build pack resolved the issue. Is there any way for me to follow when Heroku 22 support is released?
same issue here
hi @abstractcoder,
Look at your provided logs, seems that your heroku-buildpack-elixir
repo is not latest version.
Due to "Sorry,..." message was changed in commit a year ago.
Let pull the latest version of this repo and try again.
Other hand, please be careful about elixir+OTP version, I see that you try to use elixir v1.13.4 with Erlang 24.3.3.
They said Elixir v1.13.4 should use OTP 25 https://hexdocs.pm/elixir/compatibility-and-deprecations.html#compatibility-between-elixir-and-erlang-otp.
Thanks & br
If someone is like me and wondering how to upgrade the buildpack to the latest version, just doing a
heroku buildpacks:set -a app https://github.com/HashNuke/heroku-buildpack-elixir.git
worked for me.
I also cleared the build cache on Heroku a couple of times which may or may not have helped. Instructions for this is available at Herokus help pages
I was running into this from a review app failure, and a heroku buildbacks:clear -a app
also did the trick by bringing the installed buildpacks in line with what was defined in app.json
.