ci: tolerate upstream mix.lock drift#522
Merged
Merged
Conversation
CI's `mix deps.get --check-locked` fast-fails whenever any transitive dep publishes a newer compatible patch after the lock was committed -- a recurring false failure that reds every PR (and master) within minutes of an upstream release (ex_ast, then phoenix_live_view, ...). Relax the two ci-unified.yml install steps to `mix deps.get --check-locked || mix deps.get`: prefer the committed lock, but fall back to a plain resolve on pure upstream drift instead of failing the pipeline. The pre-commit hook and `mix raxol.check` still guard genuinely uncommitted lock changes locally. Also refresh the lock to current (phoenix_live_view 1.2.6 -> 1.2.7) so the common path stays reproducible.
Unified Regression Test ResultsWorkflow: Unified Regression Testing Performance ResultsFound 1 performance result(s) Memory ResultsFound 3 memory result(s) Targets
|
This was referenced Jul 13, 2026
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.
Problem
CI's
mix deps.get --check-locked(inci-unified.yml, Setup & Cache + the macOS/Windows Test matrix) fast-fails whenever a transitive dep publishes a newer compatible patch after the lock was committed. The committed lock lags the Hex registry within minutes of an upstream release, so this reds every PR and master on a rolling basis:ex_ast 0.12.9 → 0.12.10blocked Graduate raxol_symphony: :graph_parallel + 0.2.0 packaging #516 and the four open fork PRs.phoenix_live_view 1.2.6 → 1.2.7re-blocked them.None of these are code defects — every failing check is just the lock guard tripping on upstream drift.
Fix
Relax the two
ci-unified.ymlinstall steps to:Prefer the committed lock (so the reproducible path is unchanged when the lock is fresh), but fall back to a plain resolve on pure upstream drift instead of failing the pipeline. Genuinely uncommitted lock changes are still caught locally by the pre-commit hook and
mix raxol.check.Also refreshes the lock to current (
phoenix_live_view 1.2.6 → 1.2.7).Impact
Unblocks the four open
merklebonsaifork PRs (#513, #514, #515, #520), all of which are green on their actual code and red only on this guard. After this merges, their next run clears.Manual testing