Add compatibility guard test for K2 JVM compiler wrappers#6169
Open
Polina Mitrikovskaia (rpaouline) wants to merge 1 commit into
Open
Conversation
Code Owners
|
1d99d87 to
7afac1e
Compare
Introduce a compilation-only guard test for downstream Kotlin compiler JVM wrappers and plugin integrations (e.g. custom compiler wrappers). This test ensures that critical internal classes, pipeline phases, and compiler arguments used by third-party integrations (such as JvmConfigurationPipelinePhase, K2JVMCompilerArguments, and JvmAbiConfigurationKeys) are not renamed or removed without deprecation, preventing silent build breakages.
7afac1e to
2f19601
Compare
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.
Introduce a compilation-only guard test for downstream Kotlin compiler JVM wrappers and plugin integrations (e.g. custom compiler wrappers).
This test ensures that critical internal classes, pipeline phases, and compiler arguments used by third-party integrations (such as JvmConfigurationPipelinePhase, K2JVMCompilerArguments, and JvmAbiConfigurationKeys) are not renamed or removed without deprecation, preventing silent build breakages.