Bump reactor_netty from 1.1.27 to 1.2.3 #17377
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
dependabot
dependabot
bot
requested review from
anasalkouz,
andrross,
ashking94,
Bukhtawar,
CEHENKLE,
cwperks,
dblock,
dbwiddis,
gbbafna,
jainankitk,
kotwanikunal,
linuxpi,
mch2,
msfroh,
nknize,
owaiskazi19,
reta,
Rishikesh1159,
sachinpkale,
saratvemulapalli,
shwetathareja,
sohami and
VachaShah
as code owners
|
❌ Gradle check result for 62f2b3c: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
dependabot
bot
force-pushed
the
dependabot/gradle/reactor_netty-1.2.3
branch
from
62f2b3c to
347751f
Compare
|
❌ Gradle check result for 52d10c5: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
|
❌ Gradle check result for 52d10c5: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
|
❌ Gradle check result for 52d10c5: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
dependabot
bot
force-pushed
the
dependabot/gradle/reactor_netty-1.2.3
branch
from
52d10c5 to
895cf57
Compare
|
❌ Gradle check result for 09efba8: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Bumps `reactor_netty` from 1.1.27 to 1.2.3. Updates `io.projectreactor.netty:reactor-netty-core` from 1.1.27 to 1.2.3 - [Release notes](https://github.com/reactor/reactor-netty/releases) - [Commits](reactor/reactor-netty@v1.1.27...v1.2.3) Updates `io.projectreactor.netty:reactor-netty-http` from 1.1.27 to 1.2.3 - [Release notes](https://github.com/reactor/reactor-netty/releases) - [Commits](reactor/reactor-netty@v1.1.27...v1.2.3) --- updated-dependencies: - dependency-name: io.projectreactor.netty:reactor-netty-core dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: io.projectreactor.netty:reactor-netty-http dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/gradle/reactor_netty-1.2.3
branch
from
09efba8 to
802a323
Compare
Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: dependabot[bot] <support@github.com>
|
❌ Gradle check result for 276a1cf: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Bumps
reactor_nettyfrom 1.1.27 to 1.2.3.Updates
io.projectreactor.netty:reactor-netty-corefrom 1.1.27 to 1.2.3Release notes
Sourced from io.projectreactor.netty:reactor-netty-core's releases.
... (truncated)
Commits
4e2176e[release] Prepare and release 1.2.30251007Merge-ignore release 1.1.27 into 1.2.33217e35[release] Back to snapshots, next is 1.1.28-SNAPSHOT18d7ce2Merge #3624 into 1.2.3d90ddb9Merge #3623 into 1.2.37de5e89Merge #3622 into 1.2.3bd98c1dBump com.github.luben:zstd-jni from 1.5.6-9 to 1.5.6-10 (#3621)c17c1e6Merge #3619 into 1.2.305f8046Merge #3618 into 1.2.3a2bccdcUpdate CodeQL badgeUpdates
io.projectreactor.netty:reactor-netty-httpfrom 1.1.27 to 1.2.3Release notes
Sourced from io.projectreactor.netty:reactor-netty-http's releases.
... (truncated)
Commits
4e2176e[release] Prepare and release 1.2.30251007Merge-ignore release 1.1.27 into 1.2.33217e35[release] Back to snapshots, next is 1.1.28-SNAPSHOT18d7ce2Merge #3624 into 1.2.3d90ddb9Merge #3623 into 1.2.37de5e89Merge #3622 into 1.2.3bd98c1dBump com.github.luben:zstd-jni from 1.5.6-9 to 1.5.6-10 (#3621)c17c1e6Merge #3619 into 1.2.305f8046Merge #3618 into 1.2.3a2bccdcUpdate CodeQL badgeDependabot 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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@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)