search

angular-ui / ui-scroll

Unlimited bidirectional scrolling over a limited element buffer for AngularJS applications
http://angular-ui.github.io/ui-scroll/demo/
MIT License
327 stars 107 forks source link

v1.7.2 is not being published #212

Closed dhilt closed 6 years ago

dhilt commented 6 years ago

@angular-ui/ui Hi! I've pushed a new version of the ui-scroll lib to the angular-ui-scroll repo more than 1 day ago. This includes v1.7.2 github release and previously that was enough to have a new version available via npm. But v1.7.2 is still unpublished (v1.7.1 is the latest npm package version) and I don't understand how to force it. I tried to publish it be myself but I have no permission:

npm whoami dhilt npm publish npm ERR! publish Failed PUT 403 npm ERR! You do not have permission to publish "angular-ui-scroll". Are you logged in as the correct user? : angular-ui-scroll

How the process of publishing to npm works in angular-ui? Is there a chance to get appropriate permission to publish new versions by myself?

thgreasi commented 6 years ago

Oh, the npm revoke of all tokens might be the thing behind this... We should probably update all our npm tokens on the CIs that where configured for auto-publishing.

dhilt commented 6 years ago

@PowerKiKi Hi! I see your name in travis deploy config section and looks like api_key secure token is invalid now, so angular-ui-scroll v1.7.2 can't be published. Could you create and send me another one? Or if it is appropriate grant me with publishing rights. Since I'm the only maintainer of the angular-ui-scroll package for more than 2 years, I guess, having publishing rights does make sense...

ProLoser commented 6 years ago

@dhilt do you have an npm account? I can add you to the registry for this package and you should be able to make the necessary changes yourself. If possible I'd prefer to store secure tokens on Travis instead of in the repo (assuming ownership permissions from Github transfer to Travis).

PowerKiKi commented 6 years ago

@dhilt I added you as maintainer for this package on npm. That should let you fix it by yourselves.

I don't really remember where the token came from or why it stopped working, but feel free to replace my name with yours if need be.

dhilt commented 6 years ago

@PowerKiKi @ProLoser Thanks! I was able to publish new version with npm publish. Regarding tokens and auto-publishing I would follow the official guide https://docs.travis-ci.com/user/deployment/releases/, but I will try to transfer secure token to Travis environment variables