Skip to content

build: bump the gradle-minor-and-patch group with 8 updates - #23

Merged
github-actions[bot] merged 1 commit into
mainfrom
dependabot/gradle/gradle-minor-and-patch-87c0d32cf5
Oct 22, 2026
Merged

build: bump the gradle-minor-and-patch group with 8 updates#23
github-actions[bot] merged 1 commit into
mainfrom
dependabot/gradle/gradle-minor-and-patch-87c0d32cf5

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 22, 2026

Copy link
Copy Markdown
Contributor

Bumps the gradle-minor-and-patch group with 8 updates:

Package From To
tools.jackson.core:jackson-databind 3.2.3 3.2.4
tools.jackson.dataformat:jackson-dataformat-yaml 3.2.3 3.2.4
com.codeheadsystems:pk-auth-core 2.3.0 2.3.1
com.codeheadsystems:pk-auth-jwt 2.3.0 2.3.1
com.codeheadsystems:pk-auth-magic-link 2.3.0 2.3.1
com.codeheadsystems:pk-auth-otp 2.3.0 2.3.1
com.codeheadsystems:pk-auth-backup-codes 2.3.0 2.3.1
com.codeheadsystems:pk-auth-testkit 2.3.0 2.3.1

Updates tools.jackson.core:jackson-databind from 3.2.3 to 3.2.4

Commits
  • 461f8ec [maven-release-plugin] prepare release jackson-databind-3.2.4
  • 2a502c9 Prep for 3.2.4 release
  • 64a4813 Merge branch '3.1' into 3.2
  • 5d64697 Post-release dep version bump
  • 9b5fe86 [maven-release-plugin] prepare for next development iteration
  • 893c391 [maven-release-plugin] prepare release jackson-databind-3.1.8
  • 22442d0 Prep for 3.1.8 release
  • df230c1 Merge branch '2.x' into 3.1
  • 69ddc80 Merge branch '2.22' into 2.x
  • 72bb78e Post-release dep version bump
  • Additional commits viewable in compare view

Updates tools.jackson.dataformat:jackson-dataformat-yaml from 3.2.3 to 3.2.4

Commits
  • 0733be3 [maven-release-plugin] prepare release jackson-dataformats-text-3.2.4
  • 3d387c6 Prep for 3.2.4 release
  • bb8b703 Merge branch '3.1' into 3.2
  • e2b0d13 Post-release dep version bump
  • 621486d [maven-release-plugin] prepare for next development iteration
  • 1a9f03b [maven-release-plugin] prepare release jackson-dataformats-text-3.1.8
  • 87a85a8 Prep for 3.1.8 release
  • 255785a Merge branch '2.x' into 3.1
  • a4ae420 Merge branch '2.22' into 2.x
  • 55d3e60 Post-release dep version bump
  • Additional commits viewable in compare view

Updates tools.jackson.dataformat:jackson-dataformat-yaml from 3.2.3 to 3.2.4

Commits
  • 0733be3 [maven-release-plugin] prepare release jackson-dataformats-text-3.2.4
  • 3d387c6 Prep for 3.2.4 release
  • bb8b703 Merge branch '3.1' into 3.2
  • e2b0d13 Post-release dep version bump
  • 621486d [maven-release-plugin] prepare for next development iteration
  • 1a9f03b [maven-release-plugin] prepare release jackson-dataformats-text-3.1.8
  • 87a85a8 Prep for 3.1.8 release
  • 255785a Merge branch '2.x' into 3.1
  • a4ae420 Merge branch '2.22' into 2.x
  • 55d3e60 Post-release dep version bump
  • Additional commits viewable in compare view

Updates com.codeheadsystems:pk-auth-core from 2.3.0 to 2.3.1

Release notes

Sourced from com.codeheadsystems:pk-auth-core's releases.

Release 2.3.1

pk-auth 2.3.1

Maven Central

Add the modules you need (all share the same version):

implementation("com.codeheadsystems:pk-auth-spring-boot-starter:2.3.1")
// or :pk-auth-dropwizard / :pk-auth-micronaut for the other adapters
implementation("com.codeheadsystems:pk-auth-persistence-jdbi:2.3.1")
// testImplementation("com.codeheadsystems:pk-auth-testkit:2.3.1")
<dependency>
  <groupId>com.codeheadsystems</groupId>
  <artifactId>pk-auth-spring-boot-starter</artifactId>
  <version>2.3.1</version>
</dependency>

Modules Published

  • com.codeheadsystems:pk-auth-core:2.3.1
  • com.codeheadsystems:pk-auth-jwt:2.3.1
  • com.codeheadsystems:pk-auth-admin-api:2.3.1
  • com.codeheadsystems:pk-auth-backup-codes:2.3.1
  • com.codeheadsystems:pk-auth-magic-link:2.3.1
  • com.codeheadsystems:pk-auth-otp:2.3.1
  • com.codeheadsystems:pk-auth-persistence-jdbi:2.3.1
  • com.codeheadsystems:pk-auth-persistence-dynamodb:2.3.1
  • com.codeheadsystems:pk-auth-testkit:2.3.1
  • com.codeheadsystems:pk-auth-spring-boot-starter:2.3.1
  • com.codeheadsystems:pk-auth-dropwizard:2.3.1
  • com.codeheadsystems:pk-auth-micronaut:2.3.1

What's Changed

See commits since last release for details.

Note: Artifacts may take up to 2 hours to appear in Maven Central after release.

What's Changed

... (truncated)

Changelog

Sourced from com.codeheadsystems:pk-auth-core's changelog.

[2.3.1] - 2026-10-16

A patch release. It fixes a JDBI upgrade failure introduced in 2.3.0 for hosts that supply their own users table. Hosts using the documented classpath:db/migration location need no change; the upgrade note below covers the other configurations.

Fixed

  • JDBI hosts with their own identity model can apply pk-auth's migrations without the example users table. Up to 2.3.0 every migration lived flat in db/migration, so a host that excluded the example V5__example_users.sql failed on 2.3.0's V12__users_username_case_insensitive.sql with relation "users" does not exist. The migrations are now split into two classpath locations sharing one version sequence: db/migration/core (the tables pk-auth owns, always required) and db/migration/example-users (V5 and V12, needed only with JdbiUserLookup). Every script keeps its file name and its bytes, so Flyway checksums are unchanged, and V12 itself is not modified. PkAuthJdbiSchema gains CORE_MIGRATION_LOCATION, EXAMPLE_USERS_MIGRATION_LOCATION, MIGRATION_LOCATION, CORE_SCHEMA_VERSION (11), and migrateCoreForDevelopment(DataSource). See ADR 0021 and the operator guide.

    Upgrade note, by host configuration:

    • Flyway location classpath:db/migration, with JdbiUserLookup or the example table: no change. Flyway scans the location recursively and resolves the same twelve migrations with the same checksums, so an existing database validates and nothing new runs.
    • Own identity model, new database (or one that never applied V5): list classpath:db/migration/core and target PkAuthJdbiSchema.CORE_SCHEMA_VERSION. Flyway refuses a target that no configured location resolves, so CURRENT_SCHEMA_VERSION (12) fails against the core location alone.
    • Own identity model, scripts copied out of the jar by pattern with V5 excluded: change the pattern from db/migration/V*.sql to db/migration/core/V*.sql and drop the V5 exclusion. Neither V5 nor V12 needs excluding any more. The old pattern matches nothing in 2.3.1, and Flyway validation then fails on the applied migrations it can no longer resolve. A database left by the failed 2.3.0 upgrade sits at V11 (Postgres rolled the failed V12 back) and validates against the core set without further action.
    • Spring Boot with the default spring.flyway.locations (classpath:db/migration): unchanged, and the default still applies both sets from the jar. A new host that wants only the core set sets the property explicitly to its own location plus classpath:db/migration/core.
    • A database that applied V5 and V12 must keep the example location configured. Dropping it fails Flyway validation, because the applied example migrations no longer resolve.

... (truncated)

Commits
  • 795465e chore(release): prepare 2.3.1
  • c8a842b fix(jdbi): split example users migrations from core migrations
  • 60ab012 chore: retarget development line to 2.3.1 patch
  • 1895a69 build(deps): Bump the gh-actions group with 2 updates (#185)
  • 5daaf47 build(deps): Bump the dev-dependencies group with 16 updates (#184)
  • eff14ba build(deps-dev): Bump the npm-dependencies group across 4 directories with 3 ...
  • ad6c800 build: bump google-java-format to 1.36.1 for JDK 25 support
  • 51d1098 properties update
  • See full diff in compare view

Updates com.codeheadsystems:pk-auth-jwt from 2.3.0 to 2.3.1

Release notes

Sourced from com.codeheadsystems:pk-auth-jwt's releases.

Release 2.3.1

pk-auth 2.3.1

Maven Central

Add the modules you need (all share the same version):

implementation("com.codeheadsystems:pk-auth-spring-boot-starter:2.3.1")
// or :pk-auth-dropwizard / :pk-auth-micronaut for the other adapters
implementation("com.codeheadsystems:pk-auth-persistence-jdbi:2.3.1")
// testImplementation("com.codeheadsystems:pk-auth-testkit:2.3.1")
<dependency>
  <groupId>com.codeheadsystems</groupId>
  <artifactId>pk-auth-spring-boot-starter</artifactId>
  <version>2.3.1</version>
</dependency>

Modules Published

  • com.codeheadsystems:pk-auth-core:2.3.1
  • com.codeheadsystems:pk-auth-jwt:2.3.1
  • com.codeheadsystems:pk-auth-admin-api:2.3.1
  • com.codeheadsystems:pk-auth-backup-codes:2.3.1
  • com.codeheadsystems:pk-auth-magic-link:2.3.1
  • com.codeheadsystems:pk-auth-otp:2.3.1
  • com.codeheadsystems:pk-auth-persistence-jdbi:2.3.1
  • com.codeheadsystems:pk-auth-persistence-dynamodb:2.3.1
  • com.codeheadsystems:pk-auth-testkit:2.3.1
  • com.codeheadsystems:pk-auth-spring-boot-starter:2.3.1
  • com.codeheadsystems:pk-auth-dropwizard:2.3.1
  • com.codeheadsystems:pk-auth-micronaut:2.3.1

What's Changed

See commits since last release for details.

Note: Artifacts may take up to 2 hours to appear in Maven Central after release.

What's Changed

... (truncated)

Changelog

Sourced from com.codeheadsystems:pk-auth-jwt's changelog.

[2.3.1] - 2026-10-16

A patch release. It fixes a JDBI upgrade failure introduced in 2.3.0 for hosts that supply their own users table. Hosts using the documented classpath:db/migration location need no change; the upgrade note below covers the other configurations.

Fixed

  • JDBI hosts with their own identity model can apply pk-auth's migrations without the example users table. Up to 2.3.0 every migration lived flat in db/migration, so a host that excluded the example V5__example_users.sql failed on 2.3.0's V12__users_username_case_insensitive.sql with relation "users" does not exist. The migrations are now split into two classpath locations sharing one version sequence: db/migration/core (the tables pk-auth owns, always required) and db/migration/example-users (V5 and V12, needed only with JdbiUserLookup). Every script keeps its file name and its bytes, so Flyway checksums are unchanged, and V12 itself is not modified. PkAuthJdbiSchema gains CORE_MIGRATION_LOCATION, EXAMPLE_USERS_MIGRATION_LOCATION, MIGRATION_LOCATION, CORE_SCHEMA_VERSION (11), and migrateCoreForDevelopment(DataSource). See ADR 0021 and the operator guide.

    Upgrade note, by host configuration:

    • Flyway location classpath:db/migration, with JdbiUserLookup or the example table: no change. Flyway scans the location recursively and resolves the same twelve migrations with the same checksums, so an existing database validates and nothing new runs.
    • Own identity model, new database (or one that never applied V5): list classpath:db/migration/core and target PkAuthJdbiSchema.CORE_SCHEMA_VERSION. Flyway refuses a target that no configured location resolves, so CURRENT_SCHEMA_VERSION (12) fails against the core location alone.
    • Own identity model, scripts copied out of the jar by pattern with V5 excluded: change the pattern from db/migration/V*.sql to db/migration/core/V*.sql and drop the V5 exclusion. Neither V5 nor V12 needs excluding any more. The old pattern matches nothing in 2.3.1, and Flyway validation then fails on the applied migrations it can no longer resolve. A database left by the failed 2.3.0 upgrade sits at V11 (Postgres rolled the failed V12 back) and validates against the core set without further action.
    • Spring Boot with the default spring.flyway.locations (classpath:db/migration): unchanged, and the default still applies both sets from the jar. A new host that wants only the core set sets the property explicitly to its own location plus classpath:db/migration/core.
    • A database that applied V5 and V12 must keep the example location configured. Dropping it fails Flyway validation, because the applied example migrations no longer resolve.

... (truncated)

Commits
  • 795465e chore(release): prepare 2.3.1
  • c8a842b fix(jdbi): split example users migrations from core migrations
  • 60ab012 chore: retarget development line to 2.3.1 patch
  • 1895a69 build(deps): Bump the gh-actions group with 2 updates (#185)
  • 5daaf47 build(deps): Bump the dev-dependencies group with 16 updates (#184)
  • eff14ba build(deps-dev): Bump the npm-dependencies group across 4 directories with 3 ...
  • ad6c800 build: bump google-java-format to 1.36.1 for JDK 25 support
  • 51d1098 properties update
  • See full diff in compare view

Updates com.codeheadsystems:pk-auth-magic-link from 2.3.0 to 2.3.1

Release notes

Sourced from com.codeheadsystems:pk-auth-magic-link's releases.

Release 2.3.1

pk-auth 2.3.1

Maven Central

Add the modules you need (all share the same version):

implementation("com.codeheadsystems:pk-auth-spring-boot-starter:2.3.1")
// or :pk-auth-dropwizard / :pk-auth-micronaut for the other adapters
implementation("com.codeheadsystems:pk-auth-persistence-jdbi:2.3.1")
// testImplementation("com.codeheadsystems:pk-auth-testkit:2.3.1")
<dependency>
  <groupId>com.codeheadsystems</groupId>
  <artifactId>pk-auth-spring-boot-starter</artifactId>
  <version>2.3.1</version>
</dependency>

Modules Published

  • com.codeheadsystems:pk-auth-core:2.3.1
  • com.codeheadsystems:pk-auth-jwt:2.3.1
  • com.codeheadsystems:pk-auth-admin-api:2.3.1
  • com.codeheadsystems:pk-auth-backup-codes:2.3.1
  • com.codeheadsystems:pk-auth-magic-link:2.3.1
  • com.codeheadsystems:pk-auth-otp:2.3.1
  • com.codeheadsystems:pk-auth-persistence-jdbi:2.3.1
  • com.codeheadsystems:pk-auth-persistence-dynamodb:2.3.1
  • com.codeheadsystems:pk-auth-testkit:2.3.1
  • com.codeheadsystems:pk-auth-spring-boot-starter:2.3.1
  • com.codeheadsystems:pk-auth-dropwizard:2.3.1
  • com.codeheadsystems:pk-auth-micronaut:2.3.1

What's Changed

See commits since last release for details.

Note: Artifacts may take up to 2 hours to appear in Maven Central after release.

What's Changed

... (truncated)

Changelog

Sourced from com.codeheadsystems:pk-auth-magic-link's changelog.

[2.3.1] - 2026-10-16

A patch release. It fixes a JDBI upgrade failure introduced in 2.3.0 for hosts that supply their own users table. Hosts using the documented classpath:db/migration location need no change; the upgrade note below covers the other configurations.

Fixed

  • JDBI hosts with their own identity model can apply pk-auth's migrations without the example users table. Up to 2.3.0 every migration lived flat in db/migration, so a host that excluded the example V5__example_users.sql failed on 2.3.0's V12__users_username_case_insensitive.sql with relation "users" does not exist. The migrations are now split into two classpath locations sharing one version sequence: db/migration/core (the tables pk-auth owns, always required) and db/migration/example-users (V5 and V12, needed only with JdbiUserLookup). Every script keeps its file name and its bytes, so Flyway checksums are unchanged, and V12 itself is not modified. PkAuthJdbiSchema gains CORE_MIGRATION_LOCATION, EXAMPLE_USERS_MIGRATION_LOCATION, MIGRATION_LOCATION, CORE_SCHEMA_VERSION (11), and migrateCoreForDevelopment(DataSource). See ADR 0021 and the operator guide.

    Upgrade note, by host configuration:

    • Flyway location classpath:db/migration, with JdbiUserLookup or the example table: no change. Flyway scans the location recursively and resolves the same twelve migrations with the same checksums, so an existing database validates and nothing new runs.
    • Own identity model, new database (or one that never applied V5): list classpath:db/migration/core and target PkAuthJdbiSchema.CORE_SCHEMA_VERSION. Flyway refuses a target that no configured location resolves, so CURRENT_SCHEMA_VERSION (12) fails against the core location alone.
    • Own identity model, scripts copied out of the jar by pattern with V5 excluded: change the pattern from db/migration/V*.sql to db/migration/core/V*.sql and drop the V5 exclusion. Neither V5 nor V12 needs excluding any more. The old pattern matches nothing in 2.3.1, and Flyway validation then fails on the applied migrations it can no longer resolve. A database left by the failed 2.3.0 upgrade sits at V11 (Postgres rolled the failed V12 back) and validates against the core set without further action.
    • Spring Boot with the default spring.flyway.locations (classpath:db/migration): unchanged, and the default still applies both sets from the jar. A new host that wants only the core set sets the property explicitly to its own location plus classpath:db/migration/core.
    • A database that applied V5 and V12 must keep the example location configured. Dropping it fails Flyway validation, because the applied example migrations no longer resolve.

... (truncated)

Commits
  • 795465e chore(release): prepare 2.3.1
  • c8a842b fix(jdbi): split example users migrations from core migrations
  • 60ab012 chore: retarget development line to 2.3.1 patch
  • 1895a69 build(deps): Bump the gh-actions group with 2 updates (#185)
  • 5daaf47 build(deps): Bump the dev-dependencies group with 16 updates (#184)
  • eff14ba build(deps-dev): Bump the npm-dependencies group across 4 directories with 3 ...
  • ad6c800 build: bump google-java-format to 1.36.1 for JDK 25 support
  • 51d1098 properties update
  • See full diff in compare view

Updates com.codeheadsystems:pk-auth-otp from 2.3.0 to 2.3.1

Release notes

Sourced from com.codeheadsystems:pk-auth-otp's releases.

Release 2.3.1

pk-auth 2.3.1

Maven Central

Add the modules you need (all share the same version):

implementation("com.codeheadsystems:pk-auth-spring-boot-starter:2.3.1")
// or :pk-auth-dropwizard / :pk-auth-micronaut for the other adapters
implementation("com.codeheadsystems:pk-auth-persistence-jdbi:2.3.1")
// testImplementation("com.codeheadsystems:pk-auth-testkit:2.3.1")
<dependency>
  <groupId>com.codeheadsystems</groupId>
  <artifactId>pk-auth-spring-boot-starter</artifactId>
  <version>2.3.1</version>
</dependency>

Modules Published

  • com.codeheadsystems:pk-auth-core:2.3.1
  • com.codeheadsystems:pk-auth-jwt:2.3.1
  • com.codeheadsystems:pk-auth-admin-api:2.3.1
  • com.codeheadsystems:pk-auth-backup-codes:2.3.1
  • com.codeheadsystems:pk-auth-magic-link:2.3.1
  • com.codeheadsystems:pk-auth-otp:2.3.1
  • com.codeheadsystems:pk-auth-persistence-jdbi:2.3.1
  • com.codeheadsystems:pk-auth-persistence-dynamodb:2.3.1
  • com.codeheadsystems:pk-auth-testkit:2.3.1
  • com.codeheadsystems:pk-auth-spring-boot-starter:2.3.1
  • com.codeheadsystems:pk-auth-dropwizard:2.3.1
  • com.codeheadsystems:pk-auth-micronaut:2.3.1

What's Changed

See commits since last release for details.

Note: Artifacts may take up to 2 hours to appear in Maven Central after release.

What's Changed

... (truncated)

Changelog

Sourced from com.codeheadsystems:pk-auth-otp's changelog.

[2.3.1] - 2026-10-16

A patch release. It fixes a JDBI upgrade failure introduced in 2.3.0 for hosts that supply their own users table. Hosts using the documented classpath:db/migration location need no change; the upgrade note below covers the other configurations.

Fixed

  • JDBI hosts with their own identity model can apply pk-auth's migrations without the example users table. Up to 2.3.0 every migration lived flat in db/migration, so a host that excluded the example V5__example_users.sql failed on 2.3.0's V12__users_username_case_insensitive.sql with relation "users" does not exist. The migrations are now split into two classpath locations sharing one version sequence: db/migration/core (the tables pk-auth owns, always required) and db/migration/example-users (V5 and V12, needed only with JdbiUserLookup). Every script keeps its file name and its bytes, so Flyway checksums are unchanged, and V12 itself is not modified. PkAuthJdbiSchema gains CORE_MIGRATION_LOCATION, EXAMPLE_USERS_MIGRATION_LOCATION, MIGRATION_LOCATION, CORE_SCHEMA_VERSION (11), and migrateCoreForDevelopment(DataSource). See ADR 0021 and the operator guide.

    Upgrade note, by host configuration:

    • Flyway location classpath:db/migration, with JdbiUserLookup or the example table: no change. Flyway scans the location recursively and resolves the same twelve migrations with the same checksums, so an existing database validates and nothing new runs.
    • Own identity model, new database (or one that never applied V5): list classpath:db/migration/core and target PkAuthJdbiSchema.CORE_SCHEMA_VERSION. Flyway refuses a target that no configured location resolves, so CURRENT_SCHEMA_VERSION (12) fails against the core location alone.
    • Own identity model, scripts copied out of the jar by pattern with V5 excluded: change the pattern from db/migration/V*.sql to db/migration/core/V*.sql and drop the V5 exclusion. Neither V5 nor V12 needs excluding any more. The old pattern matches nothing in 2.3.1, and Flyway validation then fails on the applied migrations it can no longer resolve. A database left by the failed 2.3.0 upgrade sits at V11 (Postgres rolled the failed V12 back) and validates against the core set without further action.
    • Spring Boot with the default spring.flyway.locations (classpath:db/migration): unchanged, and the default still applies both sets from the jar. A new host that wants only the core set sets the property explicitly to its own location plus classpath:db/migration/core.
    • A database that applied V5 and V12 must keep the example location configured. Dropping it fails Flyway validation, because the applied example migrations no longer resolve.

... (truncated)

Commits
  • 795465e chore(release): prepare 2.3.1
  • c8a842b fix(jdbi): split example users migrations from core migrations
  • 60ab012 chore: retarget development line to 2.3.1 patch
  • 1895a69 build(deps): Bump the gh-actions group with 2 updates (#185)
  • 5daaf47 build(deps): Bump the dev-dependencies group with 16 updates (#184)
  • eff14ba build(deps-dev): Bump the npm-dependencies group across 4 directories with 3 ...
  • ad6c800 build: bump google-java-format to 1.36.1 for JDK 25 support
  • 51d1098 properties update
  • See full diff in compare view

Updates com.codeheadsystems:pk-auth-backup-codes from 2.3.0 to 2.3.1

Release notes

Sourced from com.codeheadsystems:pk-auth-backup-codes's releases.

Release 2.3.1

pk-auth 2.3.1

Maven Central

Add the modules you need (all share the same version):

implementation("com.codeheadsystems:pk-auth-spring-boot-starter:2.3.1")
// or :pk-auth-dropwizard / :pk-auth-micronaut for the other adapters
implementation("com.codeheadsystems:pk-auth-persistence-jdbi:2.3.1")
// testImplementation("com.codeheadsystems:pk-auth-testkit:2.3.1")
<dependency>
  <groupId>com.codeheadsystems</groupId>
  <artifactId>pk-auth-spring-boot-starter</artifactId>
  <version>2.3.1</version>
</dependency>

Modules Published

  • com.codeheadsystems:pk-auth-core:2.3.1
  • com.codeheadsystems:pk-auth-jwt:2.3.1
  • com.codeheadsystems:pk-auth-admin-api:2.3.1
  • com.codeheadsystems:pk-auth-backup-codes:2.3.1
  • com.codeheadsystems:pk-auth-magic-link:2.3.1
  • com.codeheadsystems:pk-auth-otp:2.3.1
  • com.codeheadsystems:pk-auth-persistence-jdbi:2.3.1
  • com.codeheadsystems:pk-auth-persistence-dynamodb:2.3.1
  • com.codeheadsystems:pk-auth-testkit:2.3.1
  • com.codeheadsystems:pk-auth-spring-boot-starter:2.3.1
  • com.codeheadsystems:pk-auth-dropwizard:2.3.1
  • com.codeheadsystems:pk-auth-micronaut:2.3.1

What's Changed

See commits since last release for details.

Note: Artifacts may take up to 2 hours to appear in Maven Central after release.

What's Changed

... (truncated)

Changelog

Sourced from com.codeheadsystems:pk-auth-backup-codes's changelog.

[2.3.1] - 2026-10-16

A patch release. It fixes a JDBI upgrade failure introduced in 2.3.0 for hosts that supply their own users table. Hosts using the documented classpath:db/migration location need no change; the upgrade note below covers the other configurations.

Fixed

  • JDBI hosts with their own identity model can apply pk-auth's migrations without the example users table. Up to 2.3.0 every migration lived flat in db/migration, so a host that excluded the example V5__example_users.sql failed on 2.3.0's V12__users_username_case_insensitive.sql with relation "users" does not exist. The migrations are now split into two classpath locations sharing one version sequence: db/migration/core (the tables pk-auth owns, always required) and db/migration/example-users (V5 and V12, needed only with JdbiUserLookup). Every script keeps its file name and its bytes, so Flyway checksums are unchanged, and V12 itself is not modified. PkAuthJdbiSchema gains CORE_MIGRATION_LOCATION, EXAMPLE_USERS_MIGRATION_LOCATION, MIGRATION_LOCATION, CORE_SCHEMA_VERSION (11), and migrateCoreForDevelopment(DataSource). See ADR 0021 and the operator guide.

    Upgrade note, by host configuration:

    • Flyway location classpath:db/migration, with JdbiUserLookup or the example table: no change. Flyway scans the location recursively and resolves the same twelve migrations with the same checksums, so an existing database validates and nothing new runs.
    • Own identity model, new database (or one that never applied V5): list classpath:db/migration/core and target PkAuthJdbiSchema.CORE_SCHEMA_VERSION. Flyway refuses a target that no configured location resolves, so CURRENT_SCHEMA_VERSION (12) fails against the core location alone.
    • Own identity model, scripts copied out of the jar by pattern with V5 excluded: change the pattern from db/migration/V*.sql to db/migration/core/V*.sql and drop the V5 exclusion. Neither V5 nor V12 needs excluding any more. The old pattern matches nothing in 2.3.1, and Flyway validation then fails on the applied migrations it can no longer resolve. A database left by the failed 2.3.0 upgrade sits at V11 (Postgres rolled the failed V12 back) and validates against the core set without further action.
    • Spring Boot with the default spring.flyway.locations (classpath:db/migration): unchanged, and the default still applies both sets from the jar. A new host that wants only the core set sets the property explicitly to its own location plus classpath:db/migration/core.
    • A database that applied V5 and V12 must keep the example location configured. Dropping it fails Flyway validation, because the applied example migrations no longer resolve.

... (truncated)

Commits
  • 795465e chore(release): prepare 2.3.1
  • c8a842b fix(jdbi): split example users migrations from core migrations
  • 60ab012 chore: retarget development line to 2.3.1 patch
  • 1895a69 build(deps): Bump the gh-actions group with 2 updates (#185)
  • 5daaf47 build(deps): Bump the dev-dependencies group with 16 updates (#184)
  • eff14ba build(deps-dev): Bump the npm-dependencies group across 4 directories with 3 ...
  • ad6c800 build: bump google-java-format to 1.36.1 for JDK 25 support
  • 51d1098 properties update
  • See full diff in compare view

Updates com.codeheadsystems:pk-auth-testkit from 2.3.0 to 2.3.1

Release notes

Sourced from com.codeheadsystems:pk-auth-testkit's releases.

Release 2.3.1

pk-auth 2.3.1

Maven Central

Add the modules you need (all share the same version):

implementation("com.codeheadsystems:pk-auth-spring-boot-starter:2.3.1")
// or :pk-auth-dropwizard / :pk-auth-micronaut for the other adapters
implementation("com.codeheadsystems:pk-auth-persistence-jdbi:2.3.1")
// testImplementation("com.codeheadsystems:pk-auth-testkit:2.3.1")
<dependency>
  <groupId>com.codeheadsystems</groupId>
  <artifactId>pk-auth-spring-boot-starter</artifactId>
  <version>2.3.1</version>
</dependency>

Modules Published

  • com.codeheadsystems:pk-auth-core:2.3.1
  • com.codeheadsystems:pk-auth-jwt:2.3.1
  • com.codeheadsystems:pk-auth-admin-api:2.3.1
  • com.codeheadsystems:pk-auth-backup-codes:2.3.1
  • com.codeheadsystems:pk-auth-magic-link:2.3.1
  • com.codeheadsystems:pk-auth-otp:2.3.1
  • com.codeheadsystems:pk-auth-persistence-jdbi:2.3.1
  • com.codeheadsystems:pk-auth-persistence-dynamodb:2.3.1
  • com.codeheadsystems:pk-auth-testkit:2.3.1
  • com.codeheadsystems:pk-auth-spring-boot-starter:2.3.1
  • com.codeheadsystems:pk-auth-dropwizard:2.3.1
  • com.codeheadsystems:pk-auth-micronaut:2.3.1

What's Changed

See commits since last release for details.

Note: Artifacts may take up to 2 hours to appear in Maven Central after release.

What's Changed

... (truncated)

Changelog

Sourced from com.codeheadsystems:pk-auth-testkit's changelog.

[2.3.1] - 2026-10-16

A patch release. It fixes a JDBI upgrade failure introduced in 2.3.0 for hosts that supply their own users table. Hosts using the documented classpath:db/migration location need no change; the upgrade note below covers the other configurations.

Fixed

  • JDBI hosts with their own identity model can apply pk-auth's migrations without the example users table. Up to 2.3.0 every migration lived flat in db/migration, so a host that excluded the example V5__example_users.sql failed on 2.3.0's V12__users_username_case_insensitive.sql with relation "users" does not exist. The migrations are now split into two classpath locations sharing one version sequence: db/migration/core (the tables pk-auth owns, always required) and db/migration/example-users (V5 and V12, needed only with JdbiUserLookup). Every script keeps its file name and its bytes, so Flyway checksums are unchanged, and V12 itself is not modified. PkAuthJdbiSchema gains CORE_MIGRATION_LOCATION, EXAMPLE_USERS_MIGRATION_LOCATION, MIGRATION_LOCATION, CORE_SCHEMA_VERSION (11), and migrateCoreForDevelopment(DataSource). See ADR 0021 and the operator guide.

    Upgrade note, by host configuration:

    • Flyway location classpath:db/migration, with JdbiUserLookup or the example table: no change. Flyway scans the location recursively and resolves the same twelve migrations with the same checksums, so an existing database validates and nothing new runs.
    • Own identity model, new database (or one that never applied V5): list classpath:db/migration/core and target PkAuthJdbiSchema.CORE_SCHEMA_VERSION. Flyway refuses a target that no configured location resolves, so CURRENT_SCHEMA_VERSION (12) fails against the core location alone.
    • Own identity model, scripts copied out of the jar by pattern with V5 excluded: change the pattern from db/migration/V*.sql to db/migration/core/V*.sql and drop the V5 exclusion. Neither V5 nor V12 needs excluding any more. The old pattern matches nothing in 2.3.1, and Flyway validation then fails on the applied migrations it can no longer resolve. A database left by the failed 2.3.0 upgrade sits at V11 (Postgres rolled the failed V12 back) and validates against the core set without further action.
    • Spring Boot with the default spring.flyway.locations (classpath:db/migration): unchanged, and the default still applies both sets from the jar. A new host that wants only the core set sets the property explicitly to its own location plus classpath:db/migration/core.
    • A database that applied V5 and V12 must keep the example location configured. Dropping it fails Flyway validation, because the applied example migrations no longer resolve.

... (truncated)

Commits
  • 795465e chore(release): prepare 2.3.1
  • c8a842b fix(jdbi): split example users migrations from core migrations
  • 60ab012 chore: retarget development line to 2.3.1 patch
  • 1895a69 build(deps): Bump the gh-actions group with 2 updates (#185)
  • 5daaf47 build(deps): Bump the dev-dependencies group with 16 updates (#184)
  • eff14ba build(deps-dev): Bump the npm-dependencies group across 4 directories with 3 ...
  • ad6c800 build: bump google-java-format to 1.36.1 for JDK 25 support
  • 51d1098 properties update
  • See full diff in compare view

Updates com.codeheadsystems:pk-auth-jwt from 2.3.0 to 2.3.1

Release notes

Sourced from com.codeheadsystems:pk-auth-jwt's releases.

Release 2.3.1

pk-auth 2.3.1

Maven Central

Add the modules you need (all share the same version):

implementation("com.codeheadsystems:pk-auth-spring-boot-starter:2.3.1")
// or :pk-auth-dropwizard / :pk-auth-micronaut for the other adapters
implementation("com.codeheadsystems:pk-auth-persistence-jdbi:2.3.1")
// testImplementation("com.codeheadsystems:pk-auth-testkit:2.3.1")
<dependency>
  <groupId>com.codeheadsystems</groupId>
  <artifactId>pk-auth-spring-boot-starter</artifactId>
  <version>2.3.1</version>
</dependency>

Modules Published

  • com.codeheadsystems:pk-auth-core:2.3.1
  • com.codeheadsystems:pk-auth-jwt:2.3.1
  • com.codeheadsystems:pk-auth-admin-api:2.3.1
  • com.codeheadsystems:pk-auth-backup-codes:2.3.1
  • com.codeheadsystems:pk-auth-magic-link:2.3.1
  • com.codeheadsystems:pk-auth-otp:2.3.1
  • com.codeheadsystems:pk-auth-persistence-jdbi:2.3.1
  • Description has been truncated

@dependabot
build: bump the gradle-minor-and-patch group with 8 updates
40da0c5 
Bumps the gradle-minor-and-patch group with 8 updates:

| Package | From | To |
| --- | --- | --- |
| [tools.jackson.core:jackson-databind](https://github.com/FasterXML/jackson-databind) | `3.2.3` | `3.2.4` |
| [tools.jackson.dataformat:jackson-dataformat-yaml](https://github.com/FasterXML/jackson-dataformats-text) | `3.2.3` | `3.2.4` |
| [com.codeheadsystems:pk-auth-core](https://github.com/codeheadsystems/pk-auth) | `2.3.0` | `2.3.1` |
| [com.codeheadsystems:pk-auth-jwt](https://github.com/codeheadsystems/pk-auth) | `2.3.0` | `2.3.1` |
| [com.codeheadsystems:pk-auth-magic-link](https://github.com/codeheadsystems/pk-auth) | `2.3.0` | `2.3.1` |
| [com.codeheadsystems:pk-auth-otp](https://github.com/codeheadsystems/pk-auth) | `2.3.0` | `2.3.1` |
| [com.codeheadsystems:pk-auth-backup-codes](https://github.com/codeheadsystems/pk-auth) | `2.3.0` | `2.3.1` |
| [com.codeheadsystems:pk-auth-testkit](https://github.com/codeheadsystems/pk-auth) | `2.3.0` | `2.3.1` |


Updates `tools.jackson.core:jackson-databind` from 3.2.3 to 3.2.4
- [Commits](FasterXML/jackson-databind@jackson-databind-3.2.3...jackson-databind-3.2.4)

Updates `tools.jackson.dataformat:jackson-dataformat-yaml` from 3.2.3 to 3.2.4
- [Commits](FasterXML/jackson-dataformats-text@jackson-dataformats-text-3.2.3...jackson-dataformats-text-3.2.4)

Updates `tools.jackson.dataformat:jackson-dataformat-yaml` from 3.2.3 to 3.2.4
- [Commits](FasterXML/jackson-dataformats-text@jackson-dataformats-text-3.2.3...jackson-dataformats-text-3.2.4)

Updates `com.codeheadsystems:pk-auth-core` from 2.3.0 to 2.3.1
- [Release notes](https://github.com/codeheadsystems/pk-auth/releases)
- [Changelog](https://github.com/codeheadsystems/pk-auth/blob/main/CHANGELOG.md)
- [Commits](codeheadsystems/pk-auth@v2.3.0...v2.3.1)

Updates `com.codeheadsystems:pk-auth-jwt` from 2.3.0 to 2.3.1
- [Release notes](https://github.com/codeheadsystems/pk-auth/releases)
- [Changelog](https://github.com/codeheadsystems/pk-auth/blob/main/CHANGELOG.md)
- [Commits](codeheadsystems/pk-auth@v2.3.0...v2.3.1)

Updates `com.codeheadsystems:pk-auth-magic-link` from 2.3.0 to 2.3.1
- [Release notes](https://github.com/codeheadsystems/pk-auth/releases)
- [Changelog](https://github.com/codeheadsystems/pk-auth/blob/main/CHANGELOG.md)
- [Commits](codeheadsystems/pk-auth@v2.3.0...v2.3.1)

Updates `com.codeheadsystems:pk-auth-otp` from 2.3.0 to 2.3.1
- [Release notes](https://github.com/codeheadsystems/pk-auth/releases)
- [Changelog](https://github.com/codeheadsystems/pk-auth/blob/main/CHANGELOG.md)
- [Commits](codeheadsystems/pk-auth@v2.3.0...v2.3.1)

Updates `com.codeheadsystems:pk-auth-backup-codes` from 2.3.0 to 2.3.1
- [Release notes](https://github.com/codeheadsystems/pk-auth/releases)
- [Changelog](https://github.com/codeheadsystems/pk-auth/blob/main/CHANGELOG.md)
- [Commits](codeheadsystems/pk-auth@v2.3.0...v2.3.1)

Updates `com.codeheadsystems:pk-auth-testkit` from 2.3.0 to 2.3.1
- [Release notes](https://github.com/codeheadsystems/pk-auth/releases)
- [Changelog](https://github.com/codeheadsystems/pk-auth/blob/main/CHANGELOG.md)
- [Commits](codeheadsystems/pk-auth@v2.3.0...v2.3.1)

Updates `com.codeheadsystems:pk-auth-jwt` from 2.3.0 to 2.3.1
- [Release notes](https://github.com/codeheadsystems/pk-auth/releases)
- [Changelog](https://github.com/codeheadsystems/pk-auth/blob/main/CHANGELOG.md)
- [Commits](codeheadsystems/pk-auth@v2.3.0...v2.3.1)

Updates `com.codeheadsystems:pk-auth-magic-link` from 2.3.0 to 2.3.1
- [Release notes](https://github.com/codeheadsystems/pk-auth/releases)
- [Changelog](https://github.com/codeheadsystems/pk-auth/blob/main/CHANGELOG.md)
- [Commits](codeheadsystems/pk-auth@v2.3.0...v2.3.1)

Updates `com.codeheadsystems:pk-auth-otp` from 2.3.0 to 2.3.1
- [Release notes](https://github.com/codeheadsystems/pk-auth/releases)
- [Changelog](https://github.com/codeheadsystems/pk-auth/blob/main/CHANGELOG.md)
- [Commits](codeheadsystems/pk-auth@v2.3.0...v2.3.1)

Updates `com.codeheadsystems:pk-auth-backup-codes` from 2.3.0 to 2.3.1
- [Release notes](https://github.com/codeheadsystems/pk-auth/releases)
- [Changelog](https://github.com/codeheadsystems/pk-auth/blob/main/CHANGELOG.md)
- [Commits](codeheadsystems/pk-auth@v2.3.0...v2.3.1)

Updates `com.codeheadsystems:pk-auth-testkit` from 2.3.0 to 2.3.1
- [Release notes](https://github.com/codeheadsystems/pk-auth/releases)
- [Changelog](https://github.com/codeheadsystems/pk-auth/blob/main/CHANGELOG.md)
- [Commits](codeheadsystems/pk-auth@v2.3.0...v2.3.1)

---
updated-dependencies:
- dependency-name: tools.jackson.core:jackson-databind
  dependency-version: 3.2.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gradle-minor-and-patch
- dependency-name: tools.jackson.dataformat:jackson-dataformat-yaml
  dependency-version: 3.2.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gradle-minor-and-patch
- dependency-name: tools.jackson.dataformat:jackson-dataformat-yaml
  dependency-version: 3.2.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gradle-minor-and-patch
- dependency-name: com.codeheadsystems:pk-auth-core
  dependency-version: 2.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gradle-minor-and-patch
- dependency-name: com.codeheadsystems:pk-auth-jwt
  dependency-version: 2.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gradle-minor-and-patch
- dependency-name: com.codeheadsystems:pk-auth-magic-link
  dependency-version: 2.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gradle-minor-and-patch
- dependency-name: com.codeheadsystems:pk-auth-otp
  dependency-version: 2.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gradle-minor-and-patch
- dependency-name: com.codeheadsystems:pk-auth-backup-codes
  dependency-version: 2.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gradle-minor-and-patch
- dependency-name: com.codeheadsystems:pk-auth-testkit
  dependency-version: 2.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gradle-minor-and-patch
- dependency-name: com.codeheadsystems:pk-auth-jwt
  dependency-version: 2.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gradle-minor-and-patch
- dependency-name: com.codeheadsystems:pk-auth-magic-link
  dependency-version: 2.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gradle-minor-and-patch
- dependency-name: com.codeheadsystems:pk-auth-otp
  dependency-version: 2.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gradle-minor-and-patch
- dependency-name: com.codeheadsystems:pk-auth-backup-codes
  dependency-version: 2.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gradle-minor-and-patch
- dependency-name: com.codeheadsystems:pk-auth-testkit
  dependency-version: 2.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gradle-minor-and-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Oct 22, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: dependencies, gradle. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@github-actions
github-actions Bot merged commit 694a418 into main Oct 22, 2026
3 checks passed
@github-actions
github-actions Bot deleted the dependabot/gradle/gradle-minor-and-patch-87c0d32cf5 branch October 22, 2026 11:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@github-actions github-actions[bot] github-actions[bot] approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants