build(deps): Bump the dev-dependencies group with 5 updates

[dependabot]

Bumps the dev-dependencies group with 5 updates:

Package	From	To
software.amazon.awssdk:dynamodb	2.49.0	2.49.5
software.amazon.awssdk:dynamodb-enhanced	2.49.0	2.49.5
com.diffplug.spotless:spotless-plugin-gradle	8.8.0	8.9.0
com.diffplug.spotless	8.8.0	8.9.0
ch.qos.logback:logback-classic	1.5.38	1.6.1

Updates software.amazon.awssdk:dynamodb from 2.49.0 to 2.49.5

Updates software.amazon.awssdk:dynamodb-enhanced from 2.49.0 to 2.49.5

Updates software.amazon.awssdk:dynamodb-enhanced from 2.49.0 to 2.49.5

Updates com.diffplug.spotless:spotless-plugin-gradle from 8.8.0 to 8.9.0

Release notes

Sourced from com.diffplug.spotless:spotless-plugin-gradle's releases.

Gradle Plugin v8.9.0

Added

• Add support for Java formatting via prince-of-space with the new princeOfSpace() step. (#2991)

Fixed

• Prevent parallel Gradle input fingerprinting from failing when toggleOffOn() wraps a slow lazy formatter step with no matching target files. (#2994)

Changes

• Bump default greclipse version to latest 4.39 -> 4.40. (#2989)
• Bump default tabletest-formatter version 1.1.1 -> 1.1.2.

Commits

• cbd01c4 Published gradle/8.9.0
• c724e70 Published lib/4.9.0
• 793638d Replace de.atextor:turtle-formatter with cool.rdf:cool-rdf-formatter (#2995)
• 3cb7227 Note Java 25+ requirement for RDF formatter; tidy changelogs
• fd9eb96 Merge remote-tracking branch 'origin/main' into use-cool-rdf-formatter
• d407109 Add support for prince-of-space Java formatter (#2991)
• cb64859 Merge remote-tracking branch 'origin/main' into use-cool-rdf-formatter
• f88db43 Bump tabletest-formatter to 1.1.2 (#3001)
• ec7db39 Bump tabletest-formatter to 1.1.2
• a0e59b6 Remove the round of tests for JRE 25 (breaks elsewhere)
• Additional commits viewable in compare view

Updates com.diffplug.spotless from 8.8.0 to 8.9.0

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

Release notes

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

Logback 1.6.1

2026-07-28 Release of logback version 1.6.1

• In TimeBasedRollingPolicy, when the file option is set, the intermediate file renamed before asynchronous compression now receives the target archive name without the compression suffix (e.g. .gz, .zip, .xz). Previously it used a nanotime-based .tmp suffix. This makes the file easier to identify if compression fails during rollover. (See also the following paragraph.)

• On GZ, ZIP, or XZ compression failure, the original (uncompressed) log file is no longer deleted. Compression strategies now delete the source file only after successful compression and emit a warning that the original was left intact.

• ConsoleAppender with now probes JLine's org.jline.jansi.AnsiConsole first and falls back to the legacy FuseSource org.fusesource.jansi.AnsiConsole class. This keeps ANSI coloring working after Jansi moved under the JLine project. The optional org.jline:jansi-core artifact is declared as a dependency alongside the existing FuseSource jansi dependency. A preferredJansiClassName property was added for tests. This issue was reported in issues/1043 by seonwoo_jung who also provided the relevant PR.

• LayoutWrappingEncoder now reports an error at start() when no layout is set and guards encode() against a null layout. Previously, a missing layout (for example after an ignored // branch) allowed the encoder to start and then fail with a NullPointerException on every event, resulting in silent log loss. This issue was reported in issues/1046 by seonwoo_jung who also provided the relevant PR.

• FileCollisionAnalyser now detects file collisions involving nested appenders of SiftingAppender. When the nested file or fileNamePattern does not textually reference the discriminator key (e.g. ${userId}), a warning is issued at configuration time naming the appender, the key, and the shared target. This closes a gap where statically declared file appenders were checked but sifted nested appenders were not. This enhancement was contributed in [PR #1041](qos-ch/logback#1041) by seonwoo_jung.

• More defensive handling in SyslogOutputStream and SyslogAppenderBase: the close() method now ensures that resources are closed, writes and flushes check that the underlying resources are in a valid state and fallback to no-op otherwise.

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

• See https://logback.qos.ch/news.html#1.6.1 for the original text.

Logback 1.6.0

2026-07-23 Release of logback version 1.6.0

• Removed certain deprecated variables, methods, and classes. For the list of removed members see release_1.6.0.txt.

• In AsyncAppenderBase, the put(ILoggingEvent) method now has the protected modifier to allow access from derived classes. This change was requested by Thomas Skjølberg in pr#1053.

• Bump SLF4J dependency to version 2.0.18.

• See also the overview of the 1.6.x series.

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

Commits

• 57759f4 prepare release 1.6.1
• 175f99f fix imports
• 4b8773e add compressionFailureLeavesOriginalFileIntact test for XZ compression
• cafaf11 do not delete original file if compression fails
• ee50125 let the temporary file before compression be target file without the .gz or ....
• 5626acc minor refactoring
• d97da4f minor refactoring
• 159c045 more defensive coding in SyslogOutputStream and in SyslogAppenderBase
• 9427d6b slight refactoring for clarity
• 79c4179 slight refactoring
• Additional commits viewable in compare view

Updates com.diffplug.spotless from 8.8.0 to 8.9.0

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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

[wolpert]

Diagnosis: of the three bumps here, only logback 1.5.38 → 1.6.1 is the problem. spotless 8.9.0 and aws-sdk 2.49.5 are fine.

logback 1.6.0 removed ch.qos.logback.classic.PatternLayout.DEFAULT_CONVERTER_MAP, which Dropwizard 5's dropwizard-request-logging reads in a static initializer:

java.lang.NoSuchFieldError: Class ch.qos.logback.classic.PatternLayout
  does not have member field 'java.util.Map DEFAULT_CONVERTER_MAP'
  at io.dropwizard.request.logging.layout.LogbackAccessRequestLayout.<clinit>(LogbackAccessRequestLayout.java:20)
  at io.dropwizard.request.logging.layout.LogbackAccessRequestLayoutFactory.build(...:16)
  at io.dropwizard.request.logging.LogbackAccessRequestLogFactory.build(...:80)

That one incompatibility accounts for both failing checks — the 16 :pk-auth-dropwizard integration-test failures in build (every test that boots the app), and e2e (dropwizard-demo), where :examples:dropwizard-demo:run dies at startup with the same trace.

Dropwizard 5.0.2 resolves logback-classic:1.5.33 and the catalog force-upgrades it to 1.6.1. Dropwizard 5.0.2 is the newest release on Maven Central, so there's no upgrade path out of the conflict yet.

Verified locally: on this branch, reverting only logback to 1.5.38 makes ./gradlew :pk-auth-dropwizard:test pass, with the other two bumps left in place.

Fix is in #140 — an ignore for ch.qos.logback:* on minor and major updates (1.5 → 1.6 is semver-minor, so a major-only ignore wouldn't catch it). Once that merges, recreating this PR will regenerate it with just spotless + aws-sdk.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.