Repository navigation
List mirror versions from the configured upstream - #548
Merged
Merged
Conversation
proxy mirror and mirror API jobs listed the versions of unversioned PURLs from the public registries, ignoring upstream.*. They now list them from the configured upstream through the proxy's upstream client, and npm packages from their npm_routes entry. Where the upstream has no listing API, or the ecosystem has no listing at all, the error asks for a version. Refs git-pkgs#524
Contributor
|
This is waiting on git-pkgs/registries#99. The Maven client asks |
registries main streams npm packuments (git-pkgs/registries#109), so listing the versions of packages whose packument is over 10 MiB, such as typescript, no longer fails with "unexpected end of JSON input". It also reads Maven versions from maven-metadata.xml (git-pkgs#114). go.mod points at a pseudo-version of registries main until those are released.
…ersions # Conflicts: # go.mod # go.sum
# Conflicts: # go.mod # go.sum
Merged
simonchrz
added
the
breaking
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
proxy mirror, mirror API jobs and schedules listed the versions of an unversioned PURL from the public registry, whateverupstream.*says. They now list them from the configured upstream, through the proxy's upstream client, soupstream.authand the private address rules apply. npm packages innpm_routesare listed from their route.hex_api), pub, pypi, maven, nuget, composer, cran and brew.composer_routes, and helm, swift, apk and the rest: the error asks for a version instead of the registries error. Fetching those isproxy mirrordoesn't support julia, cran, homebrew, swift, apk, debian or rpm #414.With
PROXY_UPSTREAM_NPM=http://127.0.0.1:1,proxy mirror -dry-run pkg:npm/left-padlisted 15 versions on main and now fails on the unreachable upstream.The second commit bumps registries to main, which streams npm packuments (git-pkgs/registries#109).
proxy mirror -dry-run pkg:npm/typescriptfailed withunexpected end of JSON inputand now lists every version, so this closes #524. go.mod points at a pseudo-version of registries main until the next release; I'll switch it to the tag then.Closes #524.