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.

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

Workflow fails to publish to GitHub Package Registry if repo owner login casing does not match scope casing #38

Closed
JamesMGreene opened this issue Aug 21, 2019 · 0 comments · Fixed by #39

Comments

@JamesMGreene
Copy link
Contributor

I've been testing out an Action I was building today and having issues when verifying a step to publish the package to the GitHub Package Registry, which instead attempts to publish the package to the original NPM Registry:

https://github.com/JamesMGreene/test-repo/runs/199833215

After trying to track down the issue for longer than I care to mention as I went down a few incorrect rabbit holes, I believe the root cause is pretty simple: my GitHub username has uppercase letters in it but my NPM scoped package name, by necessity for validation, is all lowercased.

This creates a casing mismatch between the .npmrc file contents that get generated by the setup-node@v1 Action and the scope used by npm publish in a later Step. Some highlights from the Workflow Run logs:

Screen Shot 2019-08-21 at 5 43 09 PM

Luckily, the fix for this should also be pretty simple: to lowercase the repo owner's login scope that gets written to the .npmrc file. 👌

damccorm pushed a commit that referenced this issue Aug 22, 2019
deining pushed a commit to deining/setup-node that referenced this issue Nov 9, 2023
…-dev

docs: add brahma-dev as a contributor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant