Release 26.1 (April)

[ichard26]

@pypa/pip-committers alrighty, which one of us wants to be the RM for this release? I have almost no availability from mid-March to mid-April, but I'm willing to cut a caretaker pip 26.1 release if that's all we have capacity for. I will have lots of free time in the second half of April. I know that @notatallshaw and @pfmoore both have limited availability on an ongoing basis.

[pfmoore]

I can't commit that far ahead at the moment, but if there's still no-one able to take it on closer to the time, ask me again. Things will have changed, and I'll have a better idea of whether it's something I can cover.

As a more general procedural note, I don't think we need to decide on an RM in advance (at least not the way I do the RM role 🙂). It's nice to have the information, of course, but with our policy that whatever's on main is what goes into the release, there's not much the RM needs to do beyond a bit of reminding people with PRs in the release milestone, and cutting the actual release.

[notatallshaw]

If we keep the pattern of releasing near the end of the month I usually need to do some logistical preparation near the beginning of the month, i.e. making sure I'm actually available on the night I would plan to release. So for me, around then would be good to formalize who is expected to be the RM.

That said, I'm likely not going to have time to be RM on this cycle, I want to dedicate some more time over the next few months to work on real life stuff, and so generally are going to spend less time on OSS work.

[ichard26]

As a more general procedural note, I don't think we need to decide on an RM in advance (at least not the way I do the RM role 🙂). It's nice to have the information, of course [...]

Mhmm. I'm totally okay with deciding who wants to be the RM later. My apologies for being too eager 🙂

[sbidoul]

Unless someone else wants to do it, I can take the RM hat for this one. I'll target a release around the weekend of April 25, 26, with what is on main at that time.

[pradyunsg]

@sbidoul How would you feel about including 3 PRs, related to unblocking the removal of the legacy resolver by handling a few reported edge cases of the 2020 resolver?

#10946 (comment)

[sbidoul]

Let's do that, yes. Great to see this progressing.

[sbidoul]

If packaging 26.1 is released soon, what do people think about including -r pylock.toml with an experimental warning in this release? #13876

[vfazio]

Since the release is scheduled in a little over a week, could I get some feedback on #13725 ? I'd like to make sure I have time to address any concerns in time to ensure it gets included.

[jeremy-london]

FYI - Hoping that https://nvd.nist.gov/vuln/detail/CVE-2026-3219 fix comes in 26.1

[notatallshaw]

@jeremy-london fix is already merged if you need a patch: #13870

It's scheduled to be in 26.1, that said if there are any last minute issues they will be handled at the discretion of the release manager, so it can only be guaranteed once it is out.