Easier to maintain one or many old lockfiles with blend #744
Conversation
This file contains 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
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.
We have been working in blend an hex package to solve the following problem.
How do you run mix test against different version of the same dependency?
We saw that in surface there is the need to run tests against phoenix_live_view 0.19.x and 0.20.x.
This was solved by adding a mix.lock.old and running mv command in the CI
With blend we attempt to make it easier to maintain the current old lockfile, and at the same time leave the groundwork to make it trivial to test against more (2 or more) lockfiles in the future when a newer version of phoenix_live_view is out".
Let me know if this make sense or you have any feedback about it.
Currently the CI is failing for phoenix_live_view 0.20.14 but there is an open PR to fix that.