MINOR: Bump trunk to 4.5.0-SNAPSHOT

[Parkerhiphop]

As described in
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=34840886#ReleaseProcess-CutBranches

This is the standard post-branch-cut bump after the 4.4 branch was
created. Trunk now tracks 4.5.0-SNAPSHOT.

Reviewers: Chia-Ping Tsai chia7712@gmail.com, Andrew Schofield
aschofield@confluent.io

[chia7712]

I'm wondering whether the active branches 4.3 and 4.2 should be included

[Parkerhiphop]

Thanks for reviewing!

Yes. I checked the current supported releases and recent branch activity, and both 4.3 and 4.2 are still active maintenance branches.

I’ll include them in both push and pull_request so this workflow also runs for PRs and pushes targeting those branches.

[AndrewJSchofield]

I think we need to update https://github.com/apache/kafka/blob/trunk/server-common/src/main/java/org/apache/kafka/server/common/MetadataVersion.java too because LATEST_PRODUCTION should be IBP_4_4_IV2 I think.

[Parkerhiphop]

I think we need to update https://github.com/apache/kafka/blob/trunk/server-common/src/main/java/org/apache/kafka/server/common/MetadataVersion.java too because LATEST_PRODUCTION should be IBP_4_4_IV2 I think.

Thanks for reviewing and pointing out.

I updated LATEST_PRODUCTION to IBP_4_4_IV2 and synced LATEST_STABLE_METADATA_VERSION in kafkatest.

Since IBP_4_4_IV2 was previously the latest enum value, I also added IBP_4_5_IV0 as the new unstable/testing metadata version for trunk and moved the unstable-version boundary comment accordingly. MetadataVersionTest passes locally.

[AndrewJSchofield]

Thanks for the update. A bunch of tests will need tweaking I think.

[AndrewJSchofield]

I don't think you need to add this one yet, just moving the comment tells the next MV author where to insert their new MV.

[Parkerhiphop]

Thanks, that makes sense. I originally added IBP_4_5_IV0 to keep the existing latestTesting() > LATEST_PRODUCTION invariant used by some tests. I removed it now and kept the unstable-version boundary comment after IBP_4_4_IV2 instead.

I also updated the affected tests to handle the temporary state where latestTesting() can equal LATEST_PRODUCTION.
MetadataVersionTest still verifies that latestTesting is unstable when it is newer than LATEST_PRODUCTION, and FormatterTest now skips unstable-release-version cases when no unstable MV exists. I also updated the expected share.version default to SV_2 since LATEST_PRODUCTION is now 4.4-IV2.

[AndrewJSchofield]

Looks good to me. Thanks for the PR.