0.2.1

Highlights

bluetape4k-javers 0.2.1 is a narrow patch release for the bluetape4k-dependencies 1.3.x train. It keeps the published 0.2.0 source boundary, fixes release-line metadata and dependency exposure, and avoids pulling unrelated development work into the patch.
Related: #216 #215 #220

Release-line fixes

• Updated javers-exposed release guidance to consume the release-train bluetape4k-exposed-bom through an implementation-scoped platform import instead of exporting that BOM through API scope.
• Restricted JaVers BOM constraints so downstream consumers receive the intended library constraints without leaking internal platform wiring.
• Corrected generated POM license metadata to match the bluetape4k MIT license policy.
• Updated the default bluetape4k dependencies catalog reference used by release workflows.
  Related: #216 #215 #205 #220

Validation and maintenance

• Covered the JaVers benchmark smoke path in the release-prep work.
• Reduced compileTestKotlin warning noise and aligned data-class validation factories.
• Recorded release-prep review evidence and clarified Exposed/JaVers DDD boundaries for maintainers.
  Related: #219 #206 #218 #214 #221

What did not change

• No new JaVers runtime feature is introduced by this patch release.
• Broader JaVers feature work remains outside the patch boundary and should be evaluated on the next development line.
  Related: #197 #186 #185 #175

Contributors

Thanks to everyone who contributed to this release.

• debop sunghyouk.bae@gmail.com

Full Changelog: 0.2.0...0.2.1