Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broken for initial release #3

Closed
nfischer opened this issue Jun 22, 2016 · 2 comments
Closed

Broken for initial release #3

nfischer opened this issue Jun 22, 2016 · 2 comments
Assignees

Comments

@nfischer
Copy link
Member

This only works to release after the initial npm publish, since it uses npm access collaborators and npm owner ls. It'd be awesome if we could work around this for brand new packages that are being published for the first time.

@nfischer
Copy link
Member Author

I think this will be fixed by the refactor proposed in #5. I'll tentatively take this issue, but will open this back up if it's not resolved.

@nfischer nfischer self-assigned this Jan 25, 2018
@nfischer
Copy link
Member Author

nfischer commented Feb 7, 2018

I believe this is fixed. I haven't tested (no intending to publish new packages), but we can reopen this if the error resurfaces.

@nfischer nfischer closed this as completed Feb 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant