Only fetch deps compatible for a specific version of Elixir

Questions / Help
1

I’m testing a library with multiple versions of Elixir on my CI. One of my dependencies is specified as a range.

{:poison, ">= 3.1.0 and < 5.0.0", optional: true}

Poison 4.0 is compatible with Elixir 1.6+ while Poison 3.1 is compatible with Elixir 1.3+. When my CI attempts to test in an Elixir 1.3 environment it fails because it’s trying to fetch Poison 4.0.

Is there any way to get around this?

2

I do fear you have to do it like this:

{:poison, cond do           
  Version.match?(System.version, "~> 1.6") -> ">= 3.1.0 and < 5.0.0"
  Version.match?(System.version, "~> 1.3") -> ">= 3.1.0 and < 4.0.0"
end, optional: true}
2 Likes
3

Any idea how hex.pm would handle reporting this?

4

Plug uses a different lock file to test with older dependencies: https://github.com/elixir-plug/plug/blob/master/mix.exs#L15

defmodule Plug.MixProject do
  use Mix.Project

  # ...
  def project do
    [
      # ...
      lockfile: lockfile(),
      # ...
    ]

  defp lockfile() do
    case System.get_env("COWBOY_VERSION") do
      "1" <> _ -> "mix-cowboy1.lock"
      _ -> "mix.lock"
    end
  end
end
3 Likes
5

Are you able to build a different lockfile using mix or will I have to handle it manually?

6

I would update mix.exs and then run mix deps.get to generate the lock file: {:poison, ">= 3.1.0 and < 4.0.0", optional: true}

Then I can rename the lock file, and revert changes on mix.lock and mix.exs.

7

Got it figured out! Thanks @NobbZ and @danschultzer for your help! Went with a combination of your two approaches.

For reference:

2 Likes
8

Hmmm, I wonder if we could add this as tip for library maintainers. I’m not sure what the best place for that would be. Does anyone know?

1 Like
9

This is where I’ve seen library guidelines before:
https://hexdocs.pm/elixir/master/library-guidelines.html

10

GitHub - mimiquate/blend: Tasks to generate and mantain multiple lockfiles might help in mantaining and switching between multiple lockfiles.