Sync mix.lock with req ~> 0.7 constraint - #149
Merged
Merged
Conversation
PR #145 bumped the mix.exs constraint without the lockfile, so mix deps.get silently re-resolved req on every CI run while local builds refused to compile. Locks req 0.7.2. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR #145 bumped the
reqconstraint inmix.exsto~> 0.7but didn't updatemix.lock(still pinned 0.6.2). CI stayed green becausemix deps.getsilently re-resolves the unsatisfied lock entry on every run — but local builds fail with "the dependency does not match the requirement", and the lockfile no longer pins what actually ships. This locks req 0.7.2.Verified:
mise run test930 passed, dialyzer clean.🤖 Generated with Claude Code