-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
feat(hex): support update-lockfile strategy #27915
feat(hex): support update-lockfile strategy #27915
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please split this PR in a manager and a versioning part.
@viceice to confirm, would you like me to close this one and submit two PRs that reference this one? |
no, just create one new PR with the changes which need to be merged first. currently don't see if it's versioning or manager, so decide yourself. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
blocked by #27924
This is ready for re-review. I've validated it still works as expected with the code. Reference: https://github.com/pdm-jd/renovate-mix-tests/pulls |
🎉 This PR is included in version 37.405.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Changes
rangeStrategy=update-lockfile
for themix
managermix.exs
to have a realistic structure - no duplicate dependencies with different versionsContext
Closes #13618
Depends on #27924
Documentation (please check one with an [x])
It looks like the documentation for Hex versioning should automatically update to include
update-lockfile
, based ontools/docs/versioning.ts
How I've tested my work (please select one)
I have verified these changes via:
Example PRs created with this code for these dependencies https://github.com/pdm-jd/renovate-mix-tests/pulls