Bump reactor-core from 3.2.11.RELEASE to 3.3.0.RELEASE

[dependabot-preview]

Bumps reactor-core from 3.2.11.RELEASE to 3.3.0.RELEASE.

Release notes

Sourced from reactor-core's releases.

v3.3.0.RC1

Reactor-Core 3.3.0.RC1 is part of Dysprosium-RC1 Pre-Release Train.

This first release candidate of the 3.3.x cycle contains bugfixes and improvements from the GA 3.2.12.RELEASE as well as a few new features. It also involves a few behavior impacting changes and deprecations.

⚠️ Update considerations and deprecations

• A few Mono operators have slightly changed their behavior in regards to how when they propagate 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)
  • A new overload has been introduced that uses BiFunction for error handler (exposing the failure that causes "rollback")
  • A single-handler version has been added to Mono for alignment with Flux. This is the simplest case: same handler for complete, error and cancel terminations.
  • All other overloads have been deprecated. Goal is to favor either the simple 1-handler-covers-all case OR force users to be explicit about ALL possible terminations.

✨ New features and improvements

• Due to a few Throwable constants, class references could leak in multi-classloader environments. This is now avoided by skipping the filling of the stacktrace (#1872)
• Add BufferUntilChanged operator (#1706, bb5b2bb5)
• Added new StepVerifier API to subscribe to source and verify it later (#1848, b2ce5fe6)

🪲 Bug fixes

• Flux#flatMap with scalar source now supports onErrorContinue (#1684)
• Flux#doAfterTerminate now executed when onError in fused mode (#1836, #1835)
• Explicitly catch LinkageError in Traces. This helps with some static analyzers (#1830)
• Pass on cancelSupport when lifting ConnectableFlux (#1860)

📖 Documentation, Tests and Build

• [github] Removed CONTRIBUTING.md and issue_template in favor of centralized ones (740c0483)

• [build] Use JCenter, not MavenCentral for doDownloadBaseline (aa087096, d4f53322)

• [doc] Remove double mention of subscribe in Flux README (#1861)

• [doc] Document that default initial delay for interval is the period (#1866)

• [doc] Add limitRate marble diagrams (#1449)

• [build] Polish benchmarks build, remove jmh plugin (#1844, 1ba49448)

• [doc] Fix several typos in javadocs (#1845)

• [build] Make it possible to run two JMH tasks - baseline and current (#1862)

• [polish] Fix MaterializeSubscriber toString, AbstractQueue's won't work (df34ad92)

• [chores] Update BlockHound to RC1 (#1877)

👍 Thanks to the following contributors that also participated to this release

@​gindex, @​UgiR

v3.3.0.M3

Reactor-Core 3.3.0.M3 is part of Dysprosium-M3 Release Train.

This third milestone of the 3.3.x cycle contains bugfixes and improvements (including changes from the GA 3.2.11.RELEASE) as well as some behavior/API impacting changes:

... (truncated)

Commits

• d5a124f [artifactory-release] Release version 3.3.0.RELEASE
• 89d473c Prepare release 3.3.0.RELEASE
• de66f37 fix #1903 Document reactor-tools in refguide
• 32d2a29 see #1804 Enforce 100K task cap on Schedulers.boundedElastic()
• f705674 Polish windowUntilChanged predicate cleanup on cancel (#1901)
• 87d636d [test] Add direct assertion method on RetainedDetector, polish few tests
• 07e0be7 fix #1804 Add a Scheduler that caps number of threads and scales to 0
• 682fe6c [test] Rework autoCleanup methods into a reusable JUnit Rule
• 239d236 [doc] Disambiguate lowTide example in limitRate javadoc
• 918c92c fix #1883 Avoid extra lastAssembly by using CorePublisher where possible
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.