deps: bump the library-dependencies group across 1 directory with 4 updates

[dependabot]

Bumps the library-dependencies group with 4 updates in the / directory: io.github.darkryh.katalyst:katalyst-conventions, ch.qos.logback:logback-classic, org.slf4j:slf4j-api and dev.kourier:amqp-client-robust-jvm.

Updates io.github.darkryh.katalyst:katalyst-conventions from 1.0.0-alpha02 to 1.0.0-beta04

Release notes

Sourced from io.github.darkryh.katalyst:katalyst-conventions's releases.

1.0.0-beta02

A maintenance release, and a small one. No framework code changed — every src/main file in this repository is byte-identical to beta01, and the API dumps agree. What moves is the terminal UI's dependency, and where the modules sit on disk.

dependencies {
    implementation(platform("io.github.darkryh.katalyst:katalyst-bom:1.0.0-beta02"))
}

What you actually get

The terminal UI stops presenting half-drawn frames. katalyst-tui now builds against Dispatch 1.0.0-beta04, which fixes the renderer showing a frame mid-composition — you'd have seen it as a flicker, or a torn row, while a screen redrew. That is the whole functional change in this release: if your application doesn't use katalyst-tui, upgrading gets you nothing but a version number, and staying on beta01 costs you nothing either.

Housekeeping

The repository is reorganised and your build does not notice. The modules had accumulated flat at the repository root; they are now grouped by what they do — http/, data/, config/, observability/, testing/, starter/, platform/, tools/, web/ — with the core modules left where they were and samples/ kept at the top level so it stays easy to find.

A Gradle project's name is independent of the directory it lives in, so this is invisible from the outside: every published coordinate is unchanged. That was measured against a pre-move baseline rather than assumed — identical project list, the same 39 published POMs, and a byte-identical BOM carrying the same 36 constraints.

If you contribute to Katalyst, re-run Reload All Gradle Projects after pulling.

Verification

2 420 tests across the published modules, zero failures, apiCheck green — and 2 512 counting the sample application, the consumer-smoke harness, the IntelliJ plugin and the initializr build.

Moving the modules invalidated Gradle's up-to-date checks, which forced suites to genuinely execute that had been reporting as cached — and that surfaced two latent defects. Neither is in shipped code; both are fixed here.

An events-bus test collected handler output into a plain ArrayList while the bus ran those handlers in parallel, so a concurrent append could drop an entry and fail the assertion at random. It had been passing only in the sense that it was never actually running.

Separately, the IntelliJ plugin's test sources had silently stopped compiling — IntelliJ Platform Gradle Plugin 2.x no longer contributes JUnit 4 to the test classpath transitively. Nothing caught it because that workflow only triggers when plugin files change, and they hadn't.

... (truncated)

Commits

• d87728e chore(release): cut 1.0.0-beta04
• a12e8a8 test(persistence): drive the quiesce wait off the connection, not the clock
• 6fd256b test(di): wait for the worker to poll instead of sleeping for it
• a3f9b38 docs: document the shutdown phase
• 45c5bb4 fix(di): tear Katalyst down after the application's own stop handlers
• 8002e5d feat(di): give the application a shutdown lifecycle
• a2e8e4e feat(persistence): let the connection pool go quiet before it closes
• fd9c836 chore(release): cut 1.0.0-beta03
• b3cd988 fix(tui): make the selected slash command unmistakable
• 669bb0a build(deps): bump dispatch to 1.0.0-beta05
• Additional commits viewable in compare view

Updates ch.qos.logback:logback-classic from 1.6.1 to 1.6.3

Release notes

Sourced from ch.qos.logback:logback-classic's releases.

Logback 1.6.3

2026-08-14 Release of logback version 1.6.3

• In response CVE-2026-19880, MDCBasedDiscriminator (used by SiftingAppender) now strips forward and backward slashes (/, \) from MDC values before they are used as discriminating keys. This prevents path segments from escaping into destinations controlled by an attacker. When sanitisation actually changes a value, a warning is emitted; the warning is rate-limited (a small batch, then a lull of about ten minutes).

• Colour console support is split out into a dedicated JansiConsoleAppender. It wraps stdout or stderr with Jansi so ANSI escape sequences (for example coloured patterns) render correctly on terminals that need it, notably Windows. Prefer this class over the older path described next. See the appenders documentation.

• The withJansi property on ConsoleAppender is deprecated. Existing configurations that still set <withJansi>true</withJansi> continue to work for compatibility, but new setups should use JansiConsoleAppender instead.

• ConsoleAppender no longer treats the process console as an exclusive resource: stopping it does not close System.out / System.err. JansiConsoleAppender pairs each AnsiConsole.systemInstall() with systemUninstall() on stop, so repeated start/stop cycles do not leave Jansi installed or tear down streams shared with the rest of the JVM. Related behavior is covered by tests for issues/1063.

• Invocation throttling helpers were reworked: SimpleInvocationGate is renamed FixedIntervalInvocationGate, and BatchedFixedIntervalInvocationGate allows a short burst of invocations before applying a fixed lull. The sanitisation warning above uses the batched gate.

• The JPMS module-info for logback-core now exports the ch.qos.logback.core.property package, which had been missing from the module descriptor.

• A bit-wise identical binary of this version can be reproduced by building from source code at commit e8e824dede022a6d7208b36cfa875b0d1b7772f3 associated with the tag v_1.6.3. The release was built using Java "21" 2023-10-17 LTS build 21.0.1.+12-LTS-29 under Linux Debian 11.6.

-- Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch

Logback 1.6.2

clean.full.1.6.2.mp4

2026-08-10 Release of logback version 1.6.2

• Configuration analysis now detects contradictory caller-data inclusion instructions. For example, an AsyncAppender, SocketAppender or SMTPAppender with includeCallerData left at the default false is incompatible with a layout or encoder pattern that uses a caller-data converter such as %C, %M, %L, %F, %l or %caller. At runtime those converters would print question marks and still incur extraction cost on a worker thread. Logback now emits a configuration-time warning when such instructions disagree. See codes.html#callerContradiction for details. This issue was reported in issues/1059 by leeychee. The initial analysis was contributed by seonwoo_jung.

• Caller-contradiction analysis can be turned off by setting the logback.skipCallerContradictionAnalysis variable to true, either as a system property (-Dlogback.skipCallerContradictionAnalysis=true) or as a property in the configuration file:

  <property name="logback.skipCallerContradictionAnalysis" value="true"/>

• SimpleSocketServer and SimpleSSLSocketServer now require an explicit client IP whitelist. On the command line, pass one or more allowed addresses (single IPs or CIDR ranges) after the configuration file. An empty whitelist means no clients are accepted. When embedding the server programmatically, register allowed addresses with addAllowedClientAddress(String) or setAllowedClientAddresses(Collection) before clients connect. See the documentation on restricting client access.

• Added ThrowableProxyVOBuilder for assembling a ThrowableProxyVO field by field, with a corresponding ThrowableProxyVO.builder() entry point.

• Dependency analysis handlers now run their postHandle method after child models have been processed, so checks that depend on nested appenders (such as caller-contradiction analysis) see a complete picture.

• Updated several dependencies, including Angus Mail to 2.0.4 and Jetty (test) to 12.1.12.

• A bit-wise identical binary of this version can be reproduced by building from source code at commit e3d78330ad1ba024fd987fd00c3ffb9cfcdb07dc associated with the tag v_1.6.2. The release was built using Java "21" 2023-10-17 LTS build 21.0.1.+12-LTS-29 under Linux Debian 11.6.

Commits

• e8e824d prepare release 1.6.3
• 761821b MDCBasedDiscriminator has a gated warning mechanism
• 53ed122 update copyright year
• c7e2db2 rename SimpleInvocationGate as FixedIntervalInvocationGate
• b5aa931 added BatchedSimpleInvocationGate
• 1f22af7 add javadocs to SimpleInvocationGate
• 638ffa7 prevent forward and backward slashes to escape to other directories
• 7d6b9a4 add missing ch.qos.logback.core.property package
• fa25930 add an extension path in ConsoleAppender for JansiConsoleAppender
• c73b43f deprecate the withJansi path
• Additional commits viewable in compare view

Updates org.slf4j:slf4j-api from 2.0.17 to 2.0.18

Updates dev.kourier:amqp-client-robust-jvm from 0.4.6 to 0.4.7

Release notes

Sourced from dev.kourier:amqp-client-robust-jvm's releases.

0.4.7

What's Changed

• fix: re-declare server-named queues on channel restore by @​Lyesbcb in kourier-amqp/kourier#68

New Contributors

• @​Lyesbcb made their first contribution in kourier-amqp/kourier#68

Full Changelog: kourier-amqp/kourier@0.4.6...0.4.7

Commits

• d4ce133 v0.4.7
• 597321d fix: re-declare server-named queues on channel restore (#68)
• See full diff in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions