Skip to content
This repository has been archived by the owner on Apr 23, 2024. It is now read-only.

Use NODE_AUTH_TOKEN instead of old unmaintained npm-cli-login #36

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

sethidden
Copy link
Contributor

No description provided.

run: |
npm install -g npm-cli-login
npm-cli-login -u "${{ secrets.NPM_USER }}" -p "${{ secrets.NPM_PASS }}" -e [email protected] -r https://registrynpm.storefrontcloud.io
registry-url: 'https://registrynpm.storefrontcloud.io'
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the only problem here is that this needs a NODE_AUTH_TOKEN env var present like:

$ echo "NODE_AUTH_TOKEN=$(${{ secrets.NPM_USER }}:${{ secrets.NPM_PASS }} | base64)" >> $GITHUB_ENV

I don't want to base64 the secrets because that way GitHub actions won't protect them against being leaked. It'd be much better to have a convention where you need to pass NODE_AUTH_TOKEN as a secret to this workflow.

The problem is that now we have a convention of having NPM_PASS and NPM_USER separately, so I'd need to write some compat input to the action that selectively uses one or the other.

Or just make a new branch for the newer CI

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant