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

fix(deps): update junit5 monorepo to v5.11.2 #363

Merged
merged 1 commit into from
Oct 17, 2024

Conversation

mend-for-github-com[bot]
Copy link
Contributor

@mend-for-github-com mend-for-github-com bot commented Jul 25, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
org.junit.jupiter:junit-jupiter-engine (source) 5.10.2 -> 5.11.2 age adoption passing confidence
org.junit.jupiter:junit-jupiter-api (source) 5.10.2 -> 5.11.2 age adoption passing confidence

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

@mend-for-github-com mend-for-github-com bot changed the title fix(deps): update junit5 monorepo to v5.10.3 fix(deps): update junit5 monorepo to v5.11.0 Aug 15, 2024
@mend-for-github-com mend-for-github-com bot force-pushed the whitesource-remediate/junit5-monorepo branch from c419e95 to 825d6ff Compare August 15, 2024 04:02
@mend-for-github-com mend-for-github-com bot force-pushed the whitesource-remediate/junit5-monorepo branch 2 times, most recently from 97048f7 to 6393456 Compare August 29, 2024 05:37
@mend-for-github-com mend-for-github-com bot force-pushed the whitesource-remediate/junit5-monorepo branch from 6393456 to 0cb6dda Compare September 26, 2024 03:11
@mend-for-github-com mend-for-github-com bot changed the title fix(deps): update junit5 monorepo to v5.11.0 fix(deps): update junit5 monorepo to v5.11.1 Sep 26, 2024
@mend-for-github-com mend-for-github-com bot changed the title fix(deps): update junit5 monorepo to v5.11.1 fix(deps): update junit5 monorepo to v5.11.2 Oct 5, 2024
@mend-for-github-com mend-for-github-com bot force-pushed the whitesource-remediate/junit5-monorepo branch from 0cb6dda to 8af0239 Compare October 5, 2024 02:59
@mend-for-github-com mend-for-github-com bot force-pushed the whitesource-remediate/junit5-monorepo branch from 8af0239 to 651861b Compare October 14, 2024 07:28
Signed-off-by: mend-for-github-com[bot] <mend-for-github-com[bot]@users.noreply.github.com>
@zane-neo zane-neo force-pushed the whitesource-remediate/junit5-monorepo branch from 651861b to 815e3f7 Compare October 16, 2024 07:15
@zane-neo zane-neo merged commit 12e5221 into main Oct 17, 2024
7 of 8 checks passed
@opensearch-trigger-bot
Copy link
Contributor

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:

# 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/skills/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/skills/backport-2.x
# Create a new branch
git switch --create backport/backport-363-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 12e5221e50dfcb1cfe0f8fbb68e220903f2eff61
# Push it to GitHub
git push --set-upstream origin backport/backport-363-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/skills/backport-2.x

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

@mend-for-github-com mend-for-github-com bot deleted the whitesource-remediate/junit5-monorepo branch October 17, 2024 05:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant