Update OTP documentation for dist-tag add by scotttrinh · Pull Request #74 · npm/cli

scotttrinh · 2018-10-03T14:06:23Z

See discussion here: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432

TL;DR:

To be clear, you can specify an existing tag and it’ll change it. If you have 2FA enabled, you do need to specify --otp and if you don’t, you should get a 401 as above.

See discussion here: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432 TL;DR: > To be clear, you can specify an existing tag and it’ll change it. If you have 2FA enabled, you do need to specify `--otp` and if you don’t, you should get a `401` as above.

iarna

This is excellent, thank you!

@scotttrinh

See discussion here: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432 TL;DR: > To be clear, you can specify an existing tag and it’ll change it. If you have 2FA enabled, you do need to specify `--otp` and if you don’t, you should get a `401` as above. Ref: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432 PR-URL: #74 Credit: @scotttrinh Reviewed-By: @iarna Reviewed-By: @zkat

scotttrinh · 2018-10-03T14:06:23Z

See discussion here: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432

TL;DR:

To be clear, you can specify an existing tag and it’ll change it. If you have 2FA enabled, you do need to specify --otp and if you don’t, you should get a 401 as above.

See discussion here: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432 TL;DR: > To be clear, you can specify an existing tag and it’ll change it. If you have 2FA enabled, you do need to specify `--otp` and if you don’t, you should get a `401` as above.

iarna

This is excellent, thank you!

@scotttrinh

See discussion here: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432 TL;DR: > To be clear, you can specify an existing tag and it’ll change it. If you have 2FA enabled, you do need to specify `--otp` and if you don’t, you should get a `401` as above. Ref: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432 PR-URL: #74 Credit: @scotttrinh Reviewed-By: @iarna Reviewed-By: @zkat

scotttrinh · 2018-10-03T14:06:23Z

See discussion here: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432

TL;DR:

To be clear, you can specify an existing tag and it’ll change it. If you have 2FA enabled, you do need to specify --otp and if you don’t, you should get a 401 as above.

See discussion here: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432 TL;DR: > To be clear, you can specify an existing tag and it’ll change it. If you have 2FA enabled, you do need to specify `--otp` and if you don’t, you should get a `401` as above.

iarna

This is excellent, thank you!

@scotttrinh

See discussion here: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432 TL;DR: > To be clear, you can specify an existing tag and it’ll change it. If you have 2FA enabled, you do need to specify `--otp` and if you don’t, you should get a `401` as above. Ref: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432 PR-URL: #74 Credit: @scotttrinh Reviewed-By: @iarna Reviewed-By: @zkat

scotttrinh · 2018-10-03T14:06:23Z

See discussion here: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432

TL;DR:

To be clear, you can specify an existing tag and it’ll change it. If you have 2FA enabled, you do need to specify --otp and if you don’t, you should get a 401 as above.

See discussion here: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432 TL;DR: > To be clear, you can specify an existing tag and it’ll change it. If you have 2FA enabled, you do need to specify `--otp` and if you don’t, you should get a `401` as above.

iarna

This is excellent, thank you!

@scotttrinh

See discussion here: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432 TL;DR: > To be clear, you can specify an existing tag and it’ll change it. If you have 2FA enabled, you do need to specify `--otp` and if you don’t, you should get a `401` as above. Ref: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432 PR-URL: #74 Credit: @scotttrinh Reviewed-By: @iarna Reviewed-By: @zkat

scotttrinh · 2018-10-03T14:06:23Z

See discussion here: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432

TL;DR:

To be clear, you can specify an existing tag and it’ll change it. If you have 2FA enabled, you do need to specify --otp and if you don’t, you should get a 401 as above.

See discussion here: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432 TL;DR: > To be clear, you can specify an existing tag and it’ll change it. If you have 2FA enabled, you do need to specify `--otp` and if you don’t, you should get a `401` as above.

iarna

This is excellent, thank you!

@scotttrinh

See discussion here: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432 TL;DR: > To be clear, you can specify an existing tag and it’ll change it. If you have 2FA enabled, you do need to specify `--otp` and if you don’t, you should get a `401` as above. Ref: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432 PR-URL: #74 Credit: @scotttrinh Reviewed-By: @iarna Reviewed-By: @zkat

scotttrinh · 2018-10-03T14:06:23Z

See discussion here: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432

TL;DR:

To be clear, you can specify an existing tag and it’ll change it. If you have 2FA enabled, you do need to specify --otp and if you don’t, you should get a 401 as above.

See discussion here: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432 TL;DR: > To be clear, you can specify an existing tag and it’ll change it. If you have 2FA enabled, you do need to specify `--otp` and if you don’t, you should get a `401` as above.

iarna

This is excellent, thank you!

@scotttrinh

See discussion here: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432 TL;DR: > To be clear, you can specify an existing tag and it’ll change it. If you have 2FA enabled, you do need to specify `--otp` and if you don’t, you should get a `401` as above. Ref: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432 PR-URL: #74 Credit: @scotttrinh Reviewed-By: @iarna Reviewed-By: @zkat

scotttrinh · 2018-10-03T14:06:23Z

See discussion here: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432

TL;DR:

To be clear, you can specify an existing tag and it’ll change it. If you have 2FA enabled, you do need to specify --otp and if you don’t, you should get a 401 as above.

See discussion here: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432 TL;DR: > To be clear, you can specify an existing tag and it’ll change it. If you have 2FA enabled, you do need to specify `--otp` and if you don’t, you should get a `401` as above.

iarna

This is excellent, thank you!

@scotttrinh

See discussion here: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432 TL;DR: > To be clear, you can specify an existing tag and it’ll change it. If you have 2FA enabled, you do need to specify `--otp` and if you don’t, you should get a `401` as above. Ref: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432 PR-URL: #74 Credit: @scotttrinh Reviewed-By: @iarna Reviewed-By: @zkat

scotttrinh · 2018-10-03T14:06:23Z

See discussion here: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432

TL;DR:

To be clear, you can specify an existing tag and it’ll change it. If you have 2FA enabled, you do need to specify --otp and if you don’t, you should get a 401 as above.

See discussion here: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432 TL;DR: > To be clear, you can specify an existing tag and it’ll change it. If you have 2FA enabled, you do need to specify `--otp` and if you don’t, you should get a `401` as above.

iarna

This is excellent, thank you!

@scotttrinh

See discussion here: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432 TL;DR: > To be clear, you can specify an existing tag and it’ll change it. If you have 2FA enabled, you do need to specify `--otp` and if you don’t, you should get a `401` as above. Ref: https://npm.community/t/npm-dist-tag-add-with-2fa-enabled-fails-for-non-latest-tag-with-500/2432 PR-URL: #74 Credit: @scotttrinh Reviewed-By: @iarna Reviewed-By: @zkat

scotttrinh requested a review from a team as a code owner October 3, 2018 14:06

iarna approved these changes Oct 4, 2018
View reviewed changes

zkat added the docs label Nov 13, 2018

zkat approved these changes Nov 13, 2018
View reviewed changes

zkat changed the base branch from latest to release-nextNovember 13, 2018 15:01

zkat merged commit 8a6ecc7 into npm:release-nextNov 26, 2018

snyk-bot mentioned this pull request Jun 16, 2022
[Snyk] Upgrade @npmcli/run-script from 3.0.2 to 3.0.3 LadyK-21/cli#1
Open

311821105 mentioned this pull request May 13, 2023
[Snyk] Upgrade retry from 0.12.0 to 0.13.1 311821105/cli#2
Open

github-actionsBot added a commit to Kevinlee7250/cli that referenced this pull request Jun 23, 2026
📊 대시보드 데이터 업데이트 (npm#74)
a3fbd25

github-actionsBot added a commit to Kevinlee7250/cli that referenced this pull request Jul 1, 2026
🤖 봇 응답 (npm#74)
ba91213

github-actionsBot added a commit to Kevinlee7250/cli that referenced this pull request Jul 10, 2026
🔧 자동 수리 완료 (npm#74)
26e4922

github-actionsBot added a commit to Kevinlee7250/cli that referenced this pull request Aug 1, 2026
🔥 트렌드 선점 후보 갱신 (npm#74)
489d89b