Bump org.jruby.joni:joni from 2.2.3 to 2.2.5 in /libs/grok#17608
Bump org.jruby.joni:joni from 2.2.3 to 2.2.5 in /libs/grok#17608
Conversation
|
❕ Gradle check result for a40ff00: UNSTABLE
Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #17608 +/- ##
============================================
- Coverage 72.48% 72.46% -0.02%
- Complexity 65771 65785 +14
============================================
Files 5311 5311
Lines 304973 304973
Branches 44229 44229
============================================
- Hits 221045 221011 -34
- Misses 65830 65893 +63
+ Partials 18098 18069 -29 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@dependabot recreate |
Bumps [org.jruby.joni:joni](https://github.com/jruby/joni) from 2.2.3 to 2.2.5. - [Commits](jruby/joni@joni-2.2.3...joni-2.2.5) --- updated-dependencies: - dependency-name: org.jruby.joni:joni dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
a40ff00 to
5cd3294
Compare
Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: dependabot[bot] <support@github.com>
|
❌ Gradle check result for a9b7f0d: 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 a9b7f0d: UNSTABLE
Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure. |
|
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-17608-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 dcad6b8ff5e2f356d71019810ce7ced3212f8769
# Push it to GitHub
git push --set-upstream origin backport/backport-17608-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 |
…h-project#17608) * Bump org.jruby.joni:joni from 2.2.3 to 2.2.5 in /libs/grok Bumps [org.jruby.joni:joni](https://github.com/jruby/joni) from 2.2.3 to 2.2.5. - [Commits](jruby/joni@joni-2.2.3...joni-2.2.5) --- updated-dependencies: - dependency-name: org.jruby.joni:joni dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> * Updating SHAs Signed-off-by: dependabot[bot] <support@github.com> * Update changelog Signed-off-by: dependabot[bot] <support@github.com> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Signed-off-by: Vinay Krishna Pudyodu <vinkrish.neo@gmail.com>
Bumps org.jruby.joni:joni from 2.2.3 to 2.2.5.
Commits
a14bf33[maven-release-plugin] prepare release joni-2.2.5a7ec7dd[maven-release-plugin] prepare for next development iteration8038338[maven-release-plugin] prepare release joni-2.2.49102f6dUpdate to latest jcodingse3c4e03Restructure and rename to match Onigmode23ab0Merge pull request #85 from sebthom/case-folding64eb19f[maven-release-plugin] prepare for next development iterationafd50a8fix: char class casefold for certain charsDependabot 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)