Remove incorrect revapi exclusions#28934
Merged
Merged
Conversation
The previous revapi comparison was done against the wrong baseline artifact, producing hundreds of spurious exclusion entries for changes already present in the 480 release. Keep only the single correct exclusion for the new hasNonDeterministicFunctions parameter added to ConnectorMetadata::finishRefreshMaterializedView.
wendigo
approved these changes
Mar 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The revapi comparison was done against the wrong baseline artifact.
Only add one entry for
ConnectorMetadata::finishRefreshMaterializedViewgaining thehasNonDeterministicFunctionsparameter (added in #28682).Additional context and related issues
Fixes the pom.xml mess introduced in #28682.
Release notes
(x) This is not user-visible or is docs only, and no release notes are required.