NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Maven Central, #953 by repository stars
Reactor Tools
Latest stable
3.8.8
Last release 1 months 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
143 releases · first in 2019
Drag across the ruler to compare, or tap a release to open it.
This is the last release of 3.3.x, as the Dysprosium line is now EoL
This is the last release of 3.3.x, as the Dysprosium line is now EoL
@NonNull annotation, not JetBrain's NotNull by @simonbasle in #2808Full Changelog: https://github.com/reactor/reactor-core/compare/v3.3.21.RELEASE...v3.3.22.RELEASE
Reactor-Core 3.3.21 is part of `Dysprosium-SR24` Release Train.
Reactor-Core 3.3.21 is part of Dysprosium-SR24 Release Train.
This service release contains one bugfixe and dependency bumps (including Gradle 7.2).
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Reactor-Core 3.3.20.RELEASE is part of `Dysprosium-SR23` Release Train.
Reactor-Core 3.3.20.RELEASE is part of Dysprosium-SR23 Release Train.
This service release contains bugfixes and polishing.
FluxOnBackpressureBufferStrategy reject sizes <= 0 (#2757)@hisener
Reactor-Core 3.3.19.RELEASE is part of `DYSPROSIUM-SR22` Release Train.
Reactor-Core 3.3.19.RELEASE is part of DYSPROSIUM-SR22 Release Train.
This service release contains a bugfix, as well as some build/ci polishing.
spotless plugin introduced to check java headers (#2722, #2732)Reactor-Core 3.3.18.RELEASE is part of `Dysprosium-SR21` Release Train.
Reactor-Core 3.3.18.RELEASE is part of Dysprosium-SR21 Release Train.
This minor service release contains a few test and build enhancements.
Reactor-Core 3.3.17.RELEASE is part of `Dysprosium-SR20` Release Train.
Reactor-Core 3.3.17.RELEASE is part of Dysprosium-SR20 Release Train.
This service release contains a few bugfixes and enhancements.
main, update CI (#2679)Reactor-Core 3.3.16.RELEASE is part of `Dysprosium-SR19` Release Train.
Reactor-Core 3.3.16.RELEASE is part of Dysprosium-SR19 Release Train.
This service release contains bugfixes and a couple implementation improvements.
@bruto1
Reactor-Core 3.3.15.RELEASE is part of `Dysprosium-SR18` Release Train.
Reactor-Core 3.3.15.RELEASE is part of Dysprosium-SR18 Release Train.
This service release mainly contains bugfixes.
MonoInnerProducerBase
MonoInnerProducerBase (#2632)MonoProducerBase but remove fusion support from MonoSingle (#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@martin-tarjanyi
Reactor-Core 3.3.14.RELEASE is part of `Dysprosium-SR17` release train.
Reactor-Core 3.3.14.RELEASE is part of Dysprosium-SR17 release train.
This is a maintenance release.
skipUntil conditional subscriber logic inconsistent (#2578)concatMap (#2576)@koldat, @mickeelm, @seants, @sjh836
Reactor-Core 3.3.13.RELEASE is part of `Dysprosium-SR16` Release Train.
Reactor-Core 3.3.13.RELEASE is part of Dysprosium-SR16 Release Train.
This service release contains a couple bugfixes and documentation polishing.
@OlegDokuka
Reactor-Core 3.3.12.RELEASE is part of `Dysprosium-SR15` Release Train.
Reactor-Core 3.3.12.RELEASE is part of Dysprosium-SR15 Release Train.
This service release contains a couple bugfixes and documentation polishing.
This note focuses on changes specific to this version, but all changes from 3.2.22.RELEASE are also included.
Mono contract was not sufficiently and explicitly stated in the docs, this has been fixed (#2481)@BilliAlpha
fix #2416 Don't blanket hide deprecated members in javadoc
Reactor-Core 3.3.11.RELEASE is part of Dysprosium-SR13 Release Train.
This is a recommended update for all Reactor 3 users.
This release also contains all changes available in 3.2.21.RELEASE
@yosfik
Reactor-Core 3.3.10.RELEASE is part of `Dysprosium-SR12` Release Train.
Reactor-Core 3.3.10.RELEASE is part of Dysprosium-SR12 Release Train.
This maintenance release contains one small enhancement to DirectProcessor/EmitterProcessor.
This version also contains all changes from v3.2.20.RELEASE.
Nothing published for this version
Reactor-Core 3.3.8.RELEASE is part of `Dysprosium-SR10` Release Train.
Reactor-Core 3.3.8.RELEASE is part of Dysprosium-SR10 Release Train.
This maintenance release is a recommended update for all Reactor 3 users.
This version also contains all changes from v3.2.19.RELEASE.
null publisher in MonoDelayUntil (#2245)@dennyac, @nicolasgavalda
reactor-core 3.3.7.RELEASE is part of `Dysprosium-SR9` Release Train.
reactor-core 3.3.7.RELEASE is part of Dysprosium-SR9 Release Train.
Flux.collect() (#2181)@rstoyanchev , @melix , @gurkerl83
Reactor-Core 3.3.6.RELEASE is part of `Dysprosium-SR8` Release Train.
Reactor-Core 3.3.6.RELEASE is part of Dysprosium-SR8 Release Train.
DeferredSubscription makes requests serially if there is racing between set / requestN (according to RS spec Rule 2.7)(#2164)FluxSwitchOnFirst serializes requests (according to RS spec Rule 2.7) (#2161)UnicastProcessor disposed to avoid racing between onNext and dispose (#2180)ZoneId.of(String) to avoid blocking disk load during first access of Schedulers.boundedElastic() (#2143)ASYNC fusion in Mono.metrics() to avoid NullPointerException or hanging in certain cases (#2160 )ConditionalSubscriber classcast in FluxSwitchOnFirst (#2166)Subscription set by reportThrowInSubscribe to an instance compatible with QueueSubscription, preventing fused cases where a ClassCastException would be thrown. (#2152 )publishOn scan test, hiccup before asserting BUFFEREDMono.first() and Mono.or() behavior (#2159)Retry.fromFunction() instead of from() (#2172)RetrySpec doc: throwablePredicate is actually filter (#2162)onCancel / onDipose limited to 1 use (#2015)generate code example (#2110)@alex-dukhno , @chakas , @berry120 , @OlegDokuka , @PyvesB , @josemalonsom
reactor-core 3.3.5.RELEASE is part of `Dysprosium-SR7` Release Train.
reactor-core 3.3.5.RELEASE is part of Dysprosium-SR7 Release Train.
It also contains all fixes from 3.2.17.RELEASE.
subscribe method can lead to two onSubscribe signal if said exception is thrown after having sent the Subscription (#2107, #2111, #2072)StepVerifier cannot, which can "hide" the true errorSubscription can be identified with Operators.canAppearAfterOnSubscribe(Subscription), which is used by StepVerifier to ignore that particular extra subscriptionsubscribe/subscribeOrReturn mutualized implementation, prevent StepVerifier getting confused by a double onSubscribe in that very specific case ((#2072, #2107, #2111)onNext vs cancel races that would bypass resource discarding (#2134, #2126, #2102, #2124, #2125, #2122, #2077, #2102)
MonoDelayElement#onNext downstreamerrorOnSubscribe steps (#2112)errorOnSubscribe scenarios into separate tests (#2099)@TestFactory in BaseOperatorTest (#2085)@OlegDokuka, @pimlock
retryWhen(Function), all retryBackoff and retry(Predicate)/retry(long, Predicate) are now deprecated, to be replaced by the more generic retryWhen(Ret…
reactor-core 3.3.4.RELEASE is part of Dysprosium-SR6 Release Train.
retryWhen(Function), all retryBackoff and retry(Predicate)/retry(long, Predicate) are now deprecated, to be replaced by the more generic retryWhen(Retry) (see RetrySpec and RetryBackoffSpec for configurable builders that cover these methods and more)retryWhen(Function) and retryBackoff as well as some retry variants in 3.4.0Retry abstract class, with two builders (or Spec) to fluently configure the retriesonNext comes in between errorsrepeatWhen and retryWhen, when a Context is emitted, we now merge it with the current instead of replacing it (#2056)VirtualTimeScheduler#getOrSet(boolean) fixes virtual time in the StepVerifier (#2060, #2017)@OlegDokuka
reactor-core 3.3.3.RELEASE is part of `Californium-SR16` Release Train.
reactor-core 3.3.3.RELEASE is part of Californium-SR16 Release Train.
defer opt-in in VirtualTimeScheduler.create (#1251, #2012)
VirtualTimeScheduler will now eagerly advance time even if there is no pending task. Use the overload with defer=true to get the old default behavior.StepVerifier-created ones will continue lazily advancing time when no task is scheduled, in order to make testing of things like delays inside a flatMap possible.fromStream and fromIterable with custom non-Collection Iterables, see #2014 and #2021
iterator() method is now invoked twice per wrapping of a given Iterable (once through default spliterator() to check the iterable is finite aka. hasCharacteristic(SIZED), once for the iteration itself)Iterator is discarded when cancelled mid-iterationIterable is a Collection or its Spliterator has the SIZED characteristic.Iterable#iterator for custom iterablesCallable" in Flux#collectList (#2023, #2024)@btkelly, @ilyavy, @robotmrv, @yarosla
reactor-core 3.3.2.RELEASE is part of `Dysprosium-SR3` Release Train.
reactor-core 3.3.2.RELEASE is part of Dysprosium-SR3 Release Train.
Flux.replay/cache hanging or delivering wrong data (tracked in #2030)currentContext() with ArchUnit (#1988)@echooymxq, @hojongs, @martin-tarjanyi, @mdonkers, @OlegDokuka, @sgsfak
Reactor-Core 3.3.1.RELEASE is part of `Dysprosium-SR2` Release Train.
Reactor-Core 3.3.1.RELEASE is part of Dysprosium-SR2 Release Train.
It also includes changes from the 3.2.13.RELEASE version.
One important change to pick up for testing Reactor is in StepVerifier: the combination of expectNoEvent followed by thenCancel wasn't working terribly well, and a new better terminal expectation has been introduced: expectTimeout (#1913)
Flux.replay/cache hanging or delivering wrong data (tracked in #2030)StepVerifier: expectTimeout(Duration) as an alternative to expectNoEvent(Duration).thenCancel()transform or transformDeferred apply a transformation to a non-Reactor Publisher, warn when/if the original Context is lost (#1888)collectSortedListMap.Entry in Context1 to ensure various libraries don't represent it inconsistenly when printing out collections of ContextContextN (by extending LinkedHashMap instead of HashMap)Mono#cache(Function, Function, Supplier) (backported)VirtualTimeScheduler#getScheduledTaskCount() (backported)Flux#publish() propagate 1st subscriber ContextExceptions.isTraceback, and a mean to unwrap a composite without the tacebacks (Exceptions.unwrapMultipleExcludingTracebacks)parallel() not replenishing properlybufferWhile was incorrectly showing dropped separatorsFlux#join javadoc and marble have been clarifiedmaven-publish and artifactory (#1943)Exceptions.multiple(Iterable) now produces a CompositeException, more test coverage of Exceptions util (#1954)@andreisilviudragnea, @akarnokd, @berry120, @dittos, @EleanorRoseLegg, @gindex, @jabrena, @simondaudin, @slisaasquatch, @thiyagu-7, @ttddyy, @slisaasquatch, @wonwoo
Mono#do[On|After]SuccessOrError has been deprecated and marked for removal in 3.4
Reactor-Core 3.3.0.RELEASE is part of Dysprosium-RELEASE Release Train.
This release note covers the first GA release of the 3.3.x cycle, and as such describes the changes from the perspective of a 3.2.x to 3.3.0 comparison.
See also release notes from 3.2.12, 3.2.11, 3.2.10 and 3.2.9 for changes that were inherited from the 3.2.x maintenance releases.
This release is a big opportunity to polish the APIs and some behaviors with less restriction than maintenance releases.
🌟 It also introduces a few new features, the highlight of which is the BoundedElasticScheduler:
this one has evolved from the ElasticScheduler and is intended as a future replacement for it.
A cap can be put on the number of threads such a scheduler can spawn. After that cap is reached, further task submissions are deferred (being enqueued) up to a second global limit on enqueued tasks (optionally unbounded).
Flux.replay/cache hanging or delivering wrong data (tracked in #2030)onNext: they could trigger onError after onNext, which is not permitted in Mono.
Mono#usingWhen now waits for the async complete handler termination before propagating onNext (#1832)Mono#using similarly avoids triggering onNext+onError if cleanup fails (#1853)Mono#doOnTerminate now acts similarly to doOnSuccess, executing the side effect before the onNext is propagated downstream (#1752)Mono#do[On|After]SuccessOrError has been deprecated and marked for removal in 3.4 (#1854)usingWhen API has been polished, and some variants deprecated for removal in 3.4 (#1687)
BiFunction for error handler (exposing the failure that causes "rollback")Mono for alignment with Flux. This is the simplest case: same handler for complete, error and cancel terminations.WorkQueueProcessor and TopicProcessor have been marked as deprecated for 3.3.x and will be removed in 3.4UnsafeEmitterProcessor and publishOnreactor-kotlin-extensionsSchedulers.Factory#decorateExecutorService has been removedonBackpressureBuffer(maxSize+error) variants now delay errorscompose() has been deprecated and renamed transformDeferred()SignalonNext events to be emitted only when the subsequent signal is ready upstreamonComplete signal, the corresponding Signal must be explicitly requested from upstream (one extra request(1))Exceptions#unwrap) in most sources that immediately produce an error, acting like a Callable (b6f4d291)reactor-tools sources into the core repository (#1731)boundedElastic Scheduler that caps number of threads and scales to 0 (#1804)
scan(Attr.NAME) or toString) of global singleton Schedulers (#1885, #1886)
parallel(parallel) this is now Schedulers.parallel()Schedulers.DEFAULT_POOL_SIZE (which can be overridden by system property)subscribe from stack by optimizing the "tail calls" (#1761, #1826)Context lookups in error sources (4f2bc7a7)DelayedWorkQueue#take (#1726)Automatic-Module-Name (reactor.core and reactor.test, #1641, #1692)CorePublisher interface has been introduced to distinguish Publisher from reactor (#1527)toString representation of classes that are known to have an obscure representation, as well as extracting such objects that would be nested in containers like a Collection, Tuple2, Signal, ...Throwable as a suppressed exception@aftersss, @akarnokd, @apuravchauhan, @berry120, @Buzzardo, @dittos, @don-vip, @flambard, @gindex, @hisener, @izeye, @jnizet, @mumukiller, @OlegDokuka, @pcdavid, @pmackowski, @ramonPires, @szpak, @ttddyy, @UgiR, @zhouzhou19950825
One column per quarter.