Mix deps.get --check-locked parameter

[Efesto]

Implements https://groups.google.com/g/elixir-lang-core/c/Jr2CS6o2elo/m/Lq3r5plfBQAJ proposal by introducing --check-locked argument to mix deps.get task.

When set and lockfile needs to be updated, mix deps.get will exit with non-zero status.

The idea is to have a way to prevent a CI pipeline from running successfully when a change in the application deps are not reflected in an update to the lockfile.

Similarly to bundler install --frozen and yarn --frozen-lockfile

TODO

• E2E testing, I need support for this one

[josevalim]

Thank you! I believe this is in the right direction but we need to discuss the name. --no-lockfile-update will most likely be read as "don't update the lockfile" instead of raising. Maybe --strict or --check-locked or --check-up-to-date are better.

[Efesto]

Thank you! I believe this is in the right direction but we need to discuss the name. --no-lockfile-update will most likely be read as "don't update the lockfile" instead of raising. Maybe --strict or --check-locked or --check-up-to-date are better.

How does --frozen-lockfile sound?

[josevalim]

Freeze is not a verb we use in Elixir. I don’t think it would have a meaning to most developers.

[josevalim]

I would say let’s go with —check-locked, because “up to date” also has multiple meaning and —strict is vague. We can also call the internal option :check_locked.

[josevalim]

💚 💙 💜 💛 ❤️