> 0.9.8 • Public • Published 7 months ago

https://www.npmjs.com/package/@apache-royale/royale-js
https://www.npmjs.com/package/@apache-royale/royale-js-swf

--
Josh Tynjala
Bowler Hat LLC <https://bowlerhat.dev>


On Wed, Mar 30, 2022 at 9:57 AM Yishay Weiss <yishayj...@hotmail.com> wrote:

> > the npm releases
> are still 0.9.8
>
> Where does that show?
>
> From: Yishay Weiss<mailto:yishayj...@hotmail.com>
> Sent: Wednesday, March 30, 2022 7:56 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: RE: NPM Credentials Problem Blocking Release
>
> Thanks for catching that. I thought we were able to push those with the
> one time passwords, but I guess not. I hope I’ll have time over the weekend
> to look at that.
>
> From: Josh Tynjala<mailto:joshtynj...@bowlerhat.dev>
> Sent: Wednesday, March 30, 2022 7:18 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: Re: NPM Credentials Problem Blocking Release
>
> Hey Yishay, I see that you posted the announcement, but the npm releases
> are still 0.9.8. What's the status on the npm releases? Were you able to
> make progress?
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Tue, Mar 29, 2022 at 3:36 AM Yishay Weiss <yishayj...@hotmail.com>
> wrote:
>
> > Ok, looks like we’ve figured it out for now with a temp password. 2FA
> does
> > not seem to be a requirement. We will update the private list with the
> new
> > credentials when that’s ready.
> >
> > From: Piotr Zarzycki<mailto:piotrzarzyck...@gmail.com>
> > Sent: Tuesday, March 29, 2022 11:18 AM
> > To: Apache Royale Development<mailto:dev@royale.apache.org>
> > Cc: OmPrakash Muppirala<mailto:bigosma...@gmail.com>
> > Subject: Re: NPM Credentials Problem Blocking Release
> >
> > Yes it goes to private as I see...
> >
> > wt., 29 mar 2022 o 09:47 Yishay Weiss <yishayj...@hotmail.com>
> napisał(a):
> >
> > > I’m not sure which email the new password gets sent to. Does it go to
> > > priv...@royale.release.org<mailto:priv...@royale.release.org> ?
> > >
> > > Also, I see some npm requests to do 2FA which we have ignored. It’s
> > > probably best to avoid that if possible to keep the release scriptable.
> > >
> > > @OmPrakash Muppirala<mailto:bigosma...@gmail.com>, are you the one who
> > > set this up? Can you help out?
> > >
> > > Thanks.
> > >
> > >     [exec] http request PUT
> > > https://registry.npmjs.org/-/user/org.couchdb.user:apache-royale-owner
> > >      [exec] info attempt registry request try #1 at 10:39:44 AM
> > >      [exec] http request PUT
> > > https://registry.npmjs.org/@apache-royale%2froyale-js
> > >      [exec] http 401
> > > https://registry.npmjs.org/-/user/org.couchdb.user:apache-royale-owner
> > >      [exec] WARN notice Please check your email for a one-time password
> > > (OTP)
> > >      [exec] WARN adduser Incorrect username or password
> > >      [exec] WARN adduser You can reset your account by visiting:
> > >      [exec] WARN adduser
> > >      [exec] WARN adduser     https://npmjs.org/forgot
> > >      [exec] WARN adduser
> > >      [exec]
> > > C:\dev\release_royale\royale-asjs\npm\release-scripts\publish.js:51
> > >      [exec]                         throw new Error(error);
> > >      [exec]                         ^
> > >      [exec]
> > >      [exec] Error: Error: failed to authenticate: A One Time Password
> > > (OTP) by email is required. :
> -/user/org.couchdb.user:apache-royale-owner
> > >      [exec]     at
> > > C:\dev\release_royale\royale-asjs\npm\release-scripts\publish.js:51:14
> > >      [exec]     at
> > >
> >
> C:\dev\release_royale\royale-asjs\npm\release-scripts\node_modules\npm-registry-client\lib\adduser.js:125:14
> > >      [exec]     at
> > >
> >
> C:\dev\release_royale\royale-asjs\npm\release-scripts\node_modules\npm-registry-client\lib\adduser.js:73:16
> > >      [exec]     at f
> > >
> >
> (C:\dev\release_royale\royale-asjs\npm\release-scripts\node_modules\once\once.js:25:25)
> > >      [exec]     at
> > >
> >
> C:\dev\release_royale\royale-asjs\npm\release-scripts\node_modules\npm-registry-client\lib\request.js:91:10
> > >      [exec]     at
> > >
> >
> C:\dev\release_royale\royale-asjs\npm\release-scripts\node_modules\npm-registry-client\lib\request.js:105:12
> > >      [exec]     at f
> > >
> >
> (C:\dev\release_royale\royale-asjs\npm\release-scripts\node_modules\once\once.js:25:25)
> > >      [exec]     at RegClient.<anonymous>
> > >
> >
> (C:\dev\release_royale\royale-asjs\npm\release-scripts\node_modules\npm-registry-client\lib\request.js:324:12)
> > >      [exec]     at Request._callback
> > >
> >
> (C:\dev\release_royale\royale-asjs\npm\release-scripts\node_modules\npm-registry-client\lib\request.js:216:14)
> > >      [exec]     at Request.self.callback
> > >
> >
> (C:\dev\release_royale\royale-asjs\npm\release-scripts\node_modules\request\request.js:185:22)
> > >      [exec]     at Request.emit (events.js:315:20)
> > >      [exec]     at Request.<anonymous>
> > >
> >
> (C:\dev\release_royale\royale-asjs\npm\release-scripts\node_modules\request\request.js:1154:10)
> > >      [exec]     at Request.emit (events.js:315:20)
> > >     [exec]     at IncomingMessage.<anonymous>
> > >
> >
> (C:\dev\release_royale\royale-asjs\npm\release-scripts\node_modules\request\request.js:1076:12)
> > >      [exec]     at Object.onceWrapper (events.js:421:28)
> > >      [exec]     at IncomingMessage.emit (events.js:327:22)
> > >
> > > BUILD FAILED
> > > C:\dev\release_royale\releasecandidate.xml:1116: The following error
> > > occurred while executing this line:
> > > C:\dev\release_royale\releasecandidate.xml:1400: exec returned: 1
> > >
> > > Total time: 7 minutes 26 seconds
> > >
> > >
> >
> > --
> >
> > Piotr Zarzycki
> >
> >
>
>

Reply via email to