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

[AUTO] Increment version to 2.19.1. #17331

Merged
merged 1 commit into from
Feb 13, 2025
Merged

Conversation

opensearch-trigger-bot[bot]
Copy link
Contributor

I've noticed that a new tag 2.19.0 was pushed, and incremented the version from 2.19.0 to 2.19.1.

Copy link
Contributor

❌ Gradle check result for 8dc589f: 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: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Signed-off-by: Andriy Redko <drreta@gmail.com>
@reta reta force-pushed the create-pull-request/patch-2.19 branch from 8dc589f to ae5f3c9 Compare February 13, 2025 00:45
Copy link
Contributor

❕ Gradle check result for ae5f3c9: 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.

Copy link

codecov bot commented Feb 13, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.99%. Comparing base (b006c0f) to head (ae5f3c9).
Report is 6 commits behind head on 2.19.

Additional details and impacted files
@@             Coverage Diff              @@
##               2.19   #17331      +/-   ##
============================================
- Coverage     72.00%   71.99%   -0.02%     
- Complexity    65963    65988      +25     
============================================
  Files          5341     5341              
  Lines        307158   307143      -15     
  Branches      44824    44824              
============================================
- Hits         221184   221139      -45     
- Misses        67498    67562      +64     
+ Partials      18476    18442      -34     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@reta reta merged commit 6e7f0c1 into 2.19 Feb 13, 2025
45 checks passed
@reta reta added the backport 2.x Backport to 2.x branch label Feb 13, 2025
@opensearch-trigger-bot
Copy link
Contributor Author

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-17331-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 6e7f0c1379a6f38a61d5d6c98e205ee5b0ceaaaa
# Push it to GitHub
git push --set-upstream origin backport/backport-17331-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-17331-to-2.x.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autocut backport 2.x Backport to 2.x branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants