Renovate's bug on widen strategy when version specification is `~> 0.x`

Hey!

I’ve found, reproduced and made a fix for a mildly annoying bug in Renovate.

It created redundant ~> 0.x or 0.x+1 in mix.exs, e.g. Pull requests · tomekowal/renovate-hex-widen-repro · GitHub

The maintainers use Github’s discussions to report bugs, so I created one Elixir libraries using widen strategy and `~> 0.x` version spec result in nonsensical `~> 0.x or ~> 0.x+1` · renovatebot/renovate · Discussion #45393 · GitHub

If you encountered the issue (or use Renovate with Elixir in general), please upvote the discussion, so that Renovate maintainers can see it in the sea of other issues :slight_smile:

1 Like