Skip to content

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

Closed
bluetech opened this issue Aug 22, 2020 · 11 comments
Closed

Release 3.10.0 #863

bluetech opened this issue Aug 22, 2020 · 11 comments

Comments

@bluetech
Copy link
Member

There are some compat fixes which would be nice to get out:

  • Fix for pytest-xdist 2
  • Fix for pytest 6 (internal pytest-django tests only)
  • Fix for Django 3.2

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).

@bluetech bluetech changed the title Release 3.9.0 Release 3.10.0 Aug 25, 2020
@bluetech
Copy link
Member Author

Well I tried but it seems like the token is not valid anymore:

HTTPError: 403 Forbidden from https://upload.pypi.org/legacy/
Invalid or non-existent authentication information. See https://pypi.org/help/#invalid-auth for more information.

(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.

@mgorny
Copy link

mgorny commented Aug 27, 2020

@bluetech if you're using setup.py upload, then try twine upload instead. It seems that the former was broken recently, at least for my projects.

@bluetech
Copy link
Member Author

It is using this:

- stage: release
script: skip
install: skip
after_success: true
deploy:
provider: pypi
user: blueyed
password:
secure: "FY7qbX/N0XRcH8hVk00SsQWvNIkuxKvY7Br4ghRnHvleHG3YulJ7WbJnik+9eoBGeMfJeNyzBfVjpeo1ZIq9IZBiyTdNfG/sZFsC5LOoG/CPxPH3nD9JktI2HoBMnlSbGg/MMHjY+wXuOY647U/3qNedcnQmGztYt6QWi5DRxu8="
on:
tags: true
distributions: "sdist bdist_wheel"

@mgorny
Copy link

mgorny commented Aug 27, 2020

I'm sorry, I can't help you with that.

@D3X
Copy link

D3X commented Sep 7, 2020

@bluetech @pelme any chance you could help with getting this released?

@nicoddemus
Copy link
Member

(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 nicoddemus). @bluetech what's yours?

@pelme
Copy link
Member

pelme commented Sep 12, 2020

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.

@bluetech
Copy link
Member Author

@pelme Great, thanks!

My PyPI username is bluetech (just created actually). Once added, I'll complete this release.

@pelme
Copy link
Member

pelme commented Sep 12, 2020

@bluetech Awesome! You are now invited on PyPI.

@bluetech
Copy link
Member Author

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?

@D3X
Copy link

D3X commented Sep 15, 2020

Maybe just switch to github actions?

Sounds like a good idea. You can then store the keys in github's secret store.

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

5 participants