Unable to deploy due to Oban Pro - change in Hex Repo?

Questions / Help
, ,
1

Yesterday I was able to deploy my app successfully.

Today my deploys are breaking with:
|
4.343 Failed to fetch record for oban/oban_pro from registry (using cache instead)

4.343 The configured repository name for your dependency oban/oban_pro does not match the repository name in the registry. This could be because the repository name is incorrect or because the registry has not been updated to the latest registry format. Set HEX_NO_VERIFY_REPO_ORIGIN=1 to disable this check and allow insecure package downloads.

4.352 ** (Mix) Unknown package oban_pro in lockfile

re: Registry

#17 [stage-0 11/22] RUN --mount=type=secret,id=OBAN_LICENSE_KEY,env=OBAN_LICENSE_KEY mix hex.repo add oban https://repo.oban.pro --fetch-public-key SHA256:4/OSKi0NRF91QVVXlGAhb/BIMLnK8NHcx/EWs+aIWPc --auth-key ****

#17 DONE 1.4s

was successful both yesterday and today:

the only changes I can see potentially related to this are that now my deploy is referencing Hex

#16 [stage-0 10/22] RUN mix local.hex --force && mix local.rebar --force

#16 1.083 * creating /root/.mix/archives/hex-2.3.0-otp-28

#16 2.010 * creating /root/.mix/elixir/1-19-otp-28/rebar3

#16 DONE 2.0s

Yesterday ref was:

#16 [stage-0 10/22] RUN mix local.hex --force && mix local.rebar --force

#16 1.009 * creating /root/.mix/archives/hex-2.2.2-otp-27

#16 1.858 * creating /root/.mix/elixir/1-19-otp-28/rebar3

#16 DONE 1.9s

—

I note that 2.3.0 of hex was deployed today???

I could use some help on what to change.

2

I changed the command to install Hex to force version to 2.2.2.

I appear to be able to deploy now!

Does this indicate an issue with my config or a bug in Hex 2.3.0 ? Happy to correct what may be missing!

3

I reported this issue in the Hex repo since it seems somehow related to the Hex changes:

2 Likes
4

@tjchambers the hex team is actively working on it.

Until they fix it, you can downgrade the hex version: mix local.hex 2.2.2

5

Thanks - that is what I did. It seems to have worked.

1 Like
6

They released v2.3.1 and that fixes the issue.

2 Likes
7

Thanks again. Can confirm Hex 2.3.1 resolves this issue.

2 Likes