Repository navigation
chore(release): prepare 2.3.1 - #187
Merged
Merged
Conversation
- Date the 2.3.1 CHANGELOG entry (JDBI core / example-users migration split, ADR 0021) and open a fresh [Unreleased] section. - Record the dependency bumps shipped since v2.3.0 (Flyway 13.10.0, PostgreSQL JDBC 42.7.14, AWS SDK 2.55.14, Micronaut 4.10.31; build-side Gradle 9.8.1, Spotless 8.10.4, google-java-format 1.36.1). - Add the v2.3.0...v2.3.1 compare link. gradle.properties is already 2.3.1-SNAPSHOT and the @SInCE tags already read 2.3.1. Tagging v2.3.1 triggers the publish workflow. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
wolpert
enabled auto-merge (rebase)
October 16, 2026 14:38
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Release prep for the 2.3.1 patch.
[2.3.1] - 2026-10-16(JDBI core / example-users migration split from fix(jdbi): split example users migrations from core migrations #186, ADR 0021) and opens a fresh[Unreleased]section.v2.3.0...v2.3.1compare link.gradle.propertiesis already2.3.1-SNAPSHOTand the new@sincetags already read 2.3.1, so no other files change.Verification
./gradlew clean build test --stacktrace(the release workflow's gate): passes, 715 tests, 0 failures.-Pversion=2.3.1build ofpk-auth-persistence-jdbi: the jar and POM come out as2.3.1, with all 12 migrations underdb/migration/{core,example-users}.publishAggregationToCentralPortal, the task both release workflows call, is still registered.After merge
Tag
v2.3.1on main to triggerrelease.yml. Then publish@pk-auth/passkeys-browser2.3.1 by hand per RELEASE.md (no SDK code changes, but the SDK version tracks the server release).🤖 Generated with Claude Code