fix(deps): update all dependencies#172
Merged
Merged
Conversation
Generated by 🚫 Danger Kotlin against a2dac09 |
4d5b6ed to
85420e5
Compare
85420e5 to
354289d
Compare
ed50441 to
1a62234
Compare
1a62234 to
a2dac09
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.
This PR contains the following updates:
9.2.1→9.3.16.0.7→6.1.26.0.7→6.1.26.0.7→6.1.21.53.0→1.58.01.53.0→1.58.01.53.0→1.58.04.16→4.16.14.33.2→4.33.54.33.2→4.33.52.3.4→2.3.52.3.4→2.3.51.9.0→1.10.05.3.0→5.4.02.57.2→2.59.12.57.2→2.59.12.57.2→2.59.12.57.2→2.59.117.3.0→17.4.034.7.0→34.8.02.11.0→2.11.12.11.0→2.11.12.9.6→2.9.72.9.6→2.9.71.10.0→1.10.22025.12.01→2026.01.011.12.2→1.12.331.13.2→32.0.031.13.2→32.0.031.13.2→32.0.031.13.2→32.0.08.13.2→9.0.08.13.2→9.0.0Release Notes
gradle/gradle (gradle)
v9.3.1: 9.3.1Compare Source
This is a patch release for 9.3.0. We recommend using 9.3.1 instead of 9.3.0.
The following issues were resolved:
Read the Release Notes
Upgrade instructions
Switch your build to use Gradle 9.3.1 by updating your wrapper:
See the Gradle 9.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.
For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.
Reporting problems
If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.
We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.
v9.3.0Compare Source
kotest/kotest (io.kotest:kotest-property)
v6.1.2Compare Source
What's Changed
Full Changelog: kotest/kotest@6.1.2...v6.1.2
v6.1.1Compare Source
What's Changed
ktor-server-coredependency. by @sksamuel in #5587Full Changelog: kotest/kotest@v6.1.0...v6.1.1
v6.1.0Compare Source
The first Kotest release of 2026 is here - 6.1 'Bouncing Boimler'
What's Changed
beBooleanmatcher public by @LeoColman in #5241kotlin-compile-testingto version 0.11.0 inlibs.versions.toml. by @sksamuel in #5251shouldContainAllInAnyOrdermatchers for collections by @sksamuel in #5228InstancePerLeafandInstancePerTest(issue #5261) by @alfonsoristorato in #5274RootTestWithConfigBuilderandRootContainerWithConfigBuilderby @alfonsoristorato in #5315New Contributors
Full Changelog: kotest/kotest@v6.0.7...v6.1.0
takahirom/roborazzi (io.github.takahirom.roborazzi)
v1.58.0Compare Source
Bugfix: Fixed NoClassDefFoundError in RoborazziPlugin when the Android Plugin is not applied
Previously, we never touched the Android Plugin class when it wasn’t in use; nevertheless, a NoClassDefFoundError was raised because the plugin contained a method that referenced the Android Plugin class. I therefore extracted Android-related code into a separate class to resolve the issue. Thank you, @rnett, for reporting this.
Update: Device qualifiers
You can now specify device qualifiers via RobolectricDeviceQualifiers. The list has been expanded with new devices such as Pixel9, XRGlasses, and even AIGlasses!
Thank you, @joergmis, for your contribution.
What's Changed
New Contributors
Full Changelog: takahirom/roborazzi@1.57.0...1.58.0
v1.57.0Compare Source
Fix AGP 9.0 KMP preview screenshots
We had been using
unitTestSources?.**java**?.addGeneratedSourceDirectory, but this approach proved ineffective when we adoptedcom.android.kotlin.multiplatform.library. Consequently, we migrated tounitTestSources?.**kotlin**?.addGeneratedSourceDirectoryfor the KMP plugin. Unfortunately, when applyingcom.android.library,unitTestSources?.kotlinremains non-functional, so we must toggle between the two depending on the plugin.Thank you for reporting this @HLCaptain !
(This is our plugin code, you don't have to write this.)
Bugfix: Compose Preview’s
onSizeChanged{}wasn’t called when multiple windows exist.There is a bug in which Compose Preview’s
onSizeChanged{}fails to fire when multiple windows are present. This issue arises because we neglected to invokecomposeTestRule.mainClock.advanceTimeByFrame() composeTestRule.waitForIdle()Reproducing screenshots
What's Changed
Full Changelog: takahirom/roborazzi@1.56.0...1.57.0
v1.56.0Compare Source
Added AGP 9.0 compatibility to RoborazziPlugin
Roborazzi was previously using APIs and classes that have since been deprecated, such as
Variant.unitTestand TestedExtension. We have now migrated to alternative, supported classes and methods. Thanks for reporting this, @allanconda-mercari !Behavior changes: Stabilized preview LaunchedEffect execution for Compose Preview support
Previously, screenshots occasionally differed from Android Studio Composable Preview when using LaunchedEffect. We now invoke
composeTestRule.mainClock.advanceTimeByFrame()by default, so some screenshots may appear different. You can restore the previous behavior by implementing a custom tester as follows:What's Changed
Full Changelog: takahirom/roborazzi@1.55.0...1.56.0
v1.55.0Compare Source
Bugfix: Fix WebP ClassCastException
What happened
SdkSandboxClassLoader.ImageIO.getImageWritersByMIMEType, which internally caches writers in a static field. When the writer is first created, the code is executed by SdkSandboxClassLoader1.What we did
We leveraged reflection to force
ImageIO.getImageWritersByMIMETypeto use the System ClassLoader, thereby guaranteeing that the same class definition is shared irrespective of the current SdkSandboxClassLoader.Many thanks to @eygraber for reporting this bug!
What's Changed
Full Changelog: takahirom/roborazzi@1.54.0...1.55.0
v1.54.0Compare Source
Breaking change: Report HTML and JSON paths have changed
The HTML report used to be at
build/reports/roborazzi/index.htmlbut is now located atbuild/reports/roborazzi/<build_variant>/index.html. This is a first step toward fixing a long-standing issue where runningrecordRoborazzi(instead ofrecordRoborazziDebug) could break test results; further work is still needed to make it fully reliable.You should be able to fix it by adding
/debug/(or your build variant) to the path in your CI script. I believe the change is straightforward, but if you run into any cases where it's difficult please let me know.Note: This change does not affect the paths of the generated screenshot images, so most users will not be impacted.
Thank you for your contribution, @vladcudoidem!
Behavioral change: Fixed screenshot timing for Compose Preview Support
Previously, we used Espresso.onIdle() and ShadowLooper.idle(), but these APIs are not suitable for Compose. Consequently, screenshots could not be captured after onSizeChanged completed.
If you encounter issues with infinite animations—such as
CircularProgressIndicator—you can configure frame-based captures using@RoboComposePreviewOptions.Thank you for reporting this issue, @savvasenok!
What's Changed
Full Changelog: takahirom/roborazzi@1.53.0...1.54.0
google/ksp (com.google.devtools.ksp)
v2.3.5Compare Source
What's Changed
Contributors
Full Changelog: google/ksp@2.3.4...2.3.5
Kotlin/kotlinx.serialization (org.jetbrains.kotlinx:kotlinx-serialization-json)
v1.10.0==================
This release is based on Kotlin 2.3.0 and contains all of the changes from 1.10.0-RC.
The only additional change is a fix for ProtoBuf packing of Kotlin unsigned types (#3079).
Big thanks to KosmX for contributing the fix.
Stabilization of APIs
kotlinx-serialization 1.10 and subsequent releases will be focused on stabilization of existing APIs.
The following APIs and configuration options are no longer experimental because they're widely used without any known major issues:
Jsonconfiguration options:decodeEnumsCaseInsensitive,allowTrailingComma,allowComments, andprettyPrintIndent. (#3100)@EncodeDefaultannotation and its modes. (#3106)JsonUnquotedLiteralconstructor function (#2900)JsonPrimitiveconstructor function overloads that accept unsigned types. (#3117)JsonElementwithNothing?overloads. (#3117)Readiness for return value checker
Kotlin 2.3.0 introduces a new feature aimed
at helping you to catch bugs related to the accidentally ignored return value of the function.
kotlinx-serialization 1.10.0-RC code is fully marked for this feature, meaning that you
can get warnings for unused function calls like
Json.encodeToString(...).To get the warnings, the feature has to be enabled in your project as described here.
Polymorphism improvements
Polymorphic serialization received a couple of improvements in this release:
New
subclassesOfSealedutility to automatically register sealed subclasses serializers in polymorphic modules (#2201).Use it in your
SerializersModulewhen configuring a polymorphic hierarchy which contains both abstract and sealed classes.For example, when root of your hierarchy is an
interface, but most of your inheritors aresealedclasses.The new function will register all known sealed subclasses for you, so you don’t need to list them one by one.
This makes writing your
SerializerModules much faster and simpler.Big thanks to Paul de Vrieze for contributing this feature.
Class discriminator conflict check rework (#3105).
If a payload already contains a property with the same name as the configured discriminator (for example,
type),it is called a class discriminator conflict.
To produce a correct output and allow more inputs to be deserialized at the same time, the following changes were made:
JsonNamingStrategytransformations are now detected during serialization as well and will causeSerializationException.It also affects non-polymorphic classes.
ClassDisciminatorMode.ALL_JSON_OBJECTSandSerializersModuleBuilder.polymorphicDefaultSerializerare also detected.Previously, it was possible in the sealed hierarchies alone due to missing assertion. See #1664 for details.
General improvements
.serialNametoMissingFieldExceptionfor clearer diagnostics. (#3114)Automatic-Module-Nameentries for metadata JARs. (#3109)Bugfixes
BIGNUM_NEGATIVEtag name. (#3090)Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.