docs: cut 0.3.0 changelog section#62
Merged
Merged
Conversation
Convert [Unreleased] to [0.3.0] (2026-06-08), condense entries to their essence while keeping BREAKING flags, PR refs, and the 0.2.x migration note. Add a fresh empty [Unreleased] and update compare links. VERSION_NAME is already 0.3.0, so the file now matches the artifact version.
Code review flagged user-facing changes merged since v0.2.0 that were never recorded in [Unreleased]: - Added: MessageDeliverer.deliverBatch (#35) - Fixed: HTTP exception classification (#44), kafka api deps (#47), Liquibase NCDF on SB 3.5.x (#42/#38), micrometer autoconfig ordering (#41), OutboxPurger partial-batch progress log (#55) Internal-only changes (benchmarks #34/#48, docs #56, chore #59, tests #61) remain intentionally excluded.
Three-reviewer team (completeness / technical truth / format) found no correctness errors, only precision fixes: - clock removal now cites #59 (actual ctor-param removal), #58 as the cause - add missing #50 ref to the Liquibase-consolidation bullet - drop 'infinite retry loop' (RetryPolicy maxRetries is finite) -> 'wasted the whole retry budget before being marked FAILED' - #42: don't name @AutoConfigureAfter (code uses @autoConfiguration afterName) Cosmetic-only notes (Added bold-lead, trailing-URL line length) left as-is: they match the existing 0.2.0/0.1.0 style.
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.
What
Converts the
[Unreleased]section ofCHANGELOG.mdinto a dated## [0.3.0] — 2026-06-08release section, condensed to the essentials.Why
VERSION_NAMEingradle.propertiesis already0.3.0, but the changelog still carried everything under[Unreleased]. This closes the section so the file matches the artifact version and is ready for thev0.3.0tag (which triggers the Maven Central publish + GitHub Release).Changes
[Unreleased]→## [0.3.0] — 2026-06-08; entries condensed (kept BREAKING flags, PR refs, and the Migration from 0.2.x note).[Unreleased].[0.3.0]: …compare/v0.2.0...v0.3.0,[Unreleased]: …compare/v0.3.0...HEAD.Net: +39 / −80 lines,
CHANGELOG.mdonly. No code changes.Note
This does not tag the release. After merge, cut
v0.3.0(git tag v0.3.0 && git push origin v0.3.0) to trigger publish.