fix(hex/mix): stop suffixing versions with ==
by default
#32539
Closed
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.
Changes
Semantic versions (not ranges) in
mix.exs
files stop getting suffixed with==
, by default.Context
0c06a23#diff-5050def58eaa9d548349c16252d28f932eb05401d5981e867392517f18c18847R80 introduced
==
as an always-present suffix tohex
versions (Hex and Git alike). The problem that comes with this (up until now we'd been updating our PRs "by hand") is that e.g. a dependency like{:k_lib, git: "[email protected]:k/k_lib.git", tag: "v0.0.1"}
gets updated to{:k_lib, git: "[email protected]:k/k_lib.git", tag: "== v0.0.2"}
which is not valid Mix syntax.I was looking at the code and trying to do this optionally but I can't seem to find (does it exist?) a proper option... if I could pass something from
mix
tohex
then I could use that to optionally add the==
, keeping previous behaviour but allowing for the bug fix.Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: