Should mix.lock be part of the public repository and package?

Should mix.lock be part of the Git public repository and Hex package?

Or should it be added to .gitignore?

It should be part of the public git repository. It ensures that new developers to the library start from a consistent set of deps that are known to work, and is also critical for reliable builds in a CI.

Mix dep resolution ignores dependency mix.lock files so there is no concern about it causing issues when the library is used as a dep.

5 Likes

Thank you @benwilson512 . That is a really clear explanation.