Bump reactor-core from 3.4.24 to 3.5.1

[dependabot]

Bumps reactor-core from 3.4.24 to 3.5.1.

Release notes

Sourced from reactor-core's releases.

v3.5.1

Reactor-Core 3.5.1 is part of 2022.0.1 Release Train.

What's Changed

⚠️ Update considerations and deprecations

• Fix regression: Sinks.one()#tryEmitValue(null) by @​simonbasle in #3287
• Ensure context restored in RetrySpec by @​OlegDokuka in #3316

✨ New features and improvements

• Ensure given iterable is interacted once per subscriber by @​OlegDokuka in #3297

🐞 Bug fixes

• Fix #3307 case by @​OlegDokuka in #3312

📖 Documentation, Tests and Build

• Revert Add jcenter() to the repositories list by @​violetagg in #3279
• Perf baseline 3.5.0, adapt Shakespeare bench to 2022.0.0 release by @​simonbasle in #3278
• Fix typo in in documentation by @​SpikeBlues in #3300
• Remove NotNull annotation from jetbrains by @​OlegDokuka in #3303

New Contributors

• @​SpikeBlues made their first contribution in #3300

Full Changelog: reactor/reactor-core@v3.5.0...v3.5.1

v3.5.0

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:

• The 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.
• We reworked the metrics utilities. Please consult the reference documentation for more details.
• A new context-propagation library has become an important part of the Reactor and Micrometer backbone to allow bridging between reactive and 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.

⚠️ Update considerations and deprecations

⚠️ 🗑️ Removals

• Remove Kotlin extensions by @​simonbasle in #2949
  • These now live in the reactor-kotlin-extensions library
• Remove deprecated Mono.doOn/AfterSuccessOrError by @​simonbasle in #2954
  • The doOn* recommended alternatives include doOnNext(Consumer), doOnError(Consumer), doOnTerminate(Runnable), and doOnSuccess(Consumer),
  • The doAfter* recommended alternatives are doAfterTerminate(Runnable) and doFinally(Consumer).
• Remove deprecated context-related operators by @​simonbasle in #2953
  • deferWithContext(Function) -> use deferContextual(Function) instead,

... (truncated)

Commits

• e0de5a1 [release] Prepare and release 3.5.1
• 9bab255 Merge-ignore release 3.4.26 into 3.5.1
• 36fad66 [release] Next development version 3.4.27-SNAPSHOT
• d2363ca [release] Prepare and release 3.4.26
• 94e7226 Merge #3312 into 3.5.1
• 9ae9858 fixes #3307 case (#3312)
• 558173d Merge #3307 into 3.5.1
• cfe1979 ensures context restored in RetrySpec (#3316)
• 69450bb Merge #3303 into 3.5.1
• a8d4cbd removes NotNull annotation from jetbrains (#3303)
• 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]

Superseded by #56.