Hey Marcelo, thanks for Blend , it’s awesome.

I just merged Surface’s PR and added it to Surface Catalogue

blend/premix.exs is very powerful, I could make custom modifications that Surface Catalogue needed.

Blend makes working with a local copy of Surface simple (BLEND=local mix ...) and fast because each blend has it’s own deps and _build directories.

There is a new article showing how to add blend to your existing package.

Hi Eiji,

For example in Github Actions you can achieve 1 and 2 using the matrix feature with blend.

We have been using blend in candlex for testing against different version of nx (0.6 and 0.7 in this case)

Initial implementation and follow up

At the end of the day it would look like this in your CI workflow

      matrix:
         include:
           - elixir_version: 1.16.0
             otp_version: '26.2.1'
             lint: true
           - elixir_version: 1.15.7
             otp_version: '25.3.2.8'
           - elixir_version: 1.15.7
             otp_version: '25.3.2.8'
             blend: "nx06"

You can take a look at the full CI workflow here

I only read this post and have few questions:

1. Do you support different Erlang and Elixir versions as well? (asdf support for example)
2. Does it only tests code or can it also detect if current project compiles with or without warnings?
3. By using your package can I detect minimum supported package version and also minimum supported package version excluding soft-deprecate warnings?

I guess that the answer for all is no, but I may be wrong. Anyway, do you think about those points? Are they interesting features to add to your hex package?