Release 26.0 (January)

[ichard26]

pip 25.3 was a success (and shockingly quiet). Now it's time to start the development cycle for 26.0.

In terms of what didn't happen in time for 25.3:

• Install build dependencies in-process #13450
• Deprecation: non-bare project name in URL/VCS egg= fragments #13157
• Implement --uploaded-prior-to #13625

@pypa/pip-committers who has bandwidth to be the RM for this release? If needed, I can be the RM, although if someone wants to be the RM, I'm all ears. I have hit-or-miss availability in November, and effectively zero for the first half of December. I'll have decent availability afterwards.

[ichard26]

As a reminder, I will be largely unavailable from now on until the second half of December. My priority once I'm back is to review PRs in the milestone and also get #13450 actually all finished.

[notatallshaw]

I'm also going to take a step back from open source for most of December to focus on family tasks, if I get spare time I'll try and focus on reviews. There's a good chance I'll be free to do the next release but I'll confirm early January if no one else has stepped up.

[pfmoore]

I'm willing to cover the January release if no-one else is, but like others, I have very little spare time right now. So if I do end up doing it, it'll be very much a minimal "release what's available" exercise, with anything that's not ready being pushed back to 26.1.

[vfazio]

Selfish request: any chance of including #13725 in 26.x?

[notatallshaw]

Selfish request: any chance of including #13725 in 26.x?

Apologies, I meant to reply to your PR when you opened it. I will put it on my review list but I am currently travelling for the holidays and I've already committed to a few PR reviews for 26.0, but I will try my best to take a look if no one else does.

[pfmoore]

I'm not going to be able to cover 26.0. Other commitments don't leave me enough time, sorry. Hopefully, someone else can step up.

[pradyunsg]

I won't have availability either.

[notatallshaw]

I'm fairly sure I have availability to do a release on the 30th Jan.

[notatallshaw]

No one else has spoken up, so barring any updates I plan to release pip 26.0 on the evening of 30th January (NYC time).

I will do my best but I don't have a lot of spare time to review between now and then, so a few things:

• Reviews appreciated for any PRs on the 26.0 milestone: https://github.com/pypa/pip/milestone/82
• Anything that isn't ready or just hasn't had enough time to review and merge I will push to 26.1
• Please don't add anything to the 26.0 milestone unless it's urgent or you plan to review yourself

[notatallshaw]

I have merged all outstanding approved PRs and created a draft release PR: #13775. @ichard26 if you have cold feet about any of your PRs I merged today feel free to revert or DM me and I will revert them.

After work today I intend to go through the news items and clean them up and rebase the PR. If anyone has specific rewording they want post them in the PR today and I will pick them all up this evening.

[ichard26]

Sounds good! I've already published my pip 26.0 release post so it's ready to be shared once you cut the release: https://ichard26.github.io/blog/2026/01/whats-new-in-pip-26.0/

Thank you!

[notatallshaw]

There appear to be some doc issues that need fixing before release, I will take a look: pypa/packaging.python.org#1997 (comment)

I plan to land #13777 before release, and I've requested ruff add a lint rule: astral-sh/ruff#22981