If dependencies in the mix.lock do not match those in mix.exs, *mix deps.get --strict* will exit with an error, instead of updating the mix.lock file.
This is inspired by npm ci <https://stackoverflow.com/questions/52499617/what-is-the-difference-between-npm-install-and-npm-ci> and aims to solve a rather common problem of people updating mix.exs but forgetting to update the mix.lock file. (there are non-obvious situations if you have path dependencies, where updating a dependency version will cascade to every other mix project using it) npm ci is used on the official github action <https://github.com/actions/starter-workflows/blob/main/ci/node.js.yml> for node.js and I think it would be nice to use mix deps.get --strict on the elixir one as well -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/8918d9ca-2fcb-4abd-b28e-f7bf2a00ead1n%40googlegroups.com.
