Update all non-major dependencies - #160
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
February 11, 2026 16:57
7be800e to
295602b
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
February 12, 2026 10:00
295602b to
c8a69c6
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
February 28, 2026 12:54
1cc1e7e to
e1426a0
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
March 12, 2026 18:10
94b87ff to
7293801
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
7 times, most recently
from
March 18, 2026 17:50
ca55bbd to
45e504f
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
March 27, 2026 14:00
cf3a691 to
5814416
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
April 10, 2026 20:48
5814416 to
35d53ec
Compare
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
April 12, 2026 20:35
c86cce7 to
083d4d5
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
May 17, 2026 01:07
e48f602 to
70a0c73
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
May 28, 2026 17:34
6427ed8 to
5de75ce
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
June 3, 2026 23:44
779be2d to
9ea7615
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
June 13, 2026 15:46
dd76daf to
520e3fa
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
5 times, most recently
from
June 24, 2026 18:13
3ae41f4 to
2916acc
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
July 4, 2026 08:00
9a83bfd to
b1e37d9
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
7 times, most recently
from
July 14, 2026 10:44
317b5e7 to
be68150
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
July 24, 2026 02:20
7e75161 to
8e276ca
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:
8.14.4→8.14.55.3.2→5.5.02.11.0→2.18.14.3.1→4.5.03.5.1→3.19.10.35.0→0.37.00.25.0→0.27.00.25.0→0.27.07.1.1→7.2.25.5.0→5.5.11.4.4→1.4.51.6.8→1.7.01.6.8→1.7.03.16.4→3.18.15.3.2→5.5.01.0.0-alpha05→1.0.01.10.0→1.11.00.7.1→0.8.00.17→0.202.2.21→2.4.102.2.21→2.4.104.1.1→4.2.21.6.6→1.7.07.5.0.202512021534-r→7.7.1.202607240634-r1.6.1→1.7.10.17→0.209.3.1→9.6.10.22→0.28Release Notes
gradle/gradle (gradle)
v8.14.5: 8.14.5Compare Source
The Gradle team is excited to announce Gradle 8.14.5.
Here are the highlights of this release:
Read the Release Notes
We would like to thank the following community members for their contributions to this release of Gradle:
Aurimas,
Ben Bader,
Björn Kautler,
chandre92,
Daniel Hammer,
Danish Nawab,
Florian Dreier,
Ivy Chen,
Jendrik Johannes,
jimmy1995-gu,
Madalin Valceleanu,
Na Minhyeok.
Upgrade instructions
Switch your build to use Gradle 8.14.5 by updating your wrapper:
See the Gradle 8.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.
lysine-dev/okhttp (com.squareup.okhttp3:okhttp)
v5.5.02026-08-16
This release introduces opt-in support for [Encrypted Client Hello (ECH)]. This new feature
improves user privacy by encrypting domain names in transit. With regular TLS, your coffee shop’s
Wi-Fi router can see that you’re visiting wikipedia.com, but it cannot see which page you’re
looking at. With ECH, the router observes only the IP address. This additional privacy is most
effective on sites hosted by big CDNs because the IP address doesn’t imply a particular website.
This requires ECH support in the platform’s TLS stack. Today this is only Android 17 (API 37,
released June 2026). When other TLS stacks add ECH support, we'll integrate them.
ECH took a lot of work to implement because the encryption keys are published over DNS in the
[HTTPS resource record], and we needed to write new code to fetch these records. This release
includes a major update to OkHttp’s DNS API: it now supports multiple resource record types (not
just IP addresses!), asynchronous streaming results, and in-memory caching.
To opt in, you can use
DnsOverHttps:You could also opt in with our new
AndroidDnsAPI. Unfortunately, the privacy benefits of ECH aredeficient because its DNS queries are not encrypted by default.
projects ([Retrofit], [Okio], and [SQLDelight]) recently joined [the Commonhaus Foundation].
@StartStopannotation now supports@NestedJUnit 5 tests.weren’t applied correctly.
the HTTP call to crash.
v5.4.02026-06-08
OkHttpClient.Builder, such as the cache, connection pool, socket factory, and DNS. We expectthis will allow most users to use interceptors everywhere, insted of mixing and matching
interceptors with custom
Call.Factorywrappers.okhttp-coroutinesartifact.autonomousapps/dependency-analysis-android-gradle-plugin (com.autonomousapps:dependency-analysis-gradle-plugin)
v3.19.1v3.19.0ArtifactsReportTaskcacheable again.kotlin-metadata-jvmruntime handling.ExpensiveJartype to holdBinaryClasses, removing them fromExplodedJar.NO_IMPLICIT_LOOKUP_IN_PARENT_PROJECTS.v3.18.0GraphViewTask's inputs are inputs, not internal details.GraphViewTasksensitive to new transitive project edges.ArtifactsReportTask.InMemoryCachewith a task.org.gradle.caching=true).v3.17.0RewriteTask) in Kotlin DSL only.change.
ZipFileobjects.T.toJson(). PreferbufferedWriteJson().v3.16.1commonMainApitojvmMainApi.Iterator.remove()for safe modification.synthetic-project.jsonto save disk space.StandardTransforminto Android/JVM/KMP-specific classes.v3.16.0AGP_MAXto 9.2.1.v3.15.0:aggregatePublicTypesTaskto movegrouptodescription.com.autonomousapps:antlrto latest.)v3.14.1computeTypeUsage.JarExplodershould ignore some MRJar content.v3.14.0AndroidScoreshould ignore class files when testing if a project has source splits.v3.13.0computeTypeUsage<variant>task generates usage report.v3.12.2exceptions. We only want to flag things that provide the exception types.
MutableSet<Usage>.simplify(visibility, bucket)inStandardTransformwasn't properly handling the case whena usage was visible on both compile and runtime classpaths. In such a case, we can filter out all usages.
jar case.
v3.12.1v3.12.0exception's type from the runtime classpath, that can cause failures in the consumer at runtime.
v3.11.0apidependencies.v3.10.0dependenciesblocks that have a single line.v3.9.0v3.8.0v3.7.0v3.6.1v3.6.0resolveExternalDependenciestask.Class.forNamehandling.javax.inject.JarExploder.publictypes to an internal package to exclude from published api, and exclude thecom.autonomousapps.model.internalpackage from the published api.AbstractDependencyAnalyzer.vanniktech/gradle-maven-publish-plugin (com.vanniktech:gradle-maven-publish-plugin)
v0.37.0Compare Source
.ascsignature files (gradle/gradle#20232) and the
sha256/sha512checksums, which are never read by Gradle or Maven Central. The published checksums can be configured through
checksums(...)in the DSL or themavenCentralChecksumsGradle property (defaultmd5,sha1). Signature checksumexclusion can be controlled through
excludeSignatureChecksums()or themavenCentralExcludeSignatureChecksumsGradle property.
Minimum supported versions
Compatibility tested up to
v0.36.0Compare Source
BREAKING
DirectorySignatureTypeinternal.Behavior changes
validateDeploymentnow has theDeploymentValidationenum as type instead of being a boolean. The defaultis now to just wait for the
VALIDATEDstate. The previous behavior can be achieved by setting it toPUBLISHED.NONEcan be used for disabling the validation completely.configure(...)manually to configure what to publish and not passingjavadocJarexplicity,the plugin now defaults to publishing an empty javadoc jar.
Features
when using the default options and the Dokka plugin is applied to the project.
JavadocJarandSourcesJaroptions toconfigureBasedOnAppliedPluginsand to allapplicable project types that can be passed to
configure. The previousBooleanbased versions havebeen deprecated.
mavenCentralDeploymentValidationandmavenCentralAutomaticPublishingare used for the default values of the 2 parameters when they are not passedexplicitly. This allows to more easily override them in certain environments.
gradle.propertiesfiles are now considered inthe same way they are when isolated projects is disabled.
Improvements
Minimum supported versions
Compatibility tested up to
square/wire (com.squareup.wire:wire-runtime)
v5.5.1Compare Source
2026-03-05
Kotlin
If set to false, Wire will not use immutable copies for repeated or map fields.
wire { kotlin { makeImmutableCopies = false } }google/truth (com.google.truth:truth)
v1.4.5: 1.4.5assertThat(nullMap).isEmpty()to fail with a useful failure message instead of throwingNullPointerException(and similarly for other "bogus" values, such as negative sizes). (da5d6e9)isInstanceOf(Int::class.java)(and Java'sisInstanceOf(int.class)) a valid way to check forInt/Integerinstances. (974ef19)isWithinto pretty-print numbers in its failure messages. (de78553,07318c2)Integerinstead ofjava.lang.Integer). (0ba72d6)ExpectFailureto never generate "value of" lines based on bytecode. This slightly simplifies writing new tests withExpectFailureand prevents future behavior changes in someExpectFailuretests that already exist. However, it may also require changes to other existingExpectFailuretests to remove or change any assertions about the "value of" line. (3caa0e8)minSdkVersionis now 23 (Marshmallow). This follows the minimum of Google's foundational Android libraries, and we expect it to have no practical impact on users. (c85c75c)@NullMarked. This was making all our types non-null in those environments, since we don't yet use@Nullablein the GWT/J2CL artifact. (6392d37)joshfriend/spotlight (com.fueledbycaffeine.spotlight:buildscript-utils)
v1.7.0Gradle Plugin
taskInvocationRulestospotlight-rules.jsonfor including projects (or all projects) when specific tasks are invokedv1.6.12Gradle Plugin
includestatements that are commented-out in:checkAllProjectsListIDE plugin
v1.6.111.6.11
v1.6.101.6.10
v1.6.9IDE plugin
lysine-dev/okio (com.squareup.okio:okio)
v3.18.12026-07-28
the new
base64()function, we inadvertently changed the binary signature! Ugh! This is nowfixed and we've automated binary-compatibility checking for Kotlin/Native going forward.
v3.18.02026-07-21
AssetFileSystem.exists()when the underlying storage throws aFileNotFoundException.preopen. The platform behavior recently changed inNodeJS, causing our
WasiFileSystemto be unable to access files!BufferedSource.readUInt(),BufferedSink.writeUInt(), and similar functions forUByte,UShortandULong. Also add support for unsigned and little-endian.BufferedSink.utf8Appendable(). Use this to adapt an Okio sink to anAppendable.Source.limit()returns a wrapped source with a strict limit on how many bytes arereturned.
ByteString.equals(other, constantTime)for subtle defense against timing attacks.v3.17.02026-03-11
New: Adjust down the Kotlin stdlib dependency to [Kotlin 2.1.21][kotlin_2_1_21]. Okio is built
with an up-to-date Kotlin compiler (2.2.21), but depends on an older kotlin-stdlib. We're doing
this so you can update Okio and Kotlin independently.
Fix: Return the correct timestamp in
FileMetadata.createdAtMillison Kotlin/Native on UNIXplatforms. We were incorrectly using the POSIX
ctime(change time) instead of thebirthtime. With this fix Okio now prefersstatx()overstat()on native platforms. ThisAPI first appeared in Linux in 4.11 (2017) and Android in API 30 (2020).
Kotlin/kotlinx.serialization (org.jetbrains.kotlinx:kotlinx-serialization-json)
v1.11.0==================
This release is based on Kotlin 2.3.20 and provides new Json exceptions API and some bugfixes and improvements.
Expose Json exceptions structure
To make working with exceptions easier and providing proper error codes in e.g., REST APIs,
classes
JsonException,JsonDecodingException, andJsonEncodingExceptionare now public.They have relevant public properties, such as
shortMessage,path,offset, and others.This API is currently experimental, and we're going to improve it further in the subsequent releases.
See the linked issues for the details: #1930, #1877.
Ability to hide user input from exception messages for security/privacy reasons.
Historically, exception messages in kotlinx.serialization often included the input Json itself for debuggability reason.
Such behavior may pose additional challenges for logging, analytics, and other systems, since
a system is not always allowed to store user data due to privacy/security reasons, which imposes additional sanitation logic.
To address this issue, a new property
exceptionsWithDebugInfois added toJsonConfiguration.Disable it to hide user input from exception messages.
IMPORTANT: This behavior will be enabled by default when this property becomes stable.
See #2590 for more details.
Bugfixes and improvements
Kotlin/kotlinx-datetime (org.jetbrains.kotlinx:kotlinx-datetime)
v0.8.0Breaking changes:
TimeZoneserialization (#576).Additions:
orNullfunctions for non-throwing construction of datetime entities (#68).parseOrNullextension functions for non-throwing attempts at parsing (#508).LocalIsoWeekDatefor representing ISO week dates (#603).Tweaks and fixes:
Instant.untilandInstant.periodUntil(#534).DateTimeComponents.Formats.RFC_1123format (#608).Changelog relative to version 0.8.0-rc02
No changes, only the version is increased.
InsertKoinIO/koin (io.insert-koin:koin-core)
v4.2.2: Koin 4.2.2Compare Source
Maintenance release for the 4.2.x line — resolver regression fixes from the 4.2.0
CoreResolverV2rewrite, ViewModel/scope fixes, a Ktor request-scope fix, plus new tvOS support and an R8/ProGuard guide.Bug Fixes
Stacked params no longer shadow qualified dependencies (#2370, #2408) — A value passed via
parametersOfcould be returned for aget(named(...))request of the same type, shadowing the qualified definition. Qualified lookups are now registry-only and never read the parameter stack — parameters carry no qualifier, so they can't satisfy a qualified request.Root factory no longer resolves its scoped dependencies from
_root_(#2379) — When a non-single factory defined in the root scope was resolved from a child scope,CoreResolverV2resolved its scoped dependencies against_root_instead of the requesting scope. Linked-scope resolution now runs the factory against the requesting scope (single instances keep their root-bound semantics, preserving #2325).viewModelScopeFactoryscope is linked to its parent (#2299) — A ViewModel scope created viaviewModelScopeFactory()was not linked to the originating scope, so dependencies declared in the parent couldn't be resolved. The created scope is now linked to its parent (except when the parent is root).Tolerate non-
Stringenvironment properties (#2348) — Loading environment/system properties whose values aren'tStringthrewClassCastExceptiondue to an unchecked map cast. Non-Stringvalues are now preserved asAnyand onlyStringkeys are required.Unique Ktor request-scope ids under concurrency (#2410) — Concurrent requests could collide on request-scope ids. Ids are now generated from a monotonic counter seeded once at startup. Thanks @lfavreli-betclic!
Actionable errors for
SavedStateHandle/viewModelScope { }(#2044, #2417) — ResolvingSavedStateHandlewithout the proper extras, or usingviewModelScope { }without theviewModelScopeFactory()option, now produces a clear, actionable error message instead of an opaque failure.Added
tvOS targets for
koin-core-viewmodel(#2426) —koin-core-viewmodelnow publishestvosArm64,tvosX64, andtvosSimulatorArm64, unblocking ViewModel usage on tvOS.Consumer R8/ProGuard rules + guide — Android and ViewModel artifacts now ship consumer R8/ProGuard rules in their AARs, and a new R8 / ProGuard guide documents keep rules for minified builds.
Improvements
bind()/binds()—bind/bindsnow append secondary types in O(1) instead of reallocating the type list per binding, removing quadratic cost when a definition declares many bindings. No user-visible behavior change.Documentation
entryProvider(#2336) — Added guidance on using Koin with the typedentryProviderin the Navigation 3 reference.Contributors
Thanks to the following contributors for this release:
v4.2.1: Koin 4.2.1Compare Source
Support for Compile Safety with Koin Compiler 1.0.0-RC1
Bug Fixes
Fix stacked-params lookup on linked scopes (#2387) — The 4.2.0 resolver rewrite (
CoreResolverV2) walked linked scopes but dropped the per-parent stacked-parameters check that 4.1.x performed via recursion. This broke patterns whereAndroidParametersHolderis stacked on the factory scope byKoinViewModelFactoryandSavedStateHandleis then resolved from a child ViewModel scope. Linked-scope resolution now also checks stacked params on each parent scope.Restore ABI compatibility for
runOnKoinStarted(#2391) — The 4.2.0 release inadvertently broke binary compatibility forrunOnKoinStartedon JVM. Fixed by restoring the original JVM class name via@JvmName/@JvmMultifileClassannotations.Fix scope
_closedconcurrency issue (#2389) — TheScope._closedflag was not volatile, which could cause stale reads under concurrent access.Improvements
Improved Scope resolution error messages —
CoreResolverV2now provides clearer error messages when scope resolution fails, making it easier to diagnose misconfigured scopes.Added
apiCheckto CI — Binary compatibility validation (kotlinx.binary-compatibility-validator) now runs on every PR to prevent future ABI breaks.Documentation
parametersOftype-collision warning (#2328) — Added a caution note explaining that when a value passed viaparametersOfhas the same type as the requested definition, Koin returns the value directly and skips the factory block. Suggests using a wrapper type as a workaround.Contributors
Thanks to the following contributors for this release:
v4.2.0Compare Source
Kotlin 2.3.20
New Features
Performance & Stability
Bug Fixes
Breaking Changes
Dependencies
Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Enabled.
♻ 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.