Publish Elixir Semver requirement with each release about hex HOT 4 CLOSED

It is not enough to put the version requirement in the metadata file. It needs to be in the registry so that we can access it during resolution. We also need to store it with the release as a new column in the database.

We already warn the user if the elixir requirement does not match for a dependency (Mix does this). The idea is to never resolve a package for which the requirement doesn't match. This can of course be overriden with override: true.

from hex.

If we're adding it to the registry will it be backwards compatible with older versions of Hex due to the ETS table structure?

If we never resolve a package, how much warning do we give to the user that this has occurred? Writing to stderr? Killing the process with an exit code >0?

from hex.

If we're adding it to the registry will it be backwards compatible with older versions of Hex due to the ETS table structure?

It will be backwards compatible.

If we never resolve a package, how much warning do we give to the user that this has occurred? Writing to stderr? Killing the process with an exit code >0?

We say that dependency resolution failed and exit.

from hex.

The client now includes the elixir version requirement in the metadata when publishing, there is still lots to do. I will continue to track this in #26.

from hex.