Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update dependency io.projectreactor:reactor-core to v3.5.5 #10

Merged
merged 1 commit into from
May 8, 2023
Merged

Update dependency io.projectreactor:reactor-core to v3.5.5 #10

merged 1 commit into from
May 8, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 8, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
io.projectreactor:reactor-core 3.2.1.RELEASE -> 3.5.5 age adoption passing confidence

Release Notes

reactor/reactor-core

v3.5.5

Reactor-Core 3.5.5 is part of 2022.0.6 Release Train.

What's Changed

✨ New features and improvements
🐞 Bug fixes
📖 Documentation, Tests and Build
🆙 Dependency Upgrades
❓ Other Changes

New Contributors

Full Changelog: reactor/reactor-core@v3.5.4...v3.5.5

v3.5.4

Reactor-Core 3.5.4 is part of 2022.0.5 Release Train.

What's Changed

✨ New features and improvements
🐞 Bug fixes
📖 Documentation, Tests and Build
🆙 Dependency Upgrades

Full Changelog: reactor/reactor-core@v3.5.3...v3.5.4

v3.5.3

Reactor-Core 3.5.3 is part of 2022.0.3 Release Train.

What's Changed

⚠️ Update considerations and deprecations
  • ensures empty inner source handled properly in case of sync fusion for concatMapIterable by @​OlegDokuka in #​3329
✨ New features and improvements
🐞 Bug fixes
🆙 Dependency Upgrades

New Contributors

Full Changelog: reactor/reactor-core@v3.5.2...v3.5.3

v3.5.2

Reactor-Core 3.5.2 is part of 2022.0.2 Release Train.

What's Changed

🐞 Bug fixes

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

v3.5.1

Reactor-Core 3.5.1 is part of 2022.0.1 Release Train.

What's Changed

⚠️ Update considerations and deprecations
✨ New features and improvements
🐞 Bug fixes
📖 Documentation, Tests and Build

New Contributors

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
  • 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,
    • 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.
  • Remove deprecated ElasticScheduler by @​simonbasle in #​2955
    • Use BoundedElasticScheduler (Schedulers.boundedElastic()) instead.
⚠️ ⌛ Deprecations
  • Introduce new module reactor-core-micrometer by @​simonbasle in #​3015
    • We introduced a new module, 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.
    • The class reactor.util.Metrics, Flux::metrics() and Mono::metrics() operators have been deprecated.
  • Deprecate [Flux|Mono|Synchronous]Sink currentContext by @​simonbasle in #​2974, #​3021
    • contextView() should be used instead.
  • Deprecate scheduler start by @​chemicL in #​3236
    • 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.
    • Implementors of Scheduler should also implement the init() method, which currently delegates to start() in the default implementation.
⚠️ ♻️ Behavior Changes
  • Make some Mono sources and aggregators lazier by @​OlegDokuka in #​3081
  • Change behavior of switchOnNext/switchMap default 0 prefetch by @​simonbasle in #​2956
  • Have concatMap default to 0 prefetch behavior by @​simonbasle in #​2967
  • take(n) now behaves as take(n,true)/limitRequest by @​simonbasle in #​2969
  • SourceException wrapper for main stream errors delivered to windows by @​chemicL in #​3167
  • Scheduler.isDisposed() only true for disposed instances by @​chemicL in #​3243
  • adds cancellation of the source future support by @​OlegDokuka in #​3146
  • Scannable.tags() rework, add tagsDeduplicated() by @​simonbasle in #​3037
  • Disable fusion in MonoSubscriber by @​UgiR in #​3245
    • A number of Mono operators derived from the Operators.MonoSubscriber have stopped negotiating fusion (even though their Publisher still implements Fuseable)
    • The highest impact is likely to be on tests that validate the fusion negotiation (eg. StepVerifier's expectFusion(...))

✨ New features and improvements

Context propagation and bridging to ThreadLocals
Observability and logging
Operators and relevant machinery
reactor-test module

🐞 Bug fixes

📖 Documentation, Tests and Build

🆙 Dependency Upgrades

New Contributors

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

v3.4.29

Reactor-Core 3.4.29 is part of 2020.0.31 Release Train (Europium SR31).

What's Changed

✨ New features and improvements
🆙 Dependency Upgrades
❓ Other Changes

New Contributors

Full Changelog: reactor/reactor-core@v3.4.28...v3.4.29

v3.4.28

Reactor-Core 3.4.28 is part of 2020.0.30 Release Train (Europium SR30).

What's Changed

🐞 Bug fixes
📖 Documentation, Tests and Build
🆙 Dependency Upgrades

Full Changelog: reactor/reactor-core@v3.4.27...v3.4.28

v3.4.27

Reactor-Core 3.4.27 is part of 2020.0.28 Release Train (Europium SR28).

What's Changed

⚠️ Update considerations and deprecations
  • ensures empty inner source handled properly in case of sync fusion for concatMapIterable by @​OlegDokuka in #​3329
🐞 Bug fixes
🆙 Dependency Upgrades

Full Changelog: reactor/reactor-core@v3.4.26...v3.4.27

v3.4.26

Reactor-Core 3.4.26 is part of 2020.0.26 Release Train (Europium SR26).

What's Changed

⚠️ Update considerations and deprecations
✨ New features and improvements
🐞 Bug fixes
📖 Documentation, Tests and Build

New Contributors

Full Changelog: reactor/reactor-core@v3.4.25...v3.4.26

v3.4.25

Reactor-Core 3.4.25 is part of 2020.0.25 Release Train (Europium SR25).

What's Changed

⚠️ Update considerations and deprecations

⚠️ ⌛ Deprecations
  • Deprecate scheduler start by @​chemicL in #​3236
    • 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.
    • Implementors of Scheduler should also implement the init() method, which currently delegates to start() in the default implementation.
⚠️ ♻️ Behavior Changes
  • Disable fusion in MonoSubscriber by @​UgiR in #​3245
    • A number of Mono operators derived from the Operators.MonoSubscriber have stopped negotiating fusion (even though their Publisher still implements Fuseable)
    • The highest impact is likely to be on tests that validate the fusion negotiation (eg. StepVerifier's expectFusion(...))
✨ New features and improvements
🐞 Bug fixes
📖 Documentation, Tests and Build
🆙 Dependency Upgrades

New Contributors

Full Changelog: reactor/reactor-core@v3.4.24...v3.4.25

v3.4.24

What's Changed

✨ New features and improvements
🐞 Bug fixes
📖 Documentation, Tests and Build
🆙 Dependency Upgrades
  • Update dependencies junit, mockito, bytebuddy, jcstress, spotless... by @​chemicL in #​3218

New Contributors

Full Changelog: reactor/reactor-core@v3.4.23...v3.4.24

v3.4.23

Compare Source

What's Changed

✨ New features and improvements
🐞 Bug fixes
🆙 Dependency Upgrades

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot merged commit 218ab25 into master May 8, 2023
2 checks passed
@renovate renovate bot deleted the renovate/io.projectreactor-reactor-core-3.x branch May 8, 2023 02:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
0 participants