Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Allow for resolution of NPM registry paths that match upstream (#21568) #21723

Merged
merged 3 commits into from
Nov 9, 2022
Merged

Allow for resolution of NPM registry paths that match upstream (#21568) #21723

merged 3 commits into from
Nov 9, 2022

Commits on Nov 8, 2022

  1. Allow for resolution of NPM registry paths that match upstream (go-gi… 

    …tea#21568)

Backport (go-gitea#21568)

This PR fixes issue go-gitea#21567 allowing for package tarball URLs to match
the upstream registry (and GitLab/JFrog Artifactory URLs). It uses a
regex to parse the filename (which contains the NPM version) and does a
fuzzy search to pull it out. The regex was built/expanded from
http://json.schemastore.org/package,
https://github.com/Masterminds/semver, and
https://docs.npmjs.com/cli/v6/using-npm/semver and is testable here:
https://regex101.com/r/OydBJq/5

Co-authored-by: Lunny Xiao <[email protected]>
    @Racer159 @lunny
    Racer159 and lunny committed Nov 8, 2022
    Configuration menu
    Copy the full SHA
    32a5288 View commit details
    Browse the repository at this point in the history

  2. Add changes needed to make backport function

    @Racer159
    Racer159 committed Nov 8, 2022
    Configuration menu
    Copy the full SHA
    af29b8a View commit details
    Browse the repository at this point in the history

Commits on Nov 9, 2022

  1. Merge branch 'release/v1.17' into backport-21568-v1.17

    @lunny
    lunny authored Nov 9, 2022
    Configuration menu
    Copy the full SHA
    6a93329 View commit details
    Browse the repository at this point in the history