0.2.6

implementation 'net.bitsar:coalesce-spring-boot-starter:0.2.6'

Published to Maven Central. Central deployment f6313f9f-90b8-494c-8a61-4dcfcfe17f5f, built by run 35305902138.

Verify what actually landed:

./gradlew -p consumer-check test -PcoalesceVersion=0.2.6

What changed

• Make the follower poll interval configurable (#20) (821bc4b)
  pollDelay() was hardcoded to a 200ms base with 120ms of jitter, so the only way to tune how often a follower wakes to re-check the bucket was to fork the library. A deployment with a fast downstream pays for waits it does not need, and one with a slow downstream cannot back off.
• Run Redis integration tests with Testcontainers (#19) (ff72e1f)
  The integration tests were gated on a socket probe against localhost:6379 and skipped themselves when nothing answered, so a build on a machine with no Redis went green having verified none of the library's actual behaviour.
• Split the request flow into three diagrams, list the open issues (#17) (0c89b77)
  The request flow was one flowchart 1617 pixels wide. Any column narrower than that scales the whole diagram down, and bitsar.net renders it at 720 pixels, where its 16px labels come out at roughly 7px. It is split into the three questions it was answering: what a caller does…
• Stop documentation pushes from publishing a release (#18) (1d6317a)
  Two patch numbers on Central are documentation. 0.2.4 came from #6, a README-only pull request titled [skip release]: a squash merge of a single-commit branch takes its subject from the commit and appends (#N), so the marker never reached 8bcdd89, which is the message this…

What's Changed

• Stop documentation pushes from publishing a release [skip release] by @BitanSarkar in #18
• Split the request flow into three diagrams, list the open issues [skip release] by @BitanSarkar in #17
• Run Redis integration tests with Testcontainers [skip release] by @Aaqibhafeezkhan in #19
• #10: Make the follower poll interval configurable by @Aaqibhafeezkhan in #20

New Contributors

• @Aaqibhafeezkhan made their first contribution in #19

Full Changelog: v0.2.5...v0.2.6

0.2.5

implementation 'net.bitsar:coalesce-spring-boot-starter:0.2.5'

Published to Maven Central. Central deployment 435383db-ad97-4b8d-a7a4-e671009d674d, built by run 34624810418.

Verify what actually landed:

./gradlew -p consumer-check test -PcoalesceVersion=0.2.5

What changed

• Add three diagrams to the README (ea17ded)
  Light and dark variants served through , because GitHub strips inline SVG from markdown and CSS variables do not resolve in an .

Full Changelog: v0.2.4...v0.2.5

0.2.4

implementation 'net.bitsar:coalesce-spring-boot-starter:0.2.4'

Published to Maven Central. Central deployment 89e96c35-4835-4d51-a467-b1d37f5abacf, built by run 34624143521.

Verify what actually landed:

./gradlew -p consumer-check test -PcoalesceVersion=0.2.4

What changed

• Advertise 0.2.3 in the README, and account for the kill switch's round trip (#6) (8bcdd89)
  0.2.3 has been on Central since the runtime kill switch merged, but the install snippets still said 0.2.1, so anyone copying them got a version two releases behind. The snippets are pinned by hand now: rewriting them automatically used to be the job of the version-bump commit,…

What's Changed

• Advertise 0.2.3 in the README [skip release] by @BitanSarkar in #6

Full Changelog: v0.2.3...v0.2.4

0.2.3

implementation 'net.bitsar:coalesce-spring-boot-starter:0.2.3'

Published to Maven Central. Central deployment 887954ae-5a36-4770-b685-0a2e30d86778, built by run 34030972941.

Verify what actually landed:

./gradlew -p consumer-check test -PcoalesceVersion=0.2.3

What changed

• Add a runtime kill switch for @Coalesce (#5) (b61c1ed)
  • Add a runtime kill switch for @Coalesce

What's Changed

• Add a runtime kill switch for @Coalesce by @BitanSarkar in #5

Full Changelog: v0.2.2...v0.2.3

0.2.2

implementation 'net.bitsar:coalesce-spring-boot-starter:0.2.2'

Published to Maven Central. Central deployment a6d9b150-6423-4fc9-b27c-dace38159908, built by run 34026227625.

Verify what actually landed:

./gradlew -p consumer-check test -PcoalesceVersion=0.2.2

What changed

• Take the published version from git tags instead of a file (#4) (9f60c0e)
  The release workflow used to commit the next version back to main after publishing. The protect-main ruleset requires a pull request, so that push is rejected and every release half-completes: published to Central and tagged, with main still holding the version that was just…

What's Changed

• Open 0.2.2 for development [skip release] by @BitanSarkar in #3
• Take the published version from git tags instead of a file [skip release] by @BitanSarkar in #4

Full Changelog: v0.2.1...v0.2.2

0.2.1

implementation 'net.bitsar:coalesce-spring-boot-starter:0.2.1'

Published to Maven Central. Central deployment 32ccc5d0-5ce2-4141-aca7-440626e921f7, built by run 34020767497.

Verify what actually landed:

./gradlew -p consumer-check test -PcoalesceVersion=0.2.1

What changed

• Reject configurations that silently do not coalesce, and fix the published URLs (#2) (091a5e5)
  Three contained fixes, no wire-format change.
• Rewrite the documentation prose to remove AI writing patterns (#1) (12b6e7a)
  Prose-only pass over README.md, CONTRIBUTING.md, RELEASING.md and docs/00 through docs/06.
• Update GitHub Actions to Node 24 runtimes and document the PR workflow (83393fa)
  Every run was annotated twice: four actions still targeted Node 20, which the runners were force-upgrading to Node 24, and setup-java v4 is end of life.

What's Changed

• Rewrite the documentation prose to remove AI writing patterns [skip release] by @BitanSarkar in #1
• Reject configurations that silently do not coalesce, and fix the published URLs by @BitanSarkar in #2

New Contributors

• @BitanSarkar made their first contribution in #1

Full Changelog: v0.2.0...v0.2.1

0.2.0

Built and signed by CI run 33988709047; Central deployment 552c15ca-88b4-41de-b2b2-063d1a3d1aa7.

0.1.2

Built and signed by CI run 33987248825; Central deployment be6298b1-5a46-4527-9a1c-7fe0d573870c.

0.1.1

Published to Maven Central before the release pipeline was automated. Behaviourally identical to 0.1.0; superseded by 0.1.2.

0.1.0

First publication of net.bitsar:coalesce-spring-boot-starter to Maven Central.

Built and signed by CI run 33984032499, deployment
0f42e265-4953-4c97-b227-c9a23f562f04, signed with PGP key
F3C0FD1FEF69C21166938341B25F19208BEDB559.