-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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): use registry v2 for packages rather than hex.pm http API #29756
base: main
Are you sure you want to change the base?
feat(hex): use registry v2 for packages rather than hex.pm http API #29756
Conversation
Leaving this as a draft until there's an answer for this #29622 (comment) I am no TS expert, so please feel free to jump in and fix up whatever can be done better. |
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.
reduce fixtures, we don't need all versions for testing, ~3 are enough. ensure the tgz file is at minimum too
Is this strictly necessary? The tgz has the registry version of the package wrapped in a signed wrapper. I don't have any way to create a version with less releases in it that would have a valid signature. I can try to find a different package as an example but this is one of the rare ones with retirements. |
Mix changes split to #29775 |
6f0e4ee
to
97ceb1d
Compare
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
ef75883
to
814dbe7
Compare
Changes
registryAliases
for private repo/registry mappingmix.repo add
in mix manager for private reposContext
#29622
This changes the
hex
datasource to use hex registry v2 for package management. Hex registries are not required to implement an http API likehex.pm
has, so the prior implementation prevented updating of packages in private repos such as oban pro. Additionally, due to the way mix works when updating dependencies,mix.lock
files could not be updated when such a dependency existed and the mix manager ranmix deps.update <<updated packages>>
.In order to keep as much parity with the prior implementation, hex.pm is used for supplemental package metadata where possible.
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: