mirror of
https://github.com/renovatebot/renovate.git
synced 2026-10-31 17:51:49 +00:00
Jamie Tanna
9303449af1
While looking at the fix for `actions/setup-java`, we noticed that `erlef/setup-beam` may also be affected, as it notes: > values like `22.x`, or even `>22`, are also accepted, and we attempt > to resolve them according to semantic versioning rules As these fall back to `semver-coerced`, Renovate then raises a PR rewriting the range into a full version, which isn't the intent. We can use `npm` versioning for the Elixir, Gleam and rebar3 dependencies. This deliberately leaves `otp-version` alone: Erlang/OTP releases 4-component versions (e.g. `26.2.5.3`) which aren't valid semver, so `npm` versioning would discard those releases entirely. Resolving that needs a versioning which handles both the 4-component versions and the ranges, which is left as a follow-up. Co-authored-by: Claude Opus 5 <jamie.tanna+claude-code@mend.io>