-
Notifications
You must be signed in to change notification settings - Fork 348
Release 3.10.0 #863
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
Comments
Well I tried but it seems like the token is not valid anymore:
(See job: https://travis-ci.org/github/pytest-dev/pytest-django/jobs/721042875). So now it's a bit of a mess with the release committed and tagged but not published to PyPI... @blueyed and @pelme: according to https://pypi.org/project/pytest-django/ you are the users who have permission to publish to PyPI. Do you think you could manually publish the wheel, or update the travis token maybe? Sorry for the mess, I hoped it would work. |
@bluetech if you're using |
It is using this: Lines 72 to 83 in 7474f9b
|
I'm sorry, I can't help you with that. |
(From https://github.com/pytest-dev/pytest/issues/7585#issuecomment-691510957): @pelme could you add me and/or @bluetech as publishers on PyPI? We can take it from there (my username is also |
Sorry for the delay. I have added @nicoddemus as owner on PyPI now. I did not know @bluetech 's PyPI username but please reply here and I will add you too! Thank you 🙏 and let me know if I can be of any other help. |
@pelme Great, thanks! My PyPI username is |
@bluetech Awesome! You are now invited on PyPI. |
3.10.0 is released to PyPI now. Note I made the upload locally; I tried to update the token in the travis file but when trying to encrypt the new token it gives some error about the token being too long... Will find some time to investigate before the next release though. Maybe just switch to github actions? |
Sounds like a good idea. You can then store the keys in github's secret store. |
There are some compat fixes which would be nice to get out:
I have never made a release here before, but if I understand correctly, all that's needed is to push a changelog update and tag it, and it is published automatically using @blueyed's PyPI token.
I will do it in a few days, unless someone objects (or volunteers).
The text was updated successfully, but these errors were encountered: