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

Deploy failed (invalid NPM token?) #275

Closed
mnkhouri opened this issue Aug 13, 2018 · 5 comments
Closed

Deploy failed (invalid NPM token?) #275

mnkhouri opened this issue Aug 13, 2018 · 5 comments
Assignees
@lijunle
Milestone
0.6.10

Comments

@mnkhouri
Copy link
Member

mnkhouri commented Aug 13, 2018 •
edited

The deploy for version 0.6.10-beta.0 failed, see log here. NPM revoked all tokens 1 months ago, so I think our token needs to be updated

For new token: https://www.npmjs.com/settings/lijunle/tokens

To update travis: travis encrypt api_key ="TOKEN VALUE" --add
@mnkhouri mnkhouri added this to the 0.6.10 milestone Aug 17, 2018
@mnkhouri
Copy link
Member Author

@lijunle might you have a chance to update this token this weekend? We can then get 0.6.10 released :)

@lijunle
Copy link
Member

lijunle commented Aug 19, 2018

@mnkhouri I just added you to the npm package maintainer list.

I don't find @LinusU user name in npm. What is your name?

@mnkhouri mnkhouri mentioned this issue Aug 20, 2018
Merged
@mnkhouri
Copy link
Member Author

Thanks @lijunle !

@mnkhouri
Copy link
Member Author

@LinusU I noticed your npm username is linusu -- I have invited you to the maintainer list as well

@mnkhouri
Copy link
Member Author

deploy is still failing 🤔 (log here)

image

I can't spot anything obviously wrong, so I'll check it out further this week.

I originally had my 2fa settings to "auth + publish", but I changed them to just "auth" then immediately kicked off this build. It's possible the 2fa change hadn't propagated yet, so my first troubleshooting step will be to just kick off the build again.

@mnkhouri mnkhouri reopened this Aug 20, 2018
mnkhouri added a commit that referenced this issue Aug 20, 2018
@mnkhouri
Update NPM tokens with correct permissions
7586540 
NPM package deployments are still failing, even with an updated token (see #275). One [issue comment](travis-ci/travis-ci#9403 (comment)) suggests that it is not sufficient to turn off 2fa-for-publishing after the token (as I did), but rather that the token must be created while 2fa-for-publishing is turned off.

Fixes #275
@mnkhouri mnkhouri mentioned this issue Aug 20, 2018
Merged
mnkhouri added a commit that referenced this issue Sep 8, 2018
@mnkhouri
Update NPM tokens with correct permissions (#279)
a5fea70 
NPM package deployments are still failing, even with an updated token (see #275). One [issue comment](travis-ci/travis-ci#9403 (comment)) suggests that it is not sufficient to turn off 2fa-for-publishing after the token (as I did), but rather that the token must be created while 2fa-for-publishing is turned off.

Fixes #275
@wv91364210zhuozh wv91364210zhuozh mentioned this issue Dec 25, 2022
Open
@snyk-bot snyk-bot mentioned this issue Apr 25, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lijunle lijunle

Labels
None yet
Projects
None yet
Milestone
0.6.10
Development

No branches or pull requests
2 participants
@lijunle @mnkhouri