chore(deps): update dependency io.projectreactor:reactor-core to v3.4.16

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
io.projectreactor:reactor-core	3.4.15 -> 3.4.16

---

Release Notes

reactor/reactor-core

v3.4.16

Compare Source

Reactor-Core 3.4.16 is part of 2020.0.17 Release Train (Europium SR17).

This service release contains a few bugfixes and improvements.

What's Changed

✨ New features and improvements

• Improve BoundedElasticScheduler to be less blocking by @​simonbasle in https://github.com/reactor/reactor-core/pull/2909
• Add EmitFailureHandler.busyLoop flavor by @​Animesh27 in https://github.com/reactor/reactor-core/pull/2943

🐞 Bug fixes

• Fix Mono.then not cancelling between Callable sources by @​simonbasle in https://github.com/reactor/reactor-core/pull/2934

📖 Documentation, Tests and Build

• Update Gradle to v7.4 in https://github.com/reactor/reactor-core/pull/2922
• [doc] Correct flux subscribe example in faq by @​liukun2634 in https://github.com/reactor/reactor-core/pull/2924
• Show how-to-fix hints in CI when preliminary steps fail (check of license headers, api compatibility) by @​simonbasle in https://github.com/reactor/reactor-core/pull/2932
• [guide] Remove ref to Swing/SwtScheduler in addons appendix by @​simonbasle in https://github.com/reactor/reactor-core/pull/2959
• [build] Have jcstress part of slowerChecks by @​simonbasle in https://github.com/reactor/reactor-core/pull/2958

🆙 Dependency Upgrades

• Update plugin spotless to v6.3.0 in https://github.com/reactor/reactor-core/pull/2925
• Update plugin bnd to v6.2.0 in https://github.com/reactor/reactor-core/pull/2941
• Update dependency org.awaitility:awaitility to v4.2.0 in https://github.com/reactor/reactor-core/pull/2945
• Update dependency ch.qos.logback:logback-classic to v1.2.11 in https://github.com/reactor/reactor-core/pull/2946
• Update dependency com.tngtech.archunit:archunit to v0.23.1 in https://github.com/reactor/reactor-core/pull/2940
• Update plugin japicmp to v0.4.0 in https://github.com/reactor/reactor-core/pull/2948
• Update dependency org.mockito:mockito-core to v4.4.0 in https://github.com/reactor/reactor-core/pull/2951
• Update plugin download to v5.0.2 in https://github.com/reactor/reactor-core/pull/2950

New Contributors

• @​Animesh27 made their first contribution in https://github.com/reactor/reactor-core/pull/2943 👍

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

---

Configuration

📅 Schedule: "after 8am on Friday,before 12pm on Friday" (UTC).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, 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, click this checkbox.

---

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

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

[simonbasle]

@kurtisvg just wanted to let you know that the (automated?) commit from this PR copied over the textual version of the entire reactor-core changelog in the commit body. Since it includes github URLs, GitHub adds a link to this GCP commit in all our issues mentioned in the changelog 😞

Note also that the markdown source of the Renovate PR body is using togithub URLs, specifically to avoid these back links. Don't know if you can do something about the gcf-merge-on-green bot, so that's a shot in the dark but I'm trying anyway.

More context in renovatebot/renovate#14804

[kurtisvg]

Hi @simonbasle - I've opened a bug against the merge on green bot (googleapis/repo-automation-bots#3343) to ask the team to take a look and see if they can fix it.