git-tags datasource is adding unnessesary "==" for the newValue update with utilized with the Elixir Manager #31998
Replies: 1 comment
-
Please link the discussion/issue it is the duplicate of. It will help other users. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
How are you running Renovate?
Self-hosted Renovate
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
Docker - renovate:38.21
Please tell us more about your question or problem
When Renovate runs with the elixir manager and finds any dependencies that utilize git tags for their versions, it will produce a result with an incorrect tag when the tag is set to a static matched value.
In the following example, if there is a service that pins a tag that is a version, then the end result pre-appends a "==" sign to the proposal.
An example of a mix.exs file being updated.
Before Proposal
mix.exs file:
After Proposal:
This PR contains the following updates:
1.7.0
->== 1.9.1
2.4.0
->== 2.6.0
End result of the proposal for the mix.exs file:
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions