Bump reactor-bom from 2020.0.8 to 2022.0.4 #3509
Conversation
Bumps [reactor-bom](https://github.com/reactor/reactor) from 2020.0.8 to 2022.0.4. - [Release notes](https://github.com/reactor/reactor/releases) - [Commits](reactor/reactor@2020.0.8...2022.0.4) --- updated-dependencies: - dependency-name: io.projectreactor:reactor-bom dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
… compatible release. Signed-off-by: James R. Perkins <jperkins@redhat.com>
https://issues.redhat.com/browse/RESTEASY-3298 Signed-off-by: James R. Perkins <jperkins@redhat.com>
|
@crankydillo Given you and your team contributed this code, could you have a look at this and let me know if it seems reasonable? We seem to be really behind, though I don't know how the versioning works :) There was a bug I found and filed which throws an exception for empty |
Hi @jamezp . I have taken this to the team. Currently, I'm trying to figure out why RE 5 is failing some of our regressions:(. I'm pretty sure these are our problems, not yours. I must say though. I have no problem with you driving |
|
hehe, cool. I just don't know much about reactive-netty so I wanted to make sure my changes weren't crazy. They were on the bug report I filed and have already merged a fix :) |
|
I don't see any crazy changes:) |
Bumps reactor-bom from 2020.0.8 to 2022.0.4.
Release notes
Sourced from reactor-bom's releases.
... (truncated)
Commits
96c81f8[release] Prepare and release BOM 2022.0.47c4d090Merge-ignore release 2020.0.29 into 2022.0.4194021f[release] Back to snapshots, next BOM will be SR 30fd3624d[release] Prepare and release BOM 2020.0.2979e5c5c[release] Back to snapshots, next BOM will be 2022.0.4fb270e1[release] Prepare and release BOM 2022.0.35bc982eMerge-ignore release 2020.0.28 into 2022.0.383f5012[release] Back to snapshots, next BOM will be SR 297d555b4[release] Prepare and release BOM 2020.0.288688dcaMerge 1f3ae91d into 2022.0.3Dependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)