-
Notifications
You must be signed in to change notification settings - Fork 625
Move Kotlin serialization gradle plugin into libs.versions.toml #6254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
📝 PRs merging into main branchOur main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released. |
Generated by 🚫 Danger |
Size Report 1Affected ProductsNo changes between base commit (27a16a1) and merge commit (eed4862).Test Logs |
Coverage Report 1Affected Products
Test Logs |
A previous change, #6186, added the Kotlin serialization plugin to every single Gradle module; however, only one module actually used it. Moreover, it is becoming more conventional to define dependency versions in
gradle/libs.versions.toml
. This PR removes the global dependency on the Kotlin serialization plugin and, instead, moves the version intogradle/libs.versions.toml
, and also modifies the dependency on the Kotlin JSON serialization library to usegradle/libs.versions.toml
. This will make sure that every module uses the same version, which will become important once Data Connect, which also uses these libraries, is merged into main.