Skip to content

Update Minor & patch dependency updates#32

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/minor-and-patch-dependency-updates
Open

Update Minor & patch dependency updates#32
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/minor-and-patch-dependency-updates

Conversation

@renovate

@renovate renovate Bot commented Apr 14, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
io.micrometer:micrometer-registry-prometheus 1.16.51.17.0 age confidence
io.github.freya022:BotCommands-jda-ktx (source) 3.1.03.3.0 age confidence
com.google.code.gson:gson 2.13.22.14.0 age confidence
io.github.freya022:BotCommands 3.1.03.3.0 age confidence
net.dv8tion:JDA 6.4.16.5.0 age confidence
org.flywaydb:flyway-database-postgresql 12.3.012.11.0 age confidence
org.flywaydb:flyway-core 12.3.012.11.0 age confidence
com.zaxxer:HikariCP 7.0.27.1.0 age confidence
org.postgresql:postgresql (source) 42.7.1142.7.13 age confidence
ch.qos.logback:logback-classic (source, changelog) 1.5.321.5.38 age confidence
io.github.oshai:kotlin-logging-jvm 8.0.018.0.4 age confidence
dev.reformator.stacktracedecoroutinator:stacktrace-decoroutinator-jvm 2.6.22.6.4 age confidence
org.jetbrains.kotlin.plugin.serialization (source) 2.3.202.4.0 age confidence
org.jetbrains.kotlin.jvm (source) 2.3.202.4.0 age confidence

Release Notes

micrometer-metrics/micrometer (io.micrometer:micrometer-registry-prometheus)

v1.17.0: 1.17.0

See also the 1.17 migration guide and the release notes for 1.17.0-RC1, 1.17.0-M3, 1.17.0-M2, 1.17.0-M1.

🐞 Bug Fixes

  • ArrayIndexOutOfBoundsException when using LongTaskTimer #​3877
  • Jetty 12's TimedHandler marks some requests with outcome UNKNOWN #​7276
  • MeterRegistry closes HighCardinalityTagsDetector twice if the registry is closed twice #​7409
  • Reduce allocation in HTTP server instrumentation #​7580
  • Reduce allocation in gRPC server convention #​7581

📔 Documentation

  • Clarify time series produced by LongTaskTimer when using Prometheus #​6507
  • Document metrics that need to close the MeterBinder #​4624
  • Multigauge Documentation lacks overwrite=true #​4403

🔨 Dependency Upgrades

  • Bump com.dynatrace.metric.util:dynatrace-metric-utils-java from 2.4.0 to 2.5.0 #​7452
  • Bump com.google.auth:google-auth-library-oauth2-http from 1.43.0 to 1.48.0 #​7397
  • Bump com.google.cloud:google-cloud-monitoring from 3.89.0 to 3.94.0 #​7398
  • Bump com.google.cloud:libraries-bom from 26.79.0 to 26.83.0 #​7497
  • Bump com.netflix.spectator:spectator-reg-atlas from 1.9.6 to 1.9.9 #​7552
  • Bump dropwizard-metrics from 4.2.38 to 4.2.39 #​7527
  • Bump io.prometheus:prometheus-metrics-bom from 1.5.1 to 1.7.0 #​7572
  • Bump software.amazon.awssdk:cloudwatch from 2.42.32 to 2.46.4 #​7494

❤️ Contributors

Thank you to all the contributors who worked on this release:

@​blaspat, @​codingkiddo, @​izeye, @​jewoodev, and @​schiemon

v1.16.6: 1.16.6

🐞 Bug Fixes

  • ArrayIndexOutOfBoundsException when using LongTaskTimer #​3877
  • Jetty 12's TimedHandler marks some requests with outcome UNKNOWN #​7276
  • MeterRegistry closes HighCardinalityTagsDetector twice if the registry is closed twice #​7409
  • Reduce allocation in HTTP server instrumentation #​7580
  • Reduce allocation in gRPC server convention #​7581

📔 Documentation

  • Clarify time series produced by LongTaskTimer when using Prometheus #​6507
  • Document metrics that need to close the MeterBinder #​4624
  • Multigauge Documentation lacks overwrite=true #​4403

🔨 Dependency Upgrades

  • Bump com.netflix.spectator:spectator-reg-atlas from 1.9.6 to 1.9.9 #​7552
  • Bump dropwizard-metrics from 4.2.38 to 4.2.39 #​7527

❤️ Contributors

Thank you to all the contributors who worked on this release:

@​blaspat, @​codingkiddo, @​izeye, @​jewoodev, and @​schiemon

freya022/BotCommands (io.github.freya022:BotCommands-jda-ktx)

v3.3.0

JDA

Changes
Modals
  • Modal DSL functions used inside a component's DSL are now compile errors
    • This prevents stuff from being applied in unexpected places, for example, it doesn't make sense to call bindTo inside a label, as it is from the modal DSL
    • This change only affects calls that are in the wrong place
jda-ktx
  • Guild#retrieveThreadChannelById now throws ParentGuildMismatchException if the retrieved thread isn't from the same guild
    • OrNull variants will return null in those cases
New features
App. Commands. Declarative
  • Added ofSubcommands to the application command manager
    • This is intended for subcommands and subcommand groups
    • This is the same as slashCommand(name, function = null) { ... }
jda-ktx
  • Added JDA#retrieveThreadChannelById(OrNull)
Fixes
Modals
  • Fixed nullable strings always getting null

Don't hesitate to check out the examples and the wiki.

Full Changelog: freya022/BotCommands@v3.2.1...v3.3.0


Installation

As a reminder, the minimum Java version supported is Java 17.

Kotlin Gradle
repositories {
    mavenCentral()
}

dependencies {
    implementation("io.github.freya022:BotCommands:3.3.0")
}
Maven
<dependency>
    <groupId>io.github.freya022</groupId>
    <artifactId>BotCommands</artifactId>
    <version>3.3.0</version>
</dependency>

v3.2.1

JDA

Small bugfix release.

Fixes
Components
  • Fixed org.postgresql.util.PSQLException: Cannot change transaction read-only property in the middle of a transaction.
Misc
  • Fixed java.lang.IllegalArgumentException: argument type mismatch sometimes occurring when dispatching events in parallel

Don't hesitate to check out the examples and the wiki.

Full Changelog: freya022/BotCommands@v3.2.0...v3.2.1


Installation

As a reminder, the minimum Java version supported is Java 17.

Kotlin Gradle
repositories {
    mavenCentral()
}

dependencies {
    implementation("io.github.freya022:BotCommands:3.2.1")
}
Maven
<dependency>
    <groupId>io.github.freya022</groupId>
    <artifactId>BotCommands</artifactId>
    <version>3.2.1</version>
</dependency>

v3.2.0

JDA


Changes
Dependencies
  • Kotlin 2.3.20
  • kotlinx.coroutines 1.11.0
  • JDA 6.4.2
Text commands
  • Text commands sharing the same path must be in the same class

Fixes
Text commands
  • Class annotations now apply again
Modals
  • Getting an empty non-null string from empty text inputs has been fixed
Misc
  • Fixed support for reflectively-accessed inner class constructors
  • Fixed support for reflectively-accessed object instance methods

Don't hesitate to check out the examples and the wiki.

Full Changelog: freya022/BotCommands@v3.1.0...v3.2.0


Installation

As a reminder, the minimum Java version supported is Java 17.

Kotlin Gradle
repositories {
    mavenCentral()
}

dependencies {
    implementation("io.github.freya022:BotCommands:3.2.0")
}
Maven
<dependency>
    <groupId>io.github.freya022</groupId>
    <artifactId>BotCommands</artifactId>
    <version>3.2.0</version>
</dependency>
discord-jda/JDA (net.dv8tion:JDA)

v6.5.0: | Message Search API

Overview

This release adds support for the Message Search API, which allows bots to search messages in a guild. See Guild#searchMessages and MessageSearchAction for detailed documentation.

Example:

guild.searchMessages()
     .attachmentFilenames("cat.png")
     .includeAuthorTypes(MessageSearchAction.AuthorType.USER)
     .queue(response -> {
         if (response.isNotReady()) {
             int retryAfter = response.asNotReady().getRetryAfter();
             event.reply("The server is still indexing messages, try again later").queue();
             return;
         }

         List<Message> messages = response.asResults().getMessages();
         event.reply("Found %s messages of cats!".formatted(messages.size())).queue();
     });

Additionally, we made a minor change in the handling for received messages. For messages received in guilds JDA now handles events with missing member objects, which is necessary to handle messages that arrive shortly after a user is banned from the guild. These messages will contain members which are not added to cache and have no roles.

New Features

Changes

Full Changelog: discord-jda/JDA@v6.4.2...v6.5.0

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:6.5.0")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>6.5.0</version> 
</dependency>

v6.4.2

New Features

Changes

  • Improve error messages caused by entities relying on the cache to find themselves by @​freya022 in #​3067
  • Component options: Prevent setting an out-of-range number of default values by @​freya022 in #​3068
  • Fix deserialization of components without unfurled media by @​freya022 in #​3078

Bug Fixes

Full Changelog: discord-jda/JDA@v6.4.1...v6.4.2

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:6.4.2")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>6.4.2</version> 
</dependency>
pgjdbc/pgjdbc (org.postgresql:postgresql)

v42.7.13

Added
  • feat: invalidate the prepared-statement cache when the server reports a search_path change via GUC_REPORT (PostgreSQL 18+), so cached plans are no longer used against the wrong schema PR #​4259
  • feat: reWriteBatchedInserts now merges up to 32768 rows into one multi-values INSERT (bounded by the 65535 bind-parameter limit on the extended protocol) instead of capping at 128, which speeds up batches of few-column rows. The new reWriteBatchedInsertsSize connection property lowers that cap when set; the default of 0 uses that maximum. PR #​4207
  • feat: invalidate the prepared-statement cache after CREATE/DROP/ALTER so callers no longer trip on "cached plan must not change result type" without opting into autosave=ALWAYS. Controlled by the new flushCacheOnDdl connection property (default true); set to false for the prior behaviour. PR #​4067
  • feat: add connectExecutor connection property to customize the Executor used to run the worker task that performs the connection attempt when loginTimeout is in effect. The value is the fully qualified name of a class implementing java.util.concurrent.Executor. With a null value, the default, the driver retains the prior behavior of running the connection attempt on a daemon thread named "PostgreSQL JDBC driver connection thread". The executor must run the task on a thread other than the caller's. Running the attempt on a named thread lets applications that monitor driver-created threads identify it. PR #​4165
  • feat: add classLoaderStrategy connection property to control which classloaders the driver searches when loading a class named by a connection property, for example socketFactory. The default driver-first now falls back to the thread context classloader when the driver's classloader cannot resolve the class, which fixes class loading in non-flat class paths such as Quarkus and OSGi. Set driver to keep the previous driver-classloader-only behaviour, or context-first to prefer the thread context classloader Issue #​2112 PR #​4167
  • feat: add OID constants for geometric arrays, RECORD, and refcursor PR #​4220
  • feat: LargeObject BlobInputStream now skips by seeking instead of reading, and the driver exposes the server version so it can select the 64-bit large-object API where available PR #​4204
Changed
  • refactor: the worker that runs the connection attempt under loginTimeout is now a FutureTask (ConnectTask) instead of the hand-rolled ConnectThread. When the caller hits the timeout, the task is now cancelled with cancel(true), which interrupts the worker thread rather than letting it run to completion. This makes the connection attempt interruptible, so loginTimeout can stop a slow connection attempt instead of leaking a thread. As before, a connection that the worker still manages to establish after the caller gives up is closed by the worker so that it does not leak. There are no public API changes and this should only lead to faster background resource cleanup for connections that time out. PR #​4120
  • chore: PGXAConnection.ConnectionHandler now rejects setAutoCommit(false) and setSavepoint(...) during an active XA branch, in addition to the long-rejected setAutoCommit(true) / commit() / rollback(). The setSavepoint rejection was already meant to be in place but the guard misspelled the method name as setSavePoint, so savepoints silently went through. Both changes bring the proxy in line with JTA 1.2 §3.4. PR #​4114
  • chore: commitPrepared / rollback-of-prepared now return XAER_RMFAIL instead of XAER_RMERR when the underlying connection is left in a non-idle TransactionState. Transaction managers (Geronimo, Narayana, Atomikos) treat XAER_RMFAIL as retryable on a fresh XAResource; the prepared transaction is no longer abandoned. PR #​4114
  • refactor: derive getPrimaryKeys from pg_constraint.conkey PR #​4202
Fixed
  • fix: the published GitHub release now ships the released postgresql-<version>.jar and its detached PGP signature, taken from the same signed build that is uploaded to Maven Central, instead of a leftover SNAPSHOT jar Issue #​3812 PR #​3814
  • fix: simplify the Statement#cancel state machine by dropping the redundant CANCELLED state. killTimerTask now waits for the state to return to IDLE directly, which removes a spin-forever case when more than one thread observes the cancel completing PR #​1827.
  • perf: defer simple-query flushes until the driver reads the response, allowing BEGIN and the following query to share a network flush Issue #​3894 PR #​4196
  • fix: reWriteBatchedInserts no longer throws IllegalArgumentException when batching a parameterless INSERT (for example INSERT INTO t VALUES (1, 2)) of 256 rows or more PR #​4207
  • fix: a comment before CALL in a CallableStatement no longer hides the native call, so OUT parameter registration works for /* comment */ call proc(?, ?) and similar. Parser.modifyJdbcCall now skips leading whitespace and SQL comments (both -- and /* */) before the call, tolerates a trailing comment after a { ... } escape, and no longer adds a spurious comma when moving an OUT parameter into a call whose arguments are only a comment Issue #​2538 PR #​4209
  • fix: PreparedStatement.toString() no longer throws for a bytea value supplied as text via PGobject. Hex-format values (\x...) are validated and rendered as a bytea literal, and escape-format values are quoted and cast like any other literal Issue #​3757 PR #​4201
  • fix: the driver no longer nulls the contextClassLoader of shared ForkJoinPool.commonPool() worker threads, which previously left unrelated tasks on those threads running with a null classloader Issue #​4155 PR #​4156
  • fix: PgResultSet#getCharacterStream wraps String in a StringReader PR #​4063
  • fix: PGXAConnection no longer saves and restores the underlying connection's JDBC autoCommit flag. All XA-protocol SQL (BEGIN, PREPARE TRANSACTION, COMMIT, ROLLBACK, COMMIT PREPARED, ROLLBACK PREPARED, the recover() SELECT) is sent through QUERY_SUPPRESS_BEGIN, so the caller's autoCommit value is invariant across every XAResource call. Fixes the "2nd phase commit must be issued using an idle connection" failure during recovery on managed datasources that pool connections with autoCommit=false (TomEE, WildFly, WebSphere Liberty) PR #​4114
  • fix: PGXAConnection.prepare() now mutates XA state only after PREPARE TRANSACTION succeeds. A failed PREPARE previously left the driver thinking the branch was already prepared, so the follow-up rollback(xid) tried ROLLBACK PREPARED against a non-existent gid and returned XAER_RMERR. Transaction managers (Narayana) escalated this to HeuristicMixedException. With the fix, rollback(xid) takes the active-branch path and issues a plain ROLLBACK, which the server accepts cleanly. Fixes Issue #​3153, Issue #​3123. PR #​4114
  • fix: an updatable result set over an unqualified table name is now classified using only the table visible through search_path. When two schemas held a table with the same name and the same primary or unique index name but a different set of key columns, the driver took the union of both schemas' columns, so the result set could be wrongly rejected as not updatable PR #​4214. Supersedes PR #​3400.
  • fix: LargeObject.close() now flushes a buffered output stream before marking the object closed, so closing a large object without an explicit flush() no longer drops buffered writes. The flush runs while the object is still open (it calls back into LargeObject.write()), and lo_close always runs afterward; a failure from lo_close no longer masks an earlier flush error, and the transaction is not committed when the flush failed Issue #​4247 PR #​4248.
  • fix: reject empty timestamp, timestamptz, and date text with a clear SQLException (SQLState 22007) instead of an ArrayIndexOutOfBoundsException PR #​4278
  • fix: return null CHAR_OCTET_LENGTH for non-character columns PR #​4231
  • fix: honor scale in ResultSet.getBigDecimal(int, int) PR #​4211
  • fix: support java.time values in an updatable ResultSet updateRow() / insertRow() PR #​3848
  • fix: improve batching when the RETURNING clause contains varchar or numeric types PR #​4014
  • fix: correct estimatedReceiveBufferBytes accounting after a forced Sync PR #​4014
  • fix: avoid creating a transient ResultSet for describe-statement purposes, and restore the pre-describe path for generated-key batches PR #​4014
  • fix: add an explicit failure message when a multi-statement command executes in a batch PR #​4014
  • fix: detect search_path changes case-insensitively PR #​4216
  • fix: auto-detect the SSL key format instead of relying on the .key extension PR #​3946
  • fix: build PKIX trust anchors without a KeyStore so FIPS JVMs work PR #​4193
  • fix: use gssResponseTimeout rather than sslResponseTimeout for GSS connections PR #​4076
  • fix: skip the autosave savepoint for SET LOCAL / SET SESSION TRANSACTION PR #​4203
  • fix: do not throw AssertionError from BatchResultHandler on a closed connection PR #​4187
  • fix: reject SQL_TSI_FRAC_SECOND with an explicit, explained error PR #​4229
  • fix: reject a null URL in Driver.acceptsURL with a clear NullPointerException PR #​4205
  • fix: reject overlong inputs in NumberParser.getFastLong instead of silently wrapping PR #​4163
  • fix: reject out-of-range and NaN values in PGInterval.setSeconds PR #​4194
  • fix: close the socket when PgConnection setup fails after connect PR #​4161
  • fix: keep the LazyCleanerImpl cleanup task alive across a transient empty queue PR #​4038
  • fix: append the default non-proxy hosts when socksNonProxyHosts is set PR #​4045
  • fix: clear the ResourceBundle cache on deregister so the driver can unload PR #​4237
  • fix: delete the temp file when spooling a stream to disk fails with an IOException PR #​4190
  • fix: avoid a direct java.lang.management dependency in the maxResultBuffer parser PR #​4069

v42.7.12

Security
Added
  • feat: reWriteBatchedInserts now merges up to 32768 rows into one multi-values INSERT (bounded by the 65535 bind-parameter limit on the extended protocol) instead of capping at 128, which speeds up batches of few-column rows. The new reWriteBatchedInsertsSize connection property lowers that cap when set; the default of 0 uses that maximum.
  • feat: invalidate the prepared-statement cache after CREATE/DROP/ALTER so callers no longer trip on "cached plan must not change result type" without opting into autosave=ALWAYS. Controlled by the new flushCacheOnDdl connection property (default true); set to false for the prior behaviour.
  • feat: add connectExecutor connection property to customize the Executor used to run the worker task that performs the connection attempt when loginTimeout is in effect. The value is the fully qualified name of a class implementing java.util.concurrent.Executor. With a null value, the default, the driver retains the prior behavior of running the connection attempt on a daemon thread named "PostgreSQL JDBC driver connection thread". The executor must run the task on a thread other than the caller's. Running the attempt on a named thread lets applications that monitor driver-created threads identify it.
  • feat: add connectThreadFactory connection property to customize the ThreadFactory used to spawn the worker thread that runs the connection attempt when loginTimeout is in effect. The value is the fully qualified name of a class implementing java.util.concurrent.ThreadFactory. With a null value, the default, the driver retains the prior behavior of using a daemon thread named "PostgreSQL JDBC driver connection thread". Useful for testing timeout behaviour or for applications that want detailed control of all driver-created threads.
  • feat: add classLoaderStrategy connection property to control which classloaders the driver searches when loading a class named by a connection property, for example socketFactory. The default driver-first now falls back to the thread context classloader when the driver's classloader cannot resolve the class, which fixes class loading in non-flat class paths such as Quarkus and OSGi. Set driver to keep the previous driver-classloader-only behaviour, or context-first to prefer the thread context classloader Issue #​2112
Changed
  • refactor: the worker that runs the connection attempt under loginTimeout is now a FutureTask (ConnectTask) instead of the hand-rolled ConnectThread. When the caller hits the timeout, the task is now cancelled with cancel(true), which interrupts the worker thread rather than letting it run to completion. This makes the connection attempt interruptible, so loginTimeout can stop a slow connection attempt instead of leaking a thread. As before, a connection that the worker still manages to establish after the caller gives up is closed by the worker so that it does not leak. There are no public API changes and this should only lead to faster background resource cleanup for connections that time out.
  • chore: PGXAConnection.ConnectionHandler now rejects setAutoCommit(false) and setSavepoint(...) during an active XA branch, in addition to the long-rejected setAutoCommit(true) / commit() / rollback(). The setSavepoint rejection was already meant to be in place but the guard misspelled the method name as setSavePoint, so savepoints silently went through. Both changes bring the proxy in line with JTA 1.2 §3.4.
  • chore: commitPrepared / rollback-of-prepared now return XAER_RMFAIL instead of XAER_RMERR when the underlying connection is left in a non-idle TransactionState. Transaction managers (Geronimo, Narayana, Atomikos) treat XAER_RMFAIL as retryable on a fresh XAResource; the prepared transaction is no longer abandoned.
Fixed
  • fix: the published GitHub release now ships the released postgresql-<version>.jar and its detached PGP signature, taken from the same signed build that is uploaded to Maven Central, instead of a leftover SNAPSHOT jar Issue #​3812 PR #​3814
  • fix: simplify the Statement#cancel state machine by dropping the redundant CANCELLED state. killTimerTask now waits for the state to return to IDLE directly, which removes a spin-forever case when more than one thread observes the cancel completing PR #​1827.
  • perf: defer simple-query flushes until the driver reads the response, allowing BEGIN and the following query to share a network flush Issue #​3894
  • fix: reWriteBatchedInserts no longer throws IllegalArgumentException when batching a parameterless INSERT (for example INSERT INTO t VALUES (1, 2)) of 256 rows or more.
  • fix: a comment before CALL in a CallableStatement no longer hides the native call, so OUT parameter registration works for /* comment */ call proc(?, ?) and similar. Parser.modifyJdbcCall now skips leading whitespace and SQL comments (both -- and /* */) before the call, tolerates a trailing comment after a { ... } escape, and no longer adds a spurious comma when moving an OUT parameter into a call whose arguments are only a comment Issue #​2538
  • fix: PreparedStatement.toString() no longer throws for a bytea value supplied as text via PGobject. Hex-format values (\x...) are validated and rendered as a bytea literal, and escape-format values are quoted and cast like any other literal Issue #​3757
  • fix: the driver no longer nulls the contextClassLoader of shared ForkJoinPool.commonPool() worker threads, which previously left unrelated tasks on those threads running with a null classloader Issue #​4155
  • fix: getCharacterStream wraps String in StringReader PR #​4063
  • fix: PGXAConnection no longer saves and restores the underlying connection's JDBC autoCommit flag. All XA-protocol SQL (BEGIN, PREPARE TRANSACTION, COMMIT, ROLLBACK, COMMIT PREPARED, ROLLBACK PREPARED, the recover() SELECT) is sent through QUERY_SUPPRESS_BEGIN, so the caller's autoCommit value is invariant across every XAResource call. Fixes the "2nd phase commit must be issued using an idle connection" failure during recovery on managed datasources that pool connections with autoCommit=false (TomEE, WildFly, WebSphere Liberty).
  • fix: PGXAConnection.prepare() now mutates XA state only after PREPARE TRANSACTION succeeds. A failed PREPARE previously left the driver thinking the branch was already prepared, so the follow-up rollback(xid) tried ROLLBACK PREPARED against a non-existent gid and returned XAER_RMERR. Transaction managers (Narayana) escalated this to HeuristicMixedException. With the fix, rollback(xid) takes the active-branch path and issues a plain ROLLBACK, which the server accepts cleanly. Fixes Issue #​3153, Issue #​3123.
  • fix: an updatable result set over an unqualified table name is now classified using only the table visible through search_path. When two schemas held a table with the same name and the same primary or unique index name but a different set of key columns, the driver took the union of both schemas' columns, so the result set could be wrongly rejected as not updatable PR #​4214. Supersedes PR #​3400.
oshai/kotlin-logging (io.github.oshai:kotlin-logging-jvm)

v8.0.4

Compare Source

Align to semver.

Full Changelog: oshai/kotlin-logging@8.0.03...8.0.4

v8.0.03

Compare Source

What's Changed

  • Fix #​598: Allow external configuration of logStartupMessage via Properties and Env Vars by @​oshai in #​602

Full Changelog: oshai/kotlin-logging@8.0.02...8.0.03

v8.0.02

Compare Source

What's Changed

  • Fix GraalVM native build error caused by stale substitution target in v8.x by @​Copilot in #​601

Full Changelog: oshai/kotlin-logging@8.0.01...8.0.02

reformator14/stacktrace-decoroutinator (dev.reformator.stacktracedecoroutinator:stacktrace-decoroutinator-jvm)

v2.6.4: 2.6.4

fix #​81

v2.6.3: 2.6.3

fix #​79

JetBrains/kotlin (org.jetbrains.kotlin.plugin.serialization)

v2.4.0

v2.3.21: Kotlin 2.3.21

Changelog
Backend. Wasm
  • KT-84610 [Wasm] Failed to compile klibs in IC mode
Compiler
  • KT-84566 Prevent launching Default dispatcher threads from IJ SDK in kotlin compiler
  • KT-85358 Native: roll back the workaround for KT-84678 once MapLibre has been properly fixed
  • KT-85626 @JvmRecord in commonMain breaks compileCommonMainKotlinMetadata with "Cannot access 'java.lang.Record'"
  • KT-85405 Postpone/Revert DontIgnoreUpperBoundViolatedOnImplicitArguments
  • KT-84678 K/N: Undefined symbol from SPM-added ObjC frameworks when linking iOS target
  • KT-85021 False positive SUBCLASS_CANT_CALL_COMPANION_PROTECTED_NON_STATIC error in multi-module project
JavaScript
  • KT-82395 Support top-level declarations from compiler plugins in JS incremental compilation
  • KT-84475 K/JS: false-positive exportability warnings in multi-module project
  • KT-84633 Kotlin/JS: "Serializer for class not found" error when IR output granularity is whole-program
  • KT-85047 Kotlin/JS: @JsStatic on suspend fun of class companion generates incorrect d.ts
  • KT-84517 K/JS: bad mappings data in outputted Kotlin stdlib source map
Libraries
  • KT-71848 Kotlinx.metadata: Add CompilerPluginData into Km API
Native. C and ObjC Import
  • KT-85399 Kotlin/Native: TypeCastException when casting ObjC Protocol MetaClass with genericSafeCasts enabled
  • KT-85508 K/N: TypeCastException when using nw_parameters_create_secure_tcp block parameter on 2.3.20
Tools. Gradle
  • KT-84729 Update Gradle plugin-publish version to enable configuration cache badge on Gradle plugins portal
Tools. Gradle. Compiler plugins
  • KT-85257 AGP/Compose: MergeMappingFileTask clears R8 artifacts due to @OutputDirectory annotation on AGP 9.1+
Tools. Scripts
  • KT-85105 Scripts: JVM backend internal error (IR lowering) when scratch file contains anonymous object
  • KT-85103 Exception while generating code when explain destructuring decls
  • KT-84842 scriptCompilationClasspathFromContext behavior changed from 2.3.10 to 2.3.20
  • KT-85029 Kotlin Scripting: ScriptDiagnostic reports "at null" instead of error location
Tools. Statistics (FUS)
  • KT-85628 KGP: composite build FUS metrics fail on access of 'configurationTimeMetrics'

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot changed the title Update Minor & patch dependency updates to v12.4.0 Update Minor & patch dependency updates Apr 23, 2026
@renovate renovate Bot force-pushed the renovate/minor-and-patch-dependency-updates branch 5 times, most recently from 0884d07 to f8b6641 Compare April 28, 2026 23:40
@renovate renovate Bot force-pushed the renovate/minor-and-patch-dependency-updates branch 3 times, most recently from 45abaa7 to a1fbc81 Compare May 6, 2026 18:38
@renovate renovate Bot force-pushed the renovate/minor-and-patch-dependency-updates branch 2 times, most recently from 445a9f5 to ec9651f Compare May 12, 2026 16:01
@renovate renovate Bot force-pushed the renovate/minor-and-patch-dependency-updates branch 2 times, most recently from e70a9a6 to 07f79a5 Compare May 21, 2026 13:33
@renovate renovate Bot force-pushed the renovate/minor-and-patch-dependency-updates branch 5 times, most recently from d191587 to 93db640 Compare June 3, 2026 10:32
@renovate renovate Bot force-pushed the renovate/minor-and-patch-dependency-updates branch 6 times, most recently from 87b6df0 to 8021a62 Compare June 8, 2026 17:14
@renovate renovate Bot force-pushed the renovate/minor-and-patch-dependency-updates branch 2 times, most recently from 1e3002d to af72a4e Compare June 18, 2026 17:59
@renovate renovate Bot force-pushed the renovate/minor-and-patch-dependency-updates branch 3 times, most recently from 0675ef0 to 4445aa5 Compare June 25, 2026 22:12
@renovate renovate Bot force-pushed the renovate/minor-and-patch-dependency-updates branch 4 times, most recently from dd80658 to 0380bbf Compare July 1, 2026 22:02
@renovate renovate Bot force-pushed the renovate/minor-and-patch-dependency-updates branch 3 times, most recently from 2a7e789 to 46548f9 Compare July 9, 2026 09:16
@renovate renovate Bot force-pushed the renovate/minor-and-patch-dependency-updates branch from 46548f9 to 736b797 Compare July 9, 2026 17:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants