fix: support sparse registries #422
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
robjtede
commented
Sep 10, 2025
Collaborator
|
Thank you for this PR, I have been extremely busy of late but hope to have a slightly clearer schedule within a week or two and will do my utmost to help this move forward and see a new version of |
robjtede
force-pushed
the
fix-priv-registries
branch
from
f01f8c2 to
67a31c8
Compare
Contributor
Author
|
New setup seems to work for all cases we've tested, but I'm having a hard time explaining why this change would have that effect. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've confirmed this simple fix enables support for my workplace's private registry (sparse index, but I think this fix is applicable to all source types).