2.5.11 release notes not accurate

[pegtrifork]

Description

In the 2.5.11 release notes it listsa fix for 4411 as beeing part of that release.
It does however seem like the fix was only commited to main and not the release branch.
We are affected by the bug described in 4411, and would like a new patch release where the bugfix is included. Alternatively the release notes should be updated to reflect that this bugfix is not part of the release.

[apicurio-bot]

Thank you for reporting an issue!

Pinging @andreaTP to respond or triage.

[carlesarnal]

@pegtrifork you're right, this has been fixed on main and has not been backported. It was caught in the release notes since they're automatically generated based on closed issues, I'll fix them.

[pegtrifork]

@carlesarnal Thank you! Will the fix be backported and released in a 2.5.12, or will it not be included untill 2.6.0?

[carlesarnal]

It will be included in the 2.6.0 release most likely.