Yes, the solution here is to publish all the packages again, and ignore errors from ones that have already been published via:
npx lerna exec --no-bail -- npm publish Best, Paul > On Mar 24, 2019, at 2:10 PM, Krisztián Szűcs <szucs.kriszt...@gmail.com> > wrote: > > Hi Kou, > > Paul has already added me, and I was trying to publish the > packages, but it fails with: > 19 verbose stack Error: 403 Forbidden - PUT > https://registry.npmjs.org/@apache-arrow%2fes2015-umd - You cannot publish > over the previously published versions: 0.4.1. > > It seems like the script has updated three of the packages: > https://www.npmjs.com/settings/apache-arrow/packages > > And now it fails to publish again. > Any suggestions? > > On Sun, Mar 24, 2019 at 10:06 PM Kouhei Sutou <k...@clear-code.com> wrote: > >> Hi, >> >> I've published 0.4.1: >> https://www.npmjs.com/package/apache-arrow/v/0.4.1 >> >> (It seems that "npx lerna exec -- npm publish" in >> npm-release.sh doesn't work with 2FA enabled account. I >> couldn't input one time password from the standard input. I >> passed one time password by --otp option: npm publish --otp OTP) >> >> Krisztian, could you tell me your user name at mpmjs? I'll >> add you to maintainers. >> >> >> Thanks, >> -- >> kou >> >> In <cahm19a6jbjrcm4vu0qcbf3lrb3p477yvzngsaob0pe+ewjj...@mail.gmail.com> >> "Re: [VOTE] Release Apache Arrow JS 0.4.1 - RC1" on Sun, 24 Mar 2019 >> 19:27:25 +0100, >> Krisztián Szűcs <szucs.kriszt...@gmail.com> wrote: >> >>> Hi All, >>> >>> The vote carries with 3 binding +1 votes. Thanks to everyone for >>> helping verify the release! >>> >>> I've published the release to the Apache dist system [1], however >>> I don't have rights to push the NPM package [2]. >>> Could someone either publish it to NPM or grant me rights? >>> >>> Thanks, Krisztian >>> >>> [1]: https://dist.apache.org/repos/dist/release/arrow/arrow-js-0.4.1/ >>> [2]: https://www.npmjs.com/package/apache-arrow >>> >>> On Thu, Mar 21, 2019 at 10:19 PM Brian Hulette <hulet...@gmail.com> >> wrote: >>> >>>> +1 (non-binding) >>>> >>>> Ran `dev/release/js-verify-release-candidate.sh 0.4.1 1` with Node >> v11.12.0 >>>> >>>> >>>> On Thu, Mar 21, 2019 at 1:54 PM Krisztián Szűcs < >> szucs.kriszt...@gmail.com >>>>> >>>> wrote: >>>> >>>>> +1 (binding) >>>>> >>>>> Ran `dev/release/js-verify-release-candidate.sh 0.4.1 1` >>>>> with Node v11.12.0 on OSX 10.14.3 and it looks good. >>>>> >>>>> On Thu, Mar 21, 2019 at 8:45 PM Krisztián Szűcs < >>>> szucs.kriszt...@gmail.com >>>>>> >>>>> wrote: >>>>> >>>>>> Hello all, >>>>>> >>>>>> I would like to propose the following release candidate (rc1) of >> Apache >>>>>> Arrow JavaScript version 0.4.1. This is the second release >> candidate, >>>>>> including the fix for node version requirement [3]. >>>>>> >>>>>> The source release rc1 is hosted at [1]. >>>>>> >>>>>> This release candidate is based on commit >>>>>> e9cf83c48b9740d42b5d18158e61c0962fda59c1 >>>>>> >>>>>> Please download, verify checksums and signatures, run the unit >> tests, >>>> and >>>>>> vote >>>>>> on the release. The easiest way is to use the JavaScript-specific >>>> release >>>>>> verification script dev/release/js-verify-release-candidate.sh. >>>>>> >>>>>> [ ] +1 Release this as Apache Arrow JavaScript 0.4.1 >>>>>> [ ] +0 >>>>>> [ ] -1 Do not release this as Apache Arrow JavaScript 0.4.1 >> because... >>>>>> >>>>>> >>>>>> How to validate a release signature: >>>>>> https://httpd.apache.org/dev/verification.html >>>>>> >>>>>> [1]: >>>>>> >>>> https://dist.apache.org/repos/dist/dev/arrow/apache-arrow-js-0.4.1-rc1/ >>>>>> [2]: >>>>>> >>>>> >>>> >> https://github.com/apache/arrow/tree/e9cf83c48b9740d42b5d18158e61c0962fda59c1 >>>>>> [3]: https://github.com/apache/arrow/pull/4006/ >>>>>> >>>>> >>>> >>
