-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Release 22.0 #10726
Comments
I can pick this up, although I won't be around during early Jan (I'm on vacation!); so the only time I would be able to do anything about these would be sometime in mid-Jan/late-Jan. |
Sorry, I really don't want to commit to doing the January release, as I'm likely to be pretty busy. Hopefully I might have more free time later in the year to help out with the releases. |
Is there a documented process to update |
It's covered in the documentation. However, I think we have a nox session for that - We do a pass updating all of our vendored libraries just before a release anyway, so this should get caught then. |
I won’t be around in earlier January either (actually will likely not be around starting from later December). |
Yea, and it should be possible to run the vendoring nox session with an upgrade flag, which automatically tries upgrading things; stopping when a failure occurs in the upgrade process. |
I'm gonna pre-emptively assign myself then. :) If there's any concerns of any other committer wants to step up, just say so. :) |
Cool, this is the plan for the release now. |
@pypa/pip-committers Okay, there's a few PRs that I'd like reviews on.
I think there's agreement on those ideas overall, but... more eyes, a proper review and an easy green tick 🤞🏽 would be much appreciated! I'm leaning toward merging those anyway tho, if there's no availability to do a review. |
Alrighty, looks like we're all set. I'll cut a release over the weekend. :) |
sigh Why is GitHub like this.
|
Alrighty. There were a couple of bugs in the html5lib transition logic, so... I'll cut 22.0.1 sometime later today/this week. |
Hi !! I am trying use lib/python3.8/site-packages/piptools/repositories/pypi.py", line 455, in _setup_logging
assert isinstance(handler, logging.StreamHandler)
AssertionError Maybe I'm missing something?. |
You might want to file an issue against https://github.com/jazzband/pip-tools. That looks like a bug on their end -- they're using pip's internals (something that is not supported) and quite possibly they weren't prepared for #10461. :) |
It's been reported at jazzband/pip-tools#1558. |
Does it make sense to try release candidates for future releases? It makes the release process more complicated, but it might allow people to try out the new version before commiting to a release. |
Released 22.0.1 now! |
@mattip We've done those before, but our experience is that not enough users test them; even when we've done a round of publicity about the release. |
Gonna defer this for next weekend. 🙈 |
22.0.2 is out on PyPI and get-pip.py has been updated. :) |
Thanks for all the work! |
@pradyunsg Should there be a 22.0.2 tag in the repo? |
Yea... I'd accidentally pushed to my fork instead of this repository. Fixed that in the morning (UK). 😅 |
22.0.3 is out, w/ a get-pip.py upgrade. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Please file a separate issue for this, as a bug report. This specific issue is for coordinating the release amongst the maintainers and contributors. |
Released the (hopefully, final!) 22.0.4 bugfix for this release.
If there's a security fix needed, I'm happy to cut it out of band -- until we decide on a 22.1 release manager in April. :) |
We're about three weeks out from a new year! I guess we'd want to cut a 22.0, given how full that milestone is. :)
The text was updated successfully, but these errors were encountered: