NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Maven Central, #951 by repository stars
Reactor Test support
Latest stable
3.8.8
Last release 26 days ago
23 Oct 2026
Ships fairly regularly
a new release about every 5 weeks
Nearly every release is documented
notes for 59 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
183 releases · first in 2019
Drag across the ruler to compare, or tap a release to open it.
<!-- Release notes generated using configuration in .github/release.yml at v3.5.17 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.5.17 -->
Reactor Core 3.5.17 is part of 2022.0.19 Release Train.
Full Changelog: https://github.com/reactor/reactor-core/compare/v3.5.16...v3.5.17
<!-- Release notes generated using configuration in .github/release.yml at v3.5.16 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.5.16 -->
Full Changelog: https://github.com/reactor/reactor-core/compare/v3.5.15...v3.5.16
Your coding agent can read these notes before it upgrades. Set up the MCP server →
<!-- Release notes generated using configuration in .github/release.yml at v3.5.15 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.5.15 -->
Reactor Core 3.5.15 is part of 2022.0.17 Release Train.
ColdTestPublisher by @OlegDokuka in #3700Mono#share javadoc for cancelling by @chemicL in #3741Full Changelog: https://github.com/reactor/reactor-core/compare/v3.5.14...v3.5.15
<!-- Release notes generated using configuration in .github/release.yml at v3.5.14 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.5.14 -->
Reactor Core 3.5.14 is part of 2022.0.15 Release Train.
Full Changelog: https://github.com/reactor/reactor-core/compare/v3.5.13...v3.5.14
<!-- Release notes generated using configuration in .github/release.yml at v3.5.13 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.5.13 -->
Reactor Core 3.5.13 is part of 2022.0.14 Release Train.
SinkManyUnicast discard support during subscription cancel by @chemicL in #3641MemoryUtils.Tracked used in tests releases collections by @chemicL in #3328StressSubscriber discardedValues should not have downstream type by @chemicL in #3643byteBuddyVersion from 1.14.8 to 1.14.9 by @dependabot in #3619Full Changelog: https://github.com/reactor/reactor-core/compare/v3.5.12...v3.5.13
<!-- Release notes generated using configuration in .github/release.yml at v3.5.12 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.5.12 -->
Reactor Core 3.5.12 is part of 2022.0.13 Release Train.
throwable assignment happens-before done assignment in onError for FluxPublish by @OlegDokuka in #3638JCStress: Await Scheduler dispose and increase timeouts by @chemicL in #3630Micrometer and Micrometer Tracing by @pderop in #3636Full Changelog: https://github.com/reactor/reactor-core/compare/v3.5.11...v3.5.12
<!-- Release notes generated using configuration in .github/release.yml at v3.5.11 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.5.11 -->
addCap always returns value with flag by @OlegDokuka in https://github.com/reactor/reactor-core/pull/3610contextualName presence by @OlegDokuka in https://github.com/reactor/reactor-core/pull/3611FluxBufferTime uses proper index value during onNext check by @OlegDokuka in https://github.com/reactor/reactor-core/pull/3614Full Changelog: https://github.com/reactor/reactor-core/compare/v3.5.10...v3.5.11
<!-- Release notes generated using configuration in .github/release.yml at v3.5.10 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.5.10 -->
Reactor Core 3.5.10 is part of 2022.0.11 Release Train.
Mono.tap in javadoc by @ajax-surovskyi-y in #3564Micrometer version to 1.10.11 by @chemicL in 7f9c77ec28dc0bdfc1eafe04062cb1195fd9b552Full Changelog: https://github.com/reactor/reactor-core/compare/v3.5.9...v3.5.10
<!-- Release notes generated using configuration in .github/release.yml at v3.5.9 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.5.9 -->
Reactor Core 3.5.9 is part of 2022.0.10 Release Train.
FluxPublish internals to relay on predictable state machine by @OlegDokuka in #3538takeUntil Predicate test before emit by @AramMessdaghi9001 in #3544MonoDelayElement to properly handle race between run and onNext by @OlegDokuka in #3546GroupedFlux delivers subscription for the second subscriber by @OlegDokuka in #3555onRequest consumer observes demand by @OlegDokuka in #3557gradle/wrapper-validation-action from 1.0.5 to 1.1.0 in /.github/workflows by @dependabot in #3542com.gradle.enterprise from 3.12.4 to 3.14.1 by @dependabot in #3548actions/setup-java from 3.6.0 to 3.12.0 in /.github/workflows by @dependabot in #3550gradle/gradle-build-action from 2.3.3 to 2.7.0 in /.github/workflows by @dependabot in #3551Micrometer version to 1.10.10 by @violetagg in #3560Full Changelog: https://github.com/reactor/reactor-core/compare/v3.5.8...v3.5.9
Update retryWhen docs on deprecated currentContext by @cbrunsdon in https://github.com/reactor/reactor-core/pull/3283
<!-- Release notes generated using configuration in .github/release.yml at v3.5.8 -->
Reactor Core 3.5.8 is part of 2022.0.9 Release Train.
FluxRefCount by @OlegDokuka in https://github.com/reactor/reactor-core/pull/3517sourceMode is obtained with happens-before relationships by @OlegDokuka in https://github.com/reactor/reactor-core/pull/3518Full Changelog: https://github.com/reactor/reactor-core/compare/v3.5.7...v3.5.8
<!-- Release notes generated using configuration in .github/release.yml at v3.5.7 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.5.7 -->
@Override to MonoDefer#subscribe by @manzhizhen in #3471Full Changelog: https://github.com/reactor/reactor-core/compare/v3.5.6...v3.5.7
<!-- Release notes generated using configuration in .github/release.yml at v3.5.6 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.5.6 -->
Reactor-Core 3.5.6 is part of 2022.0.7 Release Train.
Micrometer version to 1.10.7 by @violetagg in #3453Full Changelog: https://github.com/reactor/reactor-core/compare/v3.5.5...v3.5.6
<!-- Release notes generated using configuration in .github/release.yml at v3.5.5 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.5.5 -->
Reactor-Core 3.5.5 is part of 2022.0.6 Release Train.
Full Changelog: https://github.com/reactor/reactor-core/compare/v3.5.4...v3.5.5
<!-- Release notes generated using configuration in .github/release.yml at v3.5.4 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.5.4 -->
Reactor-Core 3.5.4 is part of 2022.0.5 Release Train.
ContextPropagation#isContextPropagationAvailable from the preprocessing for native-image support by @violetagg in #3374, by @izeye in #3376ExecutorScheduler should use onScheduleHook by @chemicL in #3356ContextQueue wrapper peek method implementation by @chemicL in #3368onErrorStop instead on cleaning context by @OlegDokuka in #3370Renovate with Dependabot by @chemicL in #3377dependencies.gradle in root project by @chemicL in #3381Mockito 5.x by @chemicL in #3385ArchUnit 1+ by @chemicL in #3394org.openjdk.jcstress:jcstress-core from 0.15 to 0.16 by @dependabot in #3378com.gradle.enterprise from 3.12.3 to 3.12.4 by @dependabot in #3379byteBuddyVersion from 1.12.23 to 1.14.1 by @dependabot in #3382jmhVersion from 1.35 to 1.36 by @dependabot in #3383org.assertj:assertj-core from 3.23.1 to 3.24.2 by @dependabot in #3389org.openjdk.jol:jol-core from 0.16 to 0.17 by @dependabot in #3393Full Changelog: https://github.com/reactor/reactor-core/compare/v3.5.3...v3.5.4
Reactor-Core 3.5.3 is part of `2022.0.3` Release Train.
Reactor-Core 3.5.3 is part of 2022.0.3 Release Train.
concatMapIterable by @OlegDokuka in #3329FlatMap #3353 by @OlegDokuka in #3353Full Changelog: https://github.com/reactor/reactor-core/compare/v3.5.2...v3.5.3
<!-- Release notes generated using configuration in .github/release.yml at v3.5.2 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.5.2 -->
Reactor-Core 3.5.2 is part of 2022.0.2 Release Train.
reflection hints for native-image support by @violetagg in #3325Full Changelog: https://github.com/reactor/reactor-core/compare/v3.5.1...v3.5.2
<!-- Release notes generated using configuration in .github/release.yml at v3.5.1 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.5.1 -->
Reactor-Core 3.5.1 is part of 2022.0.1 Release Train.
Sinks.one()#tryEmitValue(null) by @simonbasle in #3287RetrySpec by @OlegDokuka in #3316Add jcenter() to the repositories list by @violetagg in #32793.5.0, adapt Shakespeare bench to 2022.0.0 release by @simonbasle in #3278NotNull annotation from jetbrains by @OlegDokuka in #3303Full Changelog: https://github.com/reactor/reactor-core/compare/v3.5.0...v3.5.1
fixes breaking change for fromFuture source cancellation by @OlegDokuka in #3252
Reactor-Core 3.5.0 is part of 2022.0.0 Release Train.
This is the first GA release of 2022.0.0 🎉
This note focuses on 3.5.0 proper, curating changes from across all milestones and also includes changes already released as part of 3.4.x line up to 3.4.25.
While there are plenty of improvements and bug fixes, it's worth to highlight the bigger themes first:
Mono stack is now more lazy and complies to the Reactive Streams specification by only evaluating the source Publisher after receiving appropriate demand. Previously this usually happened during subscription time.ThreadLocal contextual metadata. Reactor supports this bridging as soon as context-propagation library is present at runtime. Read more in the reference documentation.Please pay special attention to the following update considerations. More detailed listing of features, bug fixes, and improvements follow.
Mono.doOn/AfterSuccessOrError by @simonbasle in #2954
doOn* recommended alternatives include doOnNext(Consumer), doOnError(Consumer), doOnTerminate(Runnable), and doOnSuccess(Consumer),doAfter* recommended alternatives are doAfterTerminate(Runnable) and doFinally(Consumer).deferWithContext(Function) -> use deferContextual(Function) instead,subscriberContext(Context) and subscriberContext(Function) -> use contextWrite(ContextView) and contextWrite(Function) instead,Signal::getContext() -> use Signal::getContextView() instead,Context::putAll(Context) -> use Context::putAll(ContextView) instead.ElasticScheduler by @simonbasle in #2955
BoundedElasticScheduler (Schedulers.boundedElastic()) instead.reactor-core-micrometer by @simonbasle in #3015
reactor-core-micrometer, and added operators and features supporting the new Observation API of Micrometer 1.10.0, read more about it the release notes.reactor.util.Metrics, Flux::metrics() and Mono::metrics() operators have been deprecated.[Flux|Mono|Synchronous]Sink currentContext by @simonbasle in #2974, #3021
contextView() should be used instead.Scheduler#init() method should be used instead. Restart capability is discouraged and the new method is allowed to throw in case of initializing a disposed instance. Please create a new Scheduler instance when necessary.Scheduler should also implement the init() method, which currently delegates to start() in the default implementation.Mono sources and aggregators lazier by @OlegDokuka in #3081switchOnNext/switchMap default 0 prefetch by @simonbasle in #2956concatMap default to 0 prefetch behavior by @simonbasle in #2967take(n) now behaves as take(n,true)/limitRequest by @simonbasle in #2969SourceException wrapper for main stream errors delivered to windows by @chemicL in #3167Scheduler.isDisposed() only true for disposed instances by @chemicL in #3243Scannable.tags() rework, add tagsDeduplicated() by @simonbasle in #3037MonoSubscriber by @UgiR in #3245
Mono operators derived from the Operators.MonoSubscriber have stopped negotiating fusion (even though their Publisher still implements Fuseable)StepVerifier's expectFusion(...))ThreadLocalscontext-propagation-api dependency + ReactorContextAccessor by @simonbasle in #3098, #3107, #3256ContextPropagation runtime util + captureContext operator by @simonbasle in #3145handle/tap implicit ThreadLocal restoration if ContextCapture by @simonbasle in #3180forEach method to ContextView and subclasses by @chemicL in #3092Context::forEach by @chemicL in #3101Context::putAllMap by @chemicL in #3102reactor-core-micrometer by @simonbasle in #3015
StateLogger for structured logging of state machines by @OlegDokuka in #3077Observation names and tag keys by @simonbasle in #3110Micrometer#observation(): avoids scopes, set parentObservation by @simonbasle in #3119Exceptions.throwIf[Jvm]Fatal, add isFatal methods by @simonbasle in #3122TimedScheduler to reactor-core-micrometer module by @simonbasle in #3109Flux.mergePriority, does not wait for all sources to emit by @osi in #3267windowTimeout with fairBackpressure by @OlegDokuka in #3054Flux.replay(int) and Flux.cache(int) by @chemicL in #3200disposeGracefully method to Scheduler by @chemicL in #3089Scheduler initialization by @chemicL in #3248Scheduler#disposeGracefully threads by @simonbasle in #3259Schedulers.onHandleError by @simonbasle in #3039whenComplete by @He-Pin in #3221FluxZip/MonoZip by @OlegDokuka in #3209map function in NPE msg by @ismailalammar in #2984StepVerifier option to use ConditionalSubscriber by @simonbasle in #3035VirtualTimeScheduler by @mdindoffer in #3097StepVerifier evaluates signal that exits thenConsumeWhile by @simonbasle in #3203LoggerUtils support and add TestLoggerExtension by @simonbasle in #3123FluxReplay buffer retaining/leaking with tiny TTL by @simonbasle in #2998SinkOneMulticast by @simonbasle in #3002Many sink / EmitterProcessor subscriber disposal leak by @simonbasle in #3029doOnEach ASYNC fusion triggering onNext signal twice by @simonbasle in #3045MonoCollect[List] by @simonbasle in #3053onLastAssembly does not break fusion chain by @OlegDokuka in #3156Loggers.useConsoleLoggers() thread safety by @alexismanin in #3174BoundedElasticScheduler rejects task by @Fearsin in #3183WorkerTask#dispose by @nathankooij in #3213tryEmitXXX call by @OlegDokuka in #3260FluxTakeUntilOther by @simonbasle in #3270FluxTakeUntilOther by @haraldpusch in #3219fromFuture source cancellation by @OlegDokuka in #3252windowTimeout stress test to use sinks by @OlegDokuka in #3074BoundedElasticTest with better controlled tasks by @simonbasle in #2968Schedulers javadoc for common/cached instances by @dedeibel in #2995BoundedElasticScheduler toString test by @simonbasle in #3010context-propagation-api dependency optional + documentation by @simonbasle in #3100ContextN.putAll(Map) intended internal use in javadoc by @chemicL in #3103Exceptions#bubble(Throwable) by @chemicL in #3160EmitFailureHandle#busyLooping by @He-Pin in #3224FluxPublishOnTest by @simonbasle in #3241MonoSubscriber comments by @UgiR in #3261EmitFailureHandler.busyLooping in refguide by @ivyazmitinov in #3271Mono fromFuture/fromCompletionStage javadocs by @simonbasle in #3272reactor-core-micrometer module compilation errors by @simonbasle in #3132BoundedElasticScheduler test by @simonbasle in #3142Full Changelog: https://github.com/reactor/reactor-core/compare/v3.4.16...v3.5.0
A very nice version in my opinion fixing a number of small bugs and slightly increased speed in a couple of corner cases. Thanks to everybody who reports bugs in he forum and by email!
There is also a new language — XML. A custom XML formerly was detected as HTML
and didn't highlight custom tags. In this version I tried to make custom XML to
be detected and highlighted by its own rules. Which by the way include such
things as CDATA sections and processing instructions (<? ... ?>).
<!-- Release notes generated using configuration in .github/release.yml at v3.4.41 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.4.41 -->
Reactor Core 3.4.41 is part of 2020.0.47 Release Train.
This is the last release of 3.4.x, as 2020.0.x Release Train is going out of OSS support. For the next steps, check our support policy.
byteBuddyVersion from 1.14.17 to 1.14.18 by @dependabot in #3842Full Changelog: https://github.com/reactor/reactor-core/compare/v3.4.40...v3.4.41
Reactor Core 3.4.40 is part of `2020.0.46` Release Train.
Reactor Core 3.4.40 is part of 2020.0.46 Release Train.
Full Changelog: https://github.com/reactor/reactor-core/compare/v3.4.39...v3.4.40
<!-- Release notes generated using configuration in .github/release.yml at v3.4.39 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.4.39 -->
Reactor Core 3.4.39 is part of 2020.0.45 Release Train.
byteBuddy version from 1.14.16 to 1.14.17 by @dependabot in #3820Full Changelog: https://github.com/reactor/reactor-core/compare/v3.4.38...v3.4.39
<!-- Release notes generated using configuration in .github/release.yml at v3.4.38 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.4.38 -->
Reactor Core 3.4.38 is part of 2020.0.44 Release Train.
Full Changelog: https://github.com/reactor/reactor-core/compare/v3.4.37...v3.4.38
<!-- Release notes generated using configuration in .github/release.yml at v3.4.37 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.4.37 -->
Full Changelog: https://github.com/reactor/reactor-core/compare/v3.4.36...v3.4.37
<!-- Release notes generated using configuration in .github/release.yml at v3.4.36 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.4.36 -->
Reactor Core 3.4.36 is part of 2020.0.42 Release Train.
ColdTestPublisher by @OlegDokuka in #3700Mono#share javadoc for cancelling by @chemicL in #3741Full Changelog: https://github.com/reactor/reactor-core/compare/v3.4.35...v3.4.36
<!-- Release notes generated using configuration in .github/release.yml at v3.4.35 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.4.35 -->
Reactor Core 3.4.35 is part of 2020.0.40 Release Train.
Full Changelog: https://github.com/reactor/reactor-core/compare/v3.4.34...v3.4.35
<!-- Release notes generated using configuration in .github/release.yml at v3.4.34 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.4.34 -->
Reactor Core 3.4.34 is part of 2020.0.38 Release Train.
addCap always returns value with flag by @OlegDokuka in 0b988cb1cef0339df81220b937e75fff5c7c9123Full Changelog: https://github.com/reactor/reactor-core/compare/v3.4.33...v3.4.34
<!-- Release notes generated using configuration in .github/release.yml at v3.4.33 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.4.33 -->
Full Changelog: https://github.com/reactor/reactor-core/compare/v3.4.32...v3.4.33
<!-- Release notes generated using configuration in .github/release.yml at v3.4.32 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.4.32 -->
Reactor Core 3.4.32 is part of 2020.0.35 Release Train.
GroupedFlux delivers subscription for the second subscriber by @OlegDokuka in #3555onRequest consumer observes demand by @OlegDokuka in #3557gradle/wrapper-validation-action from 1.0.5 to 1.1.0 in /.github/workflows by @dependabot in #3542com.gradle.enterprise from 3.12.4 to 3.14.1 by @dependabot in #3548actions/setup-java from 3.6.0 to 3.12.0 in /.github/workflows by @dependabot in #3550gradle/gradle-build-action from 2.3.3 to 2.7.0 in /.github/workflows by @dependabot in #3551Full Changelog: https://github.com/reactor/reactor-core/compare/v3.4.31...v3.4.32
Update retryWhen docs on deprecated currentContext by @cbrunsdon in https://github.com/reactor/reactor-core/pull/3283
<!-- Release notes generated using configuration in .github/release.yml at v3.4.31 -->
Reactor Core 3.4.31 is part of 2020.0.34 Release Train.
FluxRefCount by @OlegDokuka in https://github.com/reactor/reactor-core/pull/3517sourceMode is obtained with happens-before relationships by @OlegDokuka in https://github.com/reactor/reactor-core/pull/3518Full Changelog: https://github.com/reactor/reactor-core/compare/v3.4.30...v3.4.31
<!-- Release notes generated using configuration in .github/release.yml at v3.4.30 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.4.30 -->
@Override to MonoDefer#subscribe by @manzhizhen in #3471Full Changelog: https://github.com/reactor/reactor-core/compare/v3.4.29...v3.4.30
<!-- Release notes generated using configuration in .github/release.yml at v3.4.29 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.4.29 -->
Reactor-Core 3.4.29 is part of 2020.0.31 Release Train (Europium SR31).
Full Changelog: https://github.com/reactor/reactor-core/compare/v3.4.28...v3.4.29
<!-- Release notes generated using configuration in .github/release.yml at v3.4.28 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.4.28 -->
Reactor-Core 3.4.28 is part of 2020.0.30 Release Train (Europium SR30).
ExecutorScheduler should use onScheduleHook by @chemicL in #3356onErrorStop instead on cleaning context by @OlegDokuka in #3370Renovate with Dependabot by @chemicL in #3377dependencies.gradle in root project by @chemicL in #3381Mockito 5.x by @chemicL in #3385ArchUnit 1+ by @chemicL in #3394org.openjdk.jcstress:jcstress-core from 0.15 to 0.16 by @dependabot in #3378com.gradle.enterprise from 3.12.3 to 3.12.4 by @dependabot in #3379byteBuddyVersion from 1.12.23 to 1.14.1 by @dependabot in #3382jmhVersion from 1.35 to 1.36 by @dependabot in #3383org.assertj:assertj-core from 3.23.1 to 3.24.2 by @dependabot in #3389org.openjdk.jol:jol-core from 0.16 to 0.17 by @dependabot in #3393Full Changelog: https://github.com/reactor/reactor-core/compare/v3.4.27...v3.4.28
Reactor-Core 3.4.27 is part of `2020.0.28` Release Train (`Europium` SR28).
Reactor-Core 3.4.27 is part of 2020.0.28 Release Train (Europium SR28).
concatMapIterable by @OlegDokuka in #3329FlatMap #3353 by @OlegDokuka in #3353Full Changelog: https://github.com/reactor/reactor-core/compare/v3.4.26...v3.4.27
<!-- Release notes generated using configuration in .github/release.yml at v3.4.26 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.4.26 -->
Reactor-Core 3.4.26 is part of 2020.0.26 Release Train (Europium SR26).
Sinks.one()#tryEmitValue(null) by @simonbasle in #3287RetrySpec by @OlegDokuka in #3316NotNull annotation from jetbrains by @OlegDokuka in #3303Full Changelog: https://github.com/reactor/reactor-core/compare/v3.4.25...v3.4.26
Fix breaking change for fromFuture source cancellation by @OlegDokuka in #3252
<!-- Release notes generated using configuration in .github/release.yml at v3.4.25 -->
Reactor-Core 3.4.25 is part of 2020.0.25 Release Train (Europium SR25).
Scheduler#init() method should be used instead. Restart capability is discouraged and the new method is allowed to throw in case of initializing a disposed instance. Please create a new Scheduler instance when necessary.Scheduler should also implement the init() method, which currently delegates to start() in the default implementation.MonoSubscriber by @UgiR in #3245
Mono operators derived from the Operators.MonoSubscriber have stopped negotiating fusion (even though their Publisher still implements Fuseable)StepVerifier's expectFusion(...))FluxZip/MonoZip by @OlegDokuka in #3209Scheduler initialization by @chemicL in #3248MonoSubscriber by @UgiR in #3245fromFuture source cancellation by @OlegDokuka in #3252Flux.mergePriority, does not wait for all sources to emit by @osi in #3267Scheduler#disposeGracefully threads by @simonbasle in #3259tryEmitXXX call by @OlegDokuka in #3260FluxTakeUntilOther by @simonbasle in #3270 (fixing a 3.4.24 regression)FluxPublishOnTest by @simonbasle in #3241SingleScheduler.isDisposed() only true on disposed instance by @chemicL in #3242GHA API for setting output, latest core actions by @simonbasle in #3237MonoSubscriber comments by @UgiR in #3261Mono#fromFuture/fromCompletionStage javadocs by @simonbasle in #3272Full Changelog: https://github.com/reactor/reactor-core/compare/v3.4.24...v3.4.25
<!-- Release notes generated using configuration in .github/release.yml at v3.4.24 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.4.24 -->
Flux.replay(int) and Flux.cache(int) by @chemicL in #3200StepVerifier evaluates signal that exits thenConsumeWhile by @simonbasle in #3203FluxTakeUntilOther by @haraldpusch in #3219CompletionStage#handle instead of whenComplete by @He-Pin in #3221BoundedElasticScheduler rejects task by @Fearsin in #3183WorkerTask#dispose by @nathankooij in #3213EmitFailureHandle#busyLooping by @He-Pin in #3224Full Changelog: https://github.com/reactor/reactor-core/compare/v3.4.23...v3.4.24
<!-- Release notes generated using configuration in .github/release.yml at v3.4.23 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.4.23 -->
disposeGracefully method to Scheduler by @chemicL in https://github.com/reactor/reactor-core/pull/3089onErrorComplete operator and rework onErrorReturn by @simonbasle in https://github.com/reactor/reactor-core/pull/3159onLastAssembly does not break fusion chain by @OlegDokuka in https://github.com/reactor/reactor-core/pull/3156Loggers.useConsoleLoggers() thread safety by @alexismanin in https://github.com/reactor/reactor-core/pull/3174Full Changelog: https://github.com/reactor/reactor-core/compare/v3.4.22...v3.4.23
<!-- Release notes generated using configuration in .github/release.yml at v3.4.22 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.4.22 -->
Reactor-Core 3.4.22 is part of 2020.0.22 Release Train (Europium SR22).
Exceptions.throwIf[Jvm]Fatal, add isFatal methods by @simonbasle in #3122LoggerUtils support and add TestLoggerExtension by @simonbasle in #3123processExistingClasses in debugging.adoc by @kicmeri in #3130BoundedElasticScheduler test by @simonbasle in #3142Full Changelog: https://github.com/reactor/reactor-core/compare/v3.4.21...v3.4.22
<!-- Release notes generated using configuration in .github/release.yml at v3.4.20 -->
<!-- Release notes generated using configuration in .github/release.yml at v3.4.20 -->
Reactor-Core 3.4.21 is part of 2020.0.21 Release Train (Europium SR21).
Full Changelog: https://github.com/reactor/reactor-core/compare/v3.4.19...v3.4.21
:exclamation: This release was not included in Project Reactor BOM. Please check v3.4.21.
:exclamation: This release was not included in Project Reactor BOM.
Please check v3.4.21.
Reactor-Core 3.4.19 is part of 2020.0.20 Release Train (Europium SR20).
Reactor-Core 3.4.19 is part of 2020.0.20 Release Train (Europium SR20).
fairBackpressure boolean parameter.Reactor-Core 3.4.18 is part of `2020.0.19` Release Train (`Europium` SR19).
Reactor-Core 3.4.18 is part of 2020.0.19 Release Train (Europium SR19).
map function in NPE msg by @ismailalammar in #2984Deprecate [Flux|Mono|Synchronous]Sink currentContext by @simonbasle in #2974
Reactor-Core 3.4.17 is part of 2020.0.18 Release Train (Europium SR18).
<!-- Release notes generated using configuration in .github/release.yml at v3.4.17 -->
Reactor-Core 3.4.16 is part of `2020.0.17` Release Train (`Europium` SR17).
Reactor-Core 3.4.16 is part of 2020.0.17 Release Train (Europium SR17).
This service release contains a few bugfixes and improvements.
Full Changelog: https://github.com/reactor/reactor-core/compare/v3.4.15...v3.4.16
Reactor-Core 3.4.15 is part of `2020.0.16` Release Train (`Europium` SR16).
Reactor-Core 3.4.15 is part of 2020.0.16 Release Train (Europium SR16).
This service release contains a few bugfixes.
Full Changelog: https://github.com/reactor/reactor-core/compare/v3.4.14...v3.4.15
Reactor-Core 3.4.14 is part of `2020.0.15` Release Train (`Europium` SR15).
Reactor-Core 3.4.14 is part of 2020.0.15 Release Train (Europium SR15).
This release contains a cancellation bug fix on usingWhen, as well as build and docs improvements.
Reactor-Core 3.4.13 is part of `2020.0.14` Release Train (`Europium` SR14).
Reactor-Core 3.4.13 is part of 2020.0.14 Release Train (Europium SR14).
This service release contains a couple enhancements and documentation updates.
@kaladhar-mummadi
Reactor-Core 3.4.12 is part of `2020.0.13` Release Train (`Europium` SR13).
Reactor-Core 3.4.12 is part of 2020.0.13 Release Train (Europium SR13).
This service release contains improvement to tracebacks rendering, introduces a couple utility methods to Logger and bring bugfixes.
All changes from 3.3.22.RELEASE are also included and these are listed below with an additional level of indentation.
@NonNull annotation, not JetBrain's NotNull (#2808)@dominikbrandon, @lhauspie, @boroborome, @bigdaz, @trettstadtnlb, @EMellau
Reactor-Core 3.4.11 is part of `2020.0.12` Release Train (`Europium` SR12).
Reactor-Core 3.4.11 is part of 2020.0.12 Release Train (Europium SR12).
This service release contains bugfixes and one enhancement.
All changes from 3.3.21.RELEASE are also included and these are listed below with an additional level of indentation.
limit(0) (#2787)@rs017991
…of sharing it, although the whole approach is deprecated.
Reactor-Core 3.4.10 is part of 2020.0.11 Release Train (Europium SR11).
This service release contains bugfixes and polishing changes.
All changes from 3.3.20.RELEASE are also included and these are listed below with an additional level of indentation.
Flux.replay underlying implementation doesn't support 0-size anymore (which was illogical in the first place)
Flux.publish() instead (#2741)Disposable obtained by calling mono.share().subscribe() (and that variant only) would terminate/cancel the whole mono.share() for all its subscribers. now this is an individual subscription, much like .subscribe(v -> {}) for instance.toProcessor() and explicitly turning the source Mono into a MonoProcessor instead of sharing it, although the whole approach is deprecated.FluxOnBackpressureBufferStrategy reject sizes <= 0 (#2757)hasNext (#2766)@hisener, @KATKrazy, @keturn
Reactor-Core 3.4.9 is part of `2020.0.10` Release Train (`Europium` SR10).
Reactor-Core 3.4.9 is part of 2020.0.10 Release Train (Europium SR10).
This service release contains bugfixes and new features.
Some changes from 3.3.19.RELEASE are also included and these are listed below with an additional level of indentation.
@ivyazmitinov
Flux#mergeOrdered has been deprecated
Reactor-Core 3.4.8 is part of 2020.0.9 Release Train (Europium SR9).
This service release contains bugfixes and new features.
Flux#mergeOrdered has been deprecated (#2719)
mergeComparing has been introduced as an alternative that is more consistent with other merge operatorsmergeComparing as fail-fast alternative to mergeOrdered (complemented with a delayError variant) (#2719)Mono.cacheInvalidateIf and Mono.cacheInvalidateWhen (#2717)
Predicate on the value when a late subscriber comes in or by associating the cached value with a Mono<Void> invalidation trigger that can be externally completed@koldat
Explain deprecation workaround for Context#putAll(Context)
Reactor-Core 3.4.7 is part of 2020.0.8 Release Train (Europium SR8).
This minor service release contains build and test improvements as well as one new minor feature.
All changes from 3.3.18.RELEASE are also included and these are listed below with an additional level of indentation.
@clayly, @eas5
Reactor-Core 3.4.6 is part of `2020.0.7` Release Train (`Europium` SR7).
Reactor-Core 3.4.6 is part of 2020.0.7 Release Train (Europium SR7).
This service release contains bugfixes and new features.
All changes from 3.3.17.RELEASE are also included and these are listed below with an additional level of indentation.
MonoDelay doesn't produce a OverflowException backpressure error when the delay is so small that it terminates before regular request had a chance to be made (since the operator assume subscribe == request, like a lot of Monos).
reactor.core.publisher.MonoDelay.failOnBackpressure with value true. contextWrite(f) rather than subscriberContext(f) in docs (#2685)main, update CI (#2679)@horizonzy, @robotmrv, @vovikdrg
Reactor-Core 3.4.5 is part of `2020.0.6` Release Train (`Europium` SR6).
Reactor-Core 3.4.5 is part of 2020.0.6 Release Train (Europium SR6).
This service release contains bugfixes and a couple implementation improvements forwarded from the 3.3.x line as well as documentation improvements.
All changes from 3.3.16.RELEASE are also included and these are listed below with an additional level of indentation.
@berry120, @mickeelm, @underbell
Reactor-Core 3.4.4 is part of `2020.0.5` Release Train (Codename `Europium`).
Reactor-Core 3.4.4 is part of 2020.0.5 Release Train (Codename Europium).
This service release contains a few improvements and new features. It also contains bugfixes from the 3.3.x line.
All changes from 3.3.15.RELEASE are also included and these are listed below with an additional level of indentation.
MonoInnerProducerBase (#2632, #2645)Mono.fromSupplier(() -> null).single() previously failed to produce an onError(NoSuchElementException) (#2635)
Mono that was implementing Callable (which includes fromSupplier, fromCallable, fromRunnable to some extent...) would exhibit the wrong behaviorFlux#single, which is going to be fixed by #2657 in the next release@kevinten10, @mickeelm, @SimonBerry555, @v-terret
Reactor-Core 3.4.3 is part of `2020.0.4` release train (Europium SR4).
Reactor-Core 3.4.3 is part of 2020.0.4 release train (Europium SR4).
This is a maintenance release which also inherit changes from 3.3.14.RELEASE.
switchMap/switchOnNext with prefetch=0 (#2596)skipUntil conditional subscriber logic inconsistent (#2578)concatMap (#2576)TestLogger be configured with simplified format (#2538)@richardfearn, @vdjuketic
Reactor-Core 3.4.2 is part of `2020.0.3` Release Train (`Europium` SR3).
Reactor-Core 3.4.2 is part of 2020.0.3 Release Train (Europium SR3).
This service release contains a couple bugfixes inherited from 3.3.13.RELEASE as well as additional documentation polishing.
This note focuses on changes specific to this version, see also from 3.3.13.RELEASE release notes
@bbukaty
fix #2468 Review and polish deprecation suppressions
Reactor-Core 3.4.1 is part of 2020.0.2 Release Train (Europium SR2).
This service release contains bugfixes and new features.
This note focuses on changes specific to this version, but all changes from 3.2.22.RELEASE and 3.3.12.RELEASE are also included.
Timed wrapper object, allowing richer output of Duration compared to elapsed() and timestamp() (which use Tuple2 and Long)LoggerUtils allows the early installation of a Logger factory that will forward to a classic factory AND let the user activate a logging indirection later on during testsTestLogger to capture internal logs from operators that were classloaded earlier than the unit testTestPublisher
createColdNonCompliant variantContext in StepVerifier, say from which operator the asserted Context was taken (#2518)RetryWhenMainSubscriber#onError's calls serial (#2499, Fixes #2488)@dowgiallom, @seants
Schedulers deprecated back in 3.3 have been removed (WorkQueueProcessor and TopicProcessor, #2208)
Reactor-Core 3.4.0 is part of 2020.0.0 Release Train (codename Europium).
This is the first GA release of Europium :tada:
This note focuses on 3.4.0 proper, curating changes from across all milestones.
Note that the 3.4.0 effort was started right after 3.3.5.RELEASE, so this version also contains changes from 3.3.6 to 3.3.11 (see the end of the notes for links).
firstWithValue new operator has an undocumented way of checking the cause of failure for individual sources, but it uses a suppressed exception rather than a cause. Please refrain from using that, as we'll switch to initCause in 3.4.1 (and properly document the behavior, setting it in stone) => #2459WorkQueueProcessor and TopicProcessor, #2208)Schedulers.elastic() and variants are deprecated, to be removed in 3.5 (#1893)FluxProcessor (as well as all concrete implementations of it) are now deprecated and will be removed in 3.5 (#2188, #2431)
MonoProcessor is made abstract and deprecated, to be removed in 3.5 (#2188, #1053 / f04bede3, #2431)
Flux.subscribe(Consumer<Subscription>) variant is deprecated, to be removed in 3.5 (#1825)first is deprecated to be renamed to firstWithSignal (see firstWithValue in the new features below). The old deprecated method will be removed in 3.5 (#2173)Context changes (#2282):
Context at points where there is no use attempting to use write methods are deprecated and will be removed in 3.5 (#2293, 7d6c8625)
ContextView-based variant (see new features below)deferWithContext => deferContextual with a ContextViewSignal.getContext() => Signal.getContextView()Context are renamed to be clearer. Old names are deprecated and will be removed in 3.5 (see new feature below, #2148, eed93d64)Duration and convert it to milliseconds now use nanosecond precision (#1734)Operators.onErrorDropped no longer throws, but only logs the dropped exception (#1431)onError signal reaches the last (lambda based) subscriber in a chain which doesn't have an error handler, the exception is no longer thrown but only logged (#2176)Scheduler now initiate their backing infrastructure and apply Schedulers decorator in start() rather than the constructor (#1778)
start() is also now implicitly called when instantiating a Scheduler via the Schedulers.Factorythis leaking from constructorstart()EmitterProcessor with a full backpressure queue no longer blocks until data is requested, but fails fast (#2049)name operator (#1928, #2302)
flow tag has been removed entirelyname({String}) operator will replace reactor. prefix in meter names with the user-provided {String}.tags(String...) operator, but not name(String) still creates a sparse set of tags in the application which could be rejected by some metrics backendreactor_requested_requested_amount => {name}_requestedreactor_subscribed_subscribers => {name}_subscribed{name} into account from the above changestatus tag, introducing completedEmpty value (#1803)SinksSinks are a new API constructed to replace the FluxProcessor and MonoProcessor APIs, which have been deprecated (#2431, #1053).
We distinguish Sinks.Many<T> (a Flux-like sink), Sinks.One<T> (a Mono-like sink) and Sinks.Empty (a Mono<Void>-like sink).
These sinks are constructed through specs under the Sinks class. They expose a two-faced API:
tryEmit are atomic, never throw (#2319, #2329, #2336, #2426) and immediately return an EmitResult enum (originally named Emission) indicating various variations of success or error (#2319, #2338)emit attempt to provide an easier facade over the above, take an EmitFailureHandler allowing to fine tune some aspects of the default behavior (#2377)By default, the instances are "serialized", detecting parallel usage and failing fast in tryEmit (#2342, #2410, #2365, 19fc1ba1, #2412).
The vanilla reactor sink implementations of emit API terminate with the equivalent of an emitError when parallel usage is detected (#2365) but by using the EmitFailureHandler to drive the sink to retry, possibly with a small amount of sleeping, it should be possible to optimistically get rid of the contention.
It is also possible to get a low-overhead, low-protection instance of vanilla sinks by using the Sinks.unsafe() spec (#2418).
This doesn't detect parallel usage, so it must be used in a responsible way (in a context where the Reactive Streams contract is already externally enforced).
Sinks also expose a asFlux() view (or asMono(), as relevant) for them to be passed to downstream and subscribed, and also expose a bit of state through currentSubscriberCount() getter (#2372) and by being Scannable (at a minimum for TERMINATED and CANCELLED attributes, #2394).
Compared to existing processors, most flavors have a sink equivalent except DirectProcessor, with two close cousins under Sinks.many().multicast() (#2392, #2451):
directAllOrNothing will ignore tryEmitNext attempts when at least one subscriber doesn't have enough demand,directBestEffort will instead push to the subset of subscribers with demand and drop from the perspective of slow subscribers.This differs from DirectProcessor in the sense that both these sinks are kept open in such a situation, so slow subscribers that increase their request will start seeing values pushed after that (instead of being immediately terminated in DirectProcessor).
There is also a new flavor: an onBackpressureError() variant of the unicast Sink (#2347)
See links to Dysprosium releases (3.3.6 to 3.3.11) at the end.
concatMap now has a variant with 0 prefetch (#2202)Scannable operators answer the new Attr.RUN_STYLE attribute with a RunStyle enum (#2058, #2123)
Publisher and Subscriber levelRunStyle.SYNC guarantees the operator doesn't change threadsRunStyle.ASYNC indicates the operator MAY change threadsRunStyle.UNKNOWN (the default) indicates there's no available information (eg. due to the operator wrapping an arbitrary Publisher)MetricsRegistry other than the global one can now be configured (#2253, 64fd556)
Metrics.MicrometerConfiguration#useRegistry for that purposeContext now extends a simplified ContextView API which only expose the read methods (#2279, #2293)
Context when the only meaningful operations are read operationsSignal#getContextView(), deferContextual operator (variant to deferWithContext) and new transformDeferredContextual operatortransformDeferredContextual operator that takes a BiFunction, allowing to access the ContextView in the transformation (#2280 then renamed in #2293)
Mono.subscribe(valueConsumer, errorConsumer, ...) error Consumer now gets notified of exceptions thrown by the value Consumer (#1995)Context operators with clearer names (#2148, eed93d64)
Mono.subscriberContext() is not aliased, we now advise to use Mono.deferContextual(Mono::just) to get the exact same behaviorsubscriberContext(Context) is replaced by contextWrite(ContextView) (notice the use of ContextView)contextWrite(Function)Schedulers.setFactoryWithSnapshot(Factory) to get a Snapshot object while replacing the FactoryresetFrom(Snapshot)VirtualTimeScheduler to reset previously customized factoriesParallelFlux.subscribe(array) method is now public to allow delegation in wrappers (#2328)Retry object driving #retryWhen operator can now store user-provided state in the form of a ContextView, which is exposed through RetrySignal (#2312, bd8db8ab)GroupedFlux#key() method is now marked as @NonNull (#2397)firstWithValue factory operator (#2173, 41c937ff)
first, it let multiple sources competeNoSuchElementException is thrownlog() will log context access at FINE(ST) level and now uses the more correct currentContext prefix (#2220)Mono#materialize() now takes into account that the source IS a Mono, so it doesn't cancel() it when materializing its onNext (#2424, 765bfe8f)
@AayushyaVajpayee, @camsteffen, @cnabro, @hamidshahid, @Inego, @jonenst, @josemalonsom, @OlegDokuka, @robotmrv, @seants, @smaldini, @steppedreckoner, @yschimke
All changes from these releases have been forward-merged into 3.4.0:
One column per quarter.