You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think we have enough changes for a release. Version 9.1 was released on 2026-06-13.
I also propose that the next release be 10.0. Version 9.0 was released on 2025-11-08. So 10.0 will probably be ~1.5 years from the previous major which seems reasonable to me.
Unless there are objections I will aim to do the release this weekend (around 2026-10-24).
Hmm yes I actually forgot about the "keep it around for at least two minor releases" policy (which is reasonable).
For now I'll keep the next release as 10.0 but if we assess the deprecations and decide there's not much benefit, I'll change it back to 9.3. Since this can be done after the release I consider it non-blocking (might be a little messy with the .dev tag, but I figure it's not immutable and we can just delete it if necessary).
Activity
RonnyPfannschmidt commentedon Oct 18, 2026
i'd like to get about 5 more of my excessive amount of open prs into the release,
additionally we have t consider which of the removed in pytest 10 deprecation we want to turn into removed in pytest 11 deprecations to keep this nice
Add PytestRemovedIn11Warning for unreleased deprecations
bluetech commentedon Oct 25, 2026
Hmm yes I actually forgot about the "keep it around for at least two minor releases" policy (which is reasonable).
For now I'll keep the next release as 10.0 but if we assess the deprecations and decide there's not much benefit, I'll change it back to 9.3. Since this can be done after the release I consider it non-blocking (might be a little messy with the .dev tag, but I figure it's not immutable and we can just delete it if necessary).