Bump reactor_netty from 1.1.26 to 1.1.27#17322
Conversation
|
❌ Gradle check result for 42566b1: 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? |
Signed-off-by: Andriy Redko <drreta@gmail.com>
42566b1 to
6757cec
Compare
|
Bumping to 1.2.x release seems to be premature (due to Azure Java SDK is still using 1.0.x release line) |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #17322 +/- ##
============================================
- Coverage 72.41% 72.34% -0.08%
+ Complexity 65531 65472 -59
============================================
Files 5291 5291
Lines 304335 304335
Branches 44181 44181
============================================
- Hits 220395 220164 -231
- Misses 65838 66052 +214
- Partials 18102 18119 +17 ☔ View full report in Codecov by Sentry. |
|
The backport to To backport manually, run these commands in your terminal: # Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-2.x
# Create a new branch
git switch --create backport/backport-17322-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 5feb514f27e063eb6bf68c47dd939802bd0ca2d4
# Push it to GitHub
git push --set-upstream origin backport/backport-17322-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-2.xThen, create a pull request where the |
Signed-off-by: Andriy Redko <drreta@gmail.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> (cherry picked from commit 5feb514) Signed-off-by: Andriy Redko <drreta@gmail.com>
Bumps
reactor_nettyfrom 1.1.26 to 1.2.3.Updates
io.projectreactor.netty:reactor-netty-corefrom 1.1.26 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-SNAPSHOTdcceb8b[release] Prepare and release 1.1.2718d7ce2Merge #3624 into 1.2.3b4d8806Bump org.apache.tomcat.embed:tomcat-embed-core from 9.0.98 to 9.0.99 (#3624)d90ddb9Merge #3623 into 1.2.30eecfd2Depend on Netty v4.1.118.Final (#3623)7de5e89Merge #3622 into 1.2.36dd174eBump netty-tcnative-boringssl-static to version v2.0.70.Final (#3622)Updates
io.projectreactor.netty:reactor-netty-httpfrom 1.1.26 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-SNAPSHOTdcceb8b[release] Prepare and release 1.1.2718d7ce2Merge #3624 into 1.2.3b4d8806Bump org.apache.tomcat.embed:tomcat-embed-core from 9.0.98 to 9.0.99 (#3624)d90ddb9Merge #3623 into 1.2.30eecfd2Depend on Netty v4.1.118.Final (#3623)7de5e89Merge #3622 into 1.2.36dd174eBump netty-tcnative-boringssl-static to version v2.0.70.Final (#3622)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 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)