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

Update dependency io.projectreactor:reactor-core to v3.4.16 #177

Merged
merged 1 commit into from Mar 21, 2022

Conversation

ghost
Copy link

@ghost ghost commented Mar 21, 2022

This PR contains the following updates:

Package Update Change
io.projectreactor:reactor-core patch 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
🐞 Bug fixes
📖 Documentation, Tests and Build
🆙 Dependency Upgrades

New Contributors

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


Configuration

📅 Schedule: "after 8pm every weekday,every weekend,before 8am every weekday" in timezone America/Argentina/Buenos_Aires.

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

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.

@nicomz nicomz merged commit 19d227e into master Mar 21, 2022
@nicomz nicomz deleted the renovate-project.reactor.version branch March 21, 2022 12:26
@simonbasle
Copy link

@nicomz just wanted to let you know that the (self-hosted?) Renovate version that produced this PR didn't appear to sanitize URLs in the body of the changelog.

Renovate does include the entire reactor-core changelog in the commit body, and in the case of reactor-core (and reactor-netty) it includes github URLs displayed as full github.com URLs. This is what the GitHub "generate changelog" button produces when we create the Release.

Renovate usually sanitizes the markdown source of the Renovate PR body is using togithub URLs.
This avoids GitHub displaying back links to Renovate PRs inside (reactor) issues.

In the case of this PR and a couple more from other mulesoft projects, no sanitizing was performed :(

Don't know if you can do something about the renovate-pro-kbuild bot instance, so that's a shot in the dark but I'm trying anyway.

More context in renovatebot/renovate#14804

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants