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.

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

Bump projectreactor.version from 3.4.9 to 3.4.10 #1926

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 15, 2021

Bumps projectreactor.version from 3.4.9 to 3.4.10.
Updates reactor-core from 3.4.9 to 3.4.10

Release notes

Sourced from reactor-core's releases.

v3.4.10

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.

⚠️ Update considerations and deprecations

  • Flux.replay underlying implementation doesn't support 0-size anymore (which was illogical in the first place)
    • For now, the operator transparently translates such calls to Flux.publish() instead (#2741)
  • Align Mono#share() behavior with Flux#share, split sink impl out (#2756)
    • Previously the 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.
    • the old behavior can still be obtained by calling toProcessor() and explicitly turning the source Mono into a MonoProcessor instead of sharing it, although the whole approach is deprecated.

✨ New features and improvements

  • from 3.3.x:
    • Have FluxOnBackpressureBufferStrategy reject sizes <= 0 (#2757)

🪲 Bug fixes

  • Rework FluxReplay to avoid hanging, but reject 0 size (#2741)
  • Align Mono#share() behavior with Flux#share, split sink impl out (#2756)
  • Fix bad switchOnFirst state transition leading to dropped error (#2768)
  • from 3.3.x:
    • [reactor-test] Fix consumeWhile+expectRecorded* skipping signal (#2764)
    • In FluxIterable, defer hasNext exceptions from isEmpty to poll to protect against iterators that throw in hasNext (#2766)

📖 Documentation, Tests and Build

  • Fix onDiscard/onErrorContinue javadoc position in Flux/Mono (#2762)
  • [doc] remove stray mid-sentence newlines (#2763)
  • from 3.3.x:
    • Document that windows (and groupBy groups) are unicast (#2767, #2568)

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

@​hisener, @​KATKrazy, @​keturn

Commits
  • 0a67ce9 [release] Prepare and release 3.4.10
  • 3ebc865 Merge-ignore release 3.3.20 into main
  • dc4bc6f [release] Next development version 3.3.21.BUILD-SNAPSHOT
  • be7bb47 [release] Prepare and release 3.3.20.RELEASE
  • 7d8ea6f Fix bad switchOnFirst state transition leading to dropped error (#2768)
  • 7623a2b Merge #2767 (document window unicast) into 3.4.10
  • c849e44 Document that windows (and groupBy groups) are unicast
  • a596764 Rework FluxReplay to avoid hanging, but reject 0 size (#2741)
  • a72bb0d Merge #2766 into 3.4.10
  • 3d620dc In FluxIterable, defer hasNext exceptions from isEmpty to poll (#2766)
  • Additional commits viewable in compare view

Updates reactor-test from 3.4.9 to 3.4.10

Release notes

Sourced from reactor-test's releases.

v3.4.10

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.

⚠️ Update considerations and deprecations

  • Flux.replay underlying implementation doesn't support 0-size anymore (which was illogical in the first place)
    • For now, the operator transparently translates such calls to Flux.publish() instead (#2741)
  • Align Mono#share() behavior with Flux#share, split sink impl out (#2756)
    • Previously the 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.
    • the old behavior can still be obtained by calling toProcessor() and explicitly turning the source Mono into a MonoProcessor instead of sharing it, although the whole approach is deprecated.

✨ New features and improvements

  • from 3.3.x:
    • Have FluxOnBackpressureBufferStrategy reject sizes <= 0 (#2757)

🪲 Bug fixes

  • Rework FluxReplay to avoid hanging, but reject 0 size (#2741)
  • Align Mono#share() behavior with Flux#share, split sink impl out (#2756)
  • Fix bad switchOnFirst state transition leading to dropped error (#2768)
  • from 3.3.x:
    • [reactor-test] Fix consumeWhile+expectRecorded* skipping signal (#2764)
    • In FluxIterable, defer hasNext exceptions from isEmpty to poll to protect against iterators that throw in hasNext (#2766)

📖 Documentation, Tests and Build

  • Fix onDiscard/onErrorContinue javadoc position in Flux/Mono (#2762)
  • [doc] remove stray mid-sentence newlines (#2763)
  • from 3.3.x:
    • Document that windows (and groupBy groups) are unicast (#2767, #2568)

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

@​hisener, @​KATKrazy, @​keturn

Commits
  • 0a67ce9 [release] Prepare and release 3.4.10
  • 3ebc865 Merge-ignore release 3.3.20 into main
  • dc4bc6f [release] Next development version 3.3.21.BUILD-SNAPSHOT
  • be7bb47 [release] Prepare and release 3.3.20.RELEASE
  • 7d8ea6f Fix bad switchOnFirst state transition leading to dropped error (#2768)
  • 7623a2b Merge #2767 (document window unicast) into 3.4.10
  • c849e44 Document that windows (and groupBy groups) are unicast
  • a596764 Rework FluxReplay to avoid hanging, but reject 0 size (#2741)
  • a72bb0d Merge #2766 into 3.4.10
  • 3d620dc In FluxIterable, defer hasNext exceptions from isEmpty to poll (#2766)
  • 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)

Bumps `projectreactor.version` from 3.4.9 to 3.4.10.

Updates `reactor-core` from 3.4.9 to 3.4.10
- [Release notes](https://github.com/reactor/reactor-core/releases)
- [Commits](reactor/reactor-core@v3.4.9...v3.4.10)

Updates `reactor-test` from 3.4.9 to 3.4.10
- [Release notes](https://github.com/reactor/reactor-core/releases)
- [Commits](reactor/reactor-core@v3.4.9...v3.4.10)

---
updated-dependencies:
- dependency-name: io.projectreactor:reactor-core
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: io.projectreactor:reactor-test
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: In Progress Use to signal this issue is actively worked on. Target: 4.5.4 Type: Dependency Upgrade Use to signal an issue that adjusts the project’s dependencies. Typically used by dependabot only. labels Sep 15, 2021
@dependabot dependabot bot added this to the Release 4.5.4 milestone Sep 15, 2021
@smcvb smcvb self-assigned this Sep 15, 2021
@sonarcloud
Copy link

sonarcloud bot commented Sep 15, 2021

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

Copy link
Member

@smcvb smcvb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me 👍

@smcvb smcvb merged commit cc0b937 into axon-4.5.x Sep 15, 2021
@smcvb smcvb added Status: Resolved Use to signal that work on this issue is done. and removed Status: In Progress Use to signal this issue is actively worked on. labels Sep 15, 2021
@dependabot dependabot bot deleted the dependabot/maven/axon-4.5.x/projectreactor.version-3.4.10 branch September 15, 2021 07:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: Resolved Use to signal that work on this issue is done. Type: Dependency Upgrade Use to signal an issue that adjusts the project’s dependencies. Typically used by dependabot only.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant