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

Automatic deployment to PyPI #344

Open
jathak opened this issue Apr 2, 2018 · 4 comments
Open

Automatic deployment to PyPI #344

jathak opened this issue Apr 2, 2018 · 4 comments

Comments

@jathak
Copy link
Contributor

jathak commented Apr 2, 2018

It would be nice for this to be auto-deployed whenever we push a new tag

@kavigupta
Copy link
Contributor

@jathak is there a strong reason for this? https://github.com/okpy/ok-client/commits/master/release.py seems to have existed for a while before this issue was created so I assume you found it lacking?

@Sumukh
Copy link
Member

Sumukh commented Dec 27, 2019

release.py is nice but it does mean that for someone to deploy they need to have credentials to PyPi, ok admin access, and a github token (which is possibly a security feature considering clients autoupdate themselves)

@mehrdadn
Copy link
Contributor

Is automatic deployment to PyPI advisable generally? I'm not familiar with what common practice is, but it seems like a potential security concern, as well as leading too easily to mistakes when someone didn't intend to make a release.

@jathak
Copy link
Contributor Author

jathak commented Dec 27, 2019

I think automatic deployment when pushing a tag make sense, giving that's an explicit extra action on top of committing to master. It also ensures that each version released on PyPI matches the tag on GitHub. I don't know what the best practices are for PyPI specifically, but it's definitely common for automated releases to be used for packages on npm and other package managers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants