Skip to content

Auto-port 5.0: Revapi: Use default "oldVersion"#16775

Merged
chrisvest merged 1 commit into
5.0from
auto-port-pr-16774-to-5.0
May 8, 2026
Merged

Auto-port 5.0: Revapi: Use default "oldVersion"#16775
chrisvest merged 1 commit into
5.0from
auto-port-pr-16774-to-5.0

Conversation

@netty-project-bot
Copy link
Copy Markdown
Contributor

Auto-port of #16774 to 5.0
Cherry-picked commit: 3ff52d6


Motivation:
If we fix the old version to be the start of the 4.2 series, then revapi cannot find compatibility breakages in classes that were added after 4.2.0.

Modification:
Let revapi pick the old version using its defaults. This will make it compare to the most recent released version, and thus we detect API breakages between each patch release.

Result:
More fine-grained API breakage detection by revapi.

Motivation:
If we fix the old version to be the start of the 4.2 series, then revapi
cannot find compatibility breakages in classes that were added after
4.2.0.

Modification:
Let revapi pick the old version using its defaults. This will make it
compare to the most recent released version, and thus we detect API
breakages between each patch release.

Result:
More fine-grained API breakage detection by revapi.

(cherry picked from commit 3ff52d6)
@chrisvest chrisvest added this to the 5.0.0.Final milestone May 8, 2026
@chrisvest chrisvest merged commit 36f2ef3 into 5.0 May 8, 2026
10 of 13 checks passed
@chrisvest chrisvest deleted the auto-port-pr-16774-to-5.0 branch May 8, 2026 19:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants