[YANKED] pytest 8.1.0 removes many deprecations, but not mentioned in changelog

[mr-c]

#11757 is not mentioned as a breaking change for the Pytest 8.1.0 Release in https://docs.pytest.org/en/stable/changelog.html ; it breaks plugins who were still supporting the older signature.

I'm opening this issue as a hint to others; is it possible to update the changelog after a release?

[RonnyPfannschmidt]

this is a duplicate of #12068

the removal process itself is as intended, the oversight was that warnings of certain hooks where not displayed as expected

leaving this open for now to help people
the fact that it wasn't failing on 8.0 is the actual bug

[bluetech]

@RonnyPfannschmidt @nicoddemus since we botched the deprecation, perhaps we should revert the removal until we can have at least one release with proper deprecation?

[RonnyPfannschmidt]

should we yank 8.1 for the deprecation issues?

[RonnyPfannschmidt]

lets defer the return of code a bit as i'd like to know first how to trigger the errors

[nicoddemus]

I think it is fair to postpone the removals if we did not issue the proper warnings, as we vouch to do before any removals took place.

Those removals would then have to be postponed to 9.0/9.1 then.

Not sure if you folks would like to yank 8.1? Seems reasonable.

[bluetech]

Reverting + releasing 8.1.1 should not be a problem, but if @RonnyPfannschmidt wants to avoid a revert, let's yank as it seems to be causing a lot of failures.

[RonnyPfannschmidt]

lets yank and revert then

[nicoddemus]

I'm yanking it.

[nicoddemus]