Skip to content

GitHub Packages publishes mislabelled "npm" with dead npmjs.com link #123

@Shtian

Description

@Shtian

Summary

Minor issue experienced when publishing npm packages to GitHub Packages: the package link in the release notes points to a non-existent package on npmjs.com instead of linking to the package on GitHub, when publishing to the npm.pkg.github.com npm-registry. The same wrong label appears in bumpy status and bumpy ci plan output.

Tested with @varlock/bumpy@1.14.0.

Links

Notes

I spent some tokens creating a quick minimal repro case here that illustrates the issue. It includes some suggested fixes. I guess you can quickly spot if the fixes are viable or not. The unused _registry argument in buildPublishUrl leads me to believe this might just be a feature yet to be implemented :)

If the fix is straight forward as suggested I could go ahead and create a PR, but lmk if its just a misconfigured setup from my side.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions