Repository navigation
chore: record 0.2.3 release and start 0.2.4 development - #37
Merged
Merged
Conversation
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.
Version 0.2.3 is now public on Maven Central and GitHub. Record the signed-tag provenance, dependency security scope, exact-commit Langfuse read-back, two-hour load measurements and public artifact verification in a permanent release audit.
Move the reactor and independent consumer/experiment projects to
0.2.4-SNAPSHOT, and use the published0.2.3as the API compatibility baseline. README installation snippets remain on the released version.Validation: all release gates and the exact-commit sustained-load run passed; all ten public artifact signatures and checksums were verified; the public core JAR matches the load-tested JAR; ten consumer tests passed using a new public-Central-only Maven cache. Public SBOM findings are zero HIGH/CRITICAL and one MEDIUM; the documented Boot 3 web-stack limitations remain.