chore(release): prepare 2.2.0#104
Merged
Merged
Conversation
- Bump version 2.1.0-SNAPSHOT -> 2.2.0-SNAPSHOT (the post-2.1.0 development line open was missed after v2.1.0 was tagged). - Correct @SInCE on the 11 public API elements introduced after v2.1.0 from 2.1.0 to 2.2.0 (the 9 genuine 2.1.0 markers in files unchanged since the tag are left as-is). - Add the 2.2.0 CHANGELOG entry: a security-and-correctness release (magic-link replay/audience/email-binding, per-request UV enforcement, JWT claim-override + OTP brute-force fixes, DynamoDB/JDBI correctness, Retry-After on ceremony 429s). Notes the one breaking SPI change (OtpRepository.findLatestActive gains an Instant now param) and Flyway V11. Tagging v2.2.0 triggers the publish workflow. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
wolpert
enabled auto-merge (rebase)
June 28, 2026 03:57
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
1 participant
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.
Release-prep for 2.2.0. No functional code changes —
@sincecorrections, version bump, and the changelog entry. The actual fixes already landed onmainafterv2.1.0; this PR makes the tree releasable.What's in this PR
2.1.0-SNAPSHOT→2.2.0-SNAPSHOT(the post-2.1.0 dev-line bump was missed whenv2.1.0was tagged).@sincehygiene: 11 public API elements introduced afterv2.1.0were annotated@since 2.1.0(now inaccurate, since 2.1.0 shipped) → corrected to@since 2.2.0. The 9 genuine 2.1.0 markers (in files unchanged since the tag) are untouched. Verified by per-file diff againstv2.1.0.## [2.2.0]entry.Why 2.2.0 (minor), not 2.1.1 (patch)
The unreleased delta since
v2.1.0is not purely backward-compatible:OtpRepository.findLatestActivegains a requiredInstant nowparameter — direct SPI implementers must update.challenges.user_verification).MagicLinkService.DEFAULT_AUDIENCE/ofDedicatedAudience,ChallengeRecordUV field,CeremonyResponse.headers()).Release contents (security-and-correctness)
Two adversarial-review rounds: magic-link replay / dedicated-audience / email-binding fixes, server-side per-request UV enforcement, JWT claim-override + OTP brute-force hardening, DynamoDB/JDBI correctness fixes, and
Retry-Afteron ceremony 429s. See the CHANGELOG entry for the full list.After merge
Tag
v2.2.0to trigger the publish workflow (it strips-SNAPSHOTat build time).🤖 Generated with Claude Code