-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom package name for Hex dependency #32972
Comments
SourceUrl is incorrect. PackageName is correct |
but datasource fetches release based on packageName |
Yes, exactly. If you set both depName and packageName then packageName will be used for the datasource lookup |
what do you think of: https://github.com/renovatebot/renovate/pull/32984/files |
Does it work end to end? Can you share a public repo demonstrating it? |
dunno exactly the best way to demonstrate it, but using the reproduction repo I:
how do you see it? |
Please also find an example where it success upgrades an alias like this, eg. from 2.0.0 to 2.0.1 |
ok i think this new PR summarises the thing nicely: |
🎉 This issue has been resolved in version 39.61.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Discussed in #32834
Originally posted by bernardo-martinez December 1, 2024
Tell us more.
What would you like Renovate to be able to do?
In Mix in elixir you can setup a dependency with a different name than the default one fetched from hex.pm, see: https://hex.pm/docs/usage#options
For example:
This will fetch the
grpc_gun
dependency from hex.pm located here: https://hex.pm/packages/grpc_gun but will treat it locally asgun
If you have any ideas on how this should be implemented, please tell us here.
I think the mix manager should have an additional regex to search for such
hex:
option and use it to setPackageDependency.sourceUrl
accordingly, which then would be used in the hex versioning?Is this a feature you are interested in implementing yourself?
Yes, just need some discussion and guidance first
Reproduction: renovate-reproductions/32834#1
The text was updated successfully, but these errors were encountered: