[renovate]

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
io.micrometer:micrometer-registry-prometheus	1.16.5 → 1.17.2
io.github.freya022:BotCommands-jda-ktx (source)	3.1.0 → 3.4.0
com.google.code.gson:gson	2.13.2 → 2.15.0
io.github.freya022:BotCommands	3.1.0 → 3.4.0
net.dv8tion:JDA	6.4.1 → 6.7.0
org.flywaydb:flyway-database-postgresql	12.3.0 → 12.11.0
org.flywaydb:flyway-core	12.3.0 → 12.11.0
com.zaxxer:HikariCP	7.0.2 → 7.1.0
org.postgresql:postgresql (source)	42.7.12 → 42.7.14
ch.qos.logback:logback-classic (source, changelog)	1.5.32 → 1.6.6
io.github.oshai:kotlin-logging-jvm	8.0.01 → 8.0.4
dev.reformator.stacktracedecoroutinator:stacktrace-decoroutinator-jvm	2.6.2 → 2.6.6
com.google.cloud.tools.jib	3.5.3 → 3.5.4
com.palantir.git-version	5.0.0 → 5.1.0
org.jetbrains.kotlin.plugin.serialization (source)	2.3.20 → 2.4.21
org.jetbrains.kotlin.jvm	2.3.20 → 2.4.21

---

Release Notes

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

v1.17.2: 1.17.2

🐞 Bug Fixes

• Preserve whitespace in HTTP Basic authentication passwords #​8015
• Missing reflection hint for getProcessCpuTime #​7911
• Proxy JMS session results using the method's declared return type #​7896
• Kotlin interoperability for CaffeineCacheMetrics broken/requires unchecked cast to work #​7582
• Registering/Updating a MultiGauge while a Prometheus scrape occurs can lead to DuplicateLabelsException #​6851
• OTLP histogram bucket count does not equal count intermittently #​6006
• Statsd UDP epoll warn logs are verbose when statsd is down #​2624

📔 Documentation

• Fix typos in docs #​8000
• Add docs for @MeterTag when used on a method #​7829
• Document best practice about configuring registries on a composite #​7367
• Documentation on SpelValueExpressionResolver is unclear #​6465
• Document how to customize tags in micrometer-java11 HttpClient instrumentation #​4962

🔨 Dependency Upgrades

• Bump io.netty:netty-bom from 4.2.18.Final to 4.2.19.Final #​8042

❤️ Contributors

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

@​Gaurav1112, @​LindseyZ1205, @​bogdandrutu, @​pchesneau, @​cfcromn, @​schiemon, @​officialasishkumar, @​AzazelSensei, @​nick-montana, @​ghdtjdwn, @​ninadsutrave

v1.17.1: 1.17.1

🐞 Bug Fixes

• ClassNotFoundException: org.LatencyUtils.PauseDetector is thrown when introspecting AbstractTimer #​7815
• Prometheus custom meters: creation timestamps are incorrect #​7798
• Fix memory leak/NPE in MicrometerHttpClientInterceptor (HC4 & HC5)
• Sanitize line terminators in Dogstatsd, Etsy StatsD, and LoggingMeterRegistry

🔨 Dependency Upgrades

• Bump io.netty:netty-bom from 4.2.15.Final to 4.2.17.Final #​7822
• Bump software.amazon.awssdk:cloudwatch from 2.46.6 to 2.46.21 #​7705

📝 Tasks

• Fix ineffective ExemplarSampler cache in DefaultExemplarSamplerFactory #​7657
• Note micrometer-jetty11 deprecation in the artifact description #​7651

❤️ Contributors

Thank you to all the contributors who worked on this release:
@​arimu1, @​kalayciburak

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.8: 1.16.8

🐞 Bug Fixes

• Preserve whitespace in HTTP Basic authentication passwords #​8015
• Missing reflection hint for getProcessCpuTime #​7911
• Proxy JMS session results using the method's declared return type #​7896
• Kotlin interoperability for CaffeineCacheMetrics broken/requires unchecked cast to work #​7582
• Registering/Updating a MultiGauge while a Prometheus scrape occurs can lead to DuplicateLabelsException #​6851
• OTLP histogram bucket count does not equal count intermittently #​6006
• Statsd UDP epoll warn logs are verbose when statsd is down #​2624

📔 Documentation

• Fix typos in docs #​8000
• Add docs for @MeterTag when used on a method #​7829
• Document best practice about configuring registries on a composite #​7367
• Documentation on SpelValueExpressionResolver is unclear #​6465
• Document how to customize tags in micrometer-java11 HttpClient instrumentation #​4962

🔨 Dependency Upgrades

• Bump io.netty:netty-bom from 4.1.138.Final to 4.1.139.Final #​8040

❤️ Contributors

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

@​Gaurav1112, @​LindseyZ1205, @​bogdandrutu, @​pchesneau, @​cfcromn, @​schiemon, @​officialasishkumar, @​AzazelSensei, @​nick-montana, @​ghdtjdwn, @​ninadsutrave

v1.16.7: 1.16.7

🐞 Bug Fixes

• Prometheus custom meters: creation timestamps are incorrect #​7798
• Fix memory leak/NPE in MicrometerHttpClientInterceptor (HC4 & HC5)
• Sanitize line terminators in Dogstatsd, Etsy StatsD, and LoggingMeterRegistry

🔨 Dependency Upgrades

• Bump io.netty:netty-bom from 4.1.135.Final to 4.1.137.Final #​7823

📝 Tasks

• Fix ineffective ExemplarSampler cache in DefaultExemplarSamplerFactory #​7657
• Note micrometer-jetty11 deprecation in the artifact description #​7651

❤️ Contributors

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

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.4.0: | File type filtering & custom events

Updated to JDA 6.6.0, added support for file type filtering, and opt-in support for custom events.

File type filtering in slash command attachment options and modal attachment uploads (#​268)

You can now restrict which file types are allowed in attachment uploads.

New features

• Added @FileTypes, accepts extensions and/or switches for certain media types
• Added a fileTypes property to declarative slash command option builders, example:
  • fileTypes += "json"
  • fileTypes += FileType.IMAGE
• Added a fileTypes property to the AttachmentUpload DSL, it is used the same as with slash commands

Support for custom events (#​271)

It is now allowed to make listeners of any type. (except Any/Object)

Users who wish to listen to custom events must have at least one CustomEventRequirementsProvider,
which must return the requirements for the provided event type.

Note: This API is considered experimental and requires an opt-in.

---

Deprecations

jda-ktx

• Deprecated Mentions#getChannelsBag, replaced with getChannelsMultiSet

App. commands. DSL

• Deprecated range infix functions of ValueRange and LengthRange

New feature

App. commands. DSL

• valueRange and lengthRange functions were added accepting standard Kotlin ranges

Changes

App. commands

• Errors when initializing the commands cache now throws for large bots to avoid sending a ton of requests
  • For smaller bots, it falls back to an in-memory cache as usual

---

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

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

---

Installation

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

Kotlin Gradle

repositories {
    mavenCentral()
}

dependencies {
    implementation("io.github.freya022:BotCommands:3.4.0")
}

Maven

<dependency>
    <groupId>io.github.freya022</groupId>
    <artifactId>BotCommands</artifactId>
    <version>3.4.0</version>
</dependency>

v3.3.0

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

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

---

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.7.0: | Handle Channel Obfuscation

Overview

This release makes JDA aware of Channel Obfuscation, which will become mandatory on November 16, 2026.

You can test your bot early by enabling channel obfuscation in the discord developer portal.

[!WARNING]
This is a breaking change, which affects permission handling and what will be available to your bot. Please report any bugs / unexpected results you might encounter with JDA behavior.

Channels for interactions will use snapshots of the channel instead, utilizing the IDetachableEntity handling previously introduced for user-installed commands. These channels carry the current information about the channel, such as name and topic. They also have the permissions for the member that used the interaction, to allow permission checks to still work as expected for that specific member through member.hasPermission(channel, permissions).

Breaking Changes

• Add handling for obfuscated channels by @​MinnDevelopment in #​3042

Full Changelog: discord-jda/JDA@v6.6.0...v6.7.0

Installation

Gradle

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

Maven

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

v6.6.0

Overview

This is a minor release adding a few new features before a bigger change coming in 6.7.0 which will introduce handling for Obfuscated Channels.

If you can, please try out and give feedback on Add handling for obfuscated channels #​3042. To enable obfuscated channels early for testing purposes, you can toggle a switch in your application dashboard as described here.

New Features

• Add file type filtering in slash command attachment options and modal attachment uploads by @​freya022 in #​3113
• Add support for guild member banners by @​Whizyyy in #​3126

Changes

• Make LabelChildComponent replaceable by @​Kaktushose in #​3128
• Read flags_new of ApplicationInfo instead of flags by @​freya022 in #​3131
• Guild member pruning: Check for admin if PRUNE_REQUIRES_ADMIN is enabled by @​freya022 in #​3129
• Update Message.MAX_FILE_SIZE to 20 MiB by @​freya022 in #​3142

Bug Fixes

• Fix MarkdownUtil#monospace not correctly applying monospace formatting to strings with backticks by @​ManosSef in #​3139
• Fix icon URLs for GIF stickers by @​jjj-n in #​3140

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

Installation

Gradle

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

Maven

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

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

• Add message search by @​freya022 in #​3052
• Add attachment flags by @​MinnDevelopment in #​3109
• Add support for image descriptions in embeds by @​MinnDevelopment in #​310

Changes

• Handle messages received after ban by @​MinnDevelopment in #​3103

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

• Add attachment flags, embed flags and fields, and, media flags by @​freya022 in #​3081
• Add missing NO_MUTUAL_GUILDS ErrorResponse by @​srnyx in #​3083
• Add ErrorResponse#CANNOT_FORWARD_UNREADABLE_MESSAGE by @​freya022 in #​3087

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

• Fix Guild#invalidate not removing thread channels from global cache by @​MinnDevelopment in #​3094
• Fix incorrect ID used in AbstractGuildChannelImpl#getGuild for entity parent refresh by @​MinnDevelopment in #​3095
• Fix incorrect check for choice value length by @​MinnDevelopment in #​3096
• fix: handle integer sound ids in voice channel effects by @​rxsto in #​3085

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

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.6: 2.6.6

Fixes

• #​85: fix a 2.6.5 regression where Ktor pipelines (and other cases reusing a shared continuation object across nested spec-chain levels) could throw "invalid line number: 0" and hang (61f4260, 36069f0, e163df2) — the spec-reuse mechanism could process the same continuation object twice within one call chain, resetting its line-number field before it was consumed again; a new resumeChecksum/depthChecksum protocol now detects this and falls back to a guaranteed-safe retry instead of corrupting the result or hanging.
• #​87: don't crash when a transformed class's own methods can't be reflected (e31336b) — if Class.getDeclaredMethods() throws NoClassDefFoundError (seen on Android when a method signature references a type only present at a higher API level), the class is now simply left unregistered and falls back to slower runtime spec-method generation instead of crashing.

JVM agent improvements

• jvm-agent can now be started reliably even when kotlin-stdlib isn't visible on the system classpath (32f3669).

Internal

• Safer base continuation transformation (3d7009a).
• Relocated jvm-agent's entire package namespace (32f3669) so its shaded jar can never shadow another consumer's real classes sharing the same package when statically attached to an arbitrary host JVM — verified in CI by dogfooding the agent against the build that produces it.
• Fixed a null CodeSource crash when jvm-agent is attached to IntelliJ IDEA's own process (c3978e3).
• Fixed ServiceLoader construction throwing uncaught on Android's core-library-desugared backport (fe28c20).
• Added a "regular" base-continuation-accessor fast path for jvm and jvm-agent (e999b98), replacing reflective MethodHandle lookups with a pre-compiled accessor class.
• jvm-agent now dispatches per target classloader (17e3e79) rather than per calling classloader.
• Minimized jvm-agent's size (9f1c700).
• Moved the process-wide DI/registry/settings-cache singletons from common into provider (3bd0e43).
• Expanded RemoveKotlinStdlibProcessor's allowlist (7356988).
• Added a delete-signature-checksums Gradle plugin (47d53a2) to drop redundant checksum files from Maven Central publications.

v2.6.5: 2.6.5

Performance and memory usage improvements

• Lazy per-instance continuation caching (d563476) — added a LazilyCachedContinuation mechanism for kotlinx.coroutines internal classes whose real stack-trace element genuinely varies per instance, computed and cached once on first use (complements the existing eager ManualContinuation caching for classes whose value is class-wide constant).
• Expanded ManualContinuation coverage (c226066) — patched a few more kotlinx.coroutines internal classes.
• Simplified class-identity check ([e76c6a8](https://re

[!IMPORTANT]
✂ PR body was truncated to here.

---

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.