CI fails to publish to npm because of missing OTP
frigus02 opened this issue · comments
- First failure: https://github.com/google/closure-compiler-npm/actions/runs/2428128972
- Most recent failure: https://github.com/google/closure-compiler-npm/actions/runs/2431711905
Error message (manually reformatted to be readable):
npm notice
npm notice 📦 google-closure-compiler-java@20220601.0.0
npm notice === Tarball Contents ===
npm notice 13.1MB compiler.jar
npm notice 666B index.js
npm notice 967B package.json
npm notice 210B readme.md
npm notice === Tarball Details ===
npm notice name: google-closure-compiler-java
npm notice version: 20220601.0.0
npm notice package size: 12.0 MB
npm notice unpacked size: 13.1 MB
npm notice shasum: 0c62d0dafde2e0ec96b46734977454b28042e7e7
npm notice integrity: sha512-7amrWmgqMb0gb[...]7WCyVzfuvEgig==
npm notice total files: 4
npm notice
npm notice Open https://www.npmjs.com/login/5355162b-5634-4e1d-aaa0-499a6b016ded to use your security key for authentication or enter OTP from your authenticator app
npm ERR! code EOTP
npm ERR! This operation requires a one-time password from your authenticator.
npm ERR! You can provide a one-time password by passing --otp=<code> to the command you ran.
npm ERR! If you already provided a one-time password then it is likely that you either typoed
npm ERR! it, or it timed out. Please try again.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/runner/.npm/_logs/2022-06-03T00_45_10_503Z-debug.log
Did anything change recently? Is it possible that the npm account didn't require an OTP previously and it does now?
@ChadKillingsworth This failure seems to be new.
This was due to security changes at npm. New publication tokens had to be issued. Publication is succeeding again.