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 swaggerversion to v2.1.25 #1010

Merged
merged 1 commit into from
Jan 22, 2025

Conversation

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

@mend-for-github-com mend-for-github-com bot commented Jan 18, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
io.swagger.parser.v3:swagger-parser-v3 (source) 2.1.24 -> 2.1.25 age adoption passing confidence
io.swagger.parser.v3:swagger-parser (source) 2.1.24 -> 2.1.25 age adoption passing confidence
io.swagger.parser.v3:swagger-parser-core (source) 2.1.24 -> 2.1.25 age adoption passing confidence

Release Notes

swagger-api/swagger-parser (io.swagger.parser.v3:swagger-parser-v3)

v2.1.25: Swagger-parser 2.1.25 released!

  • update dependencies (Jackson to 2.18.2, fix quotes in tests) (#​2153)

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

Copy link

codecov bot commented Jan 18, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 76.40%. Comparing base (bca570d) to head (c744114).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##               main    #1010   +/-   ##
=========================================
  Coverage     76.40%   76.40%           
  Complexity     1010     1010           
=========================================
  Files           100      100           
  Lines          4879     4879           
  Branches        455      455           
=========================================
  Hits           3728     3728           
  Misses          954      954           
  Partials        197      197           

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

Signed-off-by: mend-for-github-com[bot] <mend-for-github-com[bot]@users.noreply.github.com>
@mend-for-github-com mend-for-github-com bot force-pushed the whitesource-remediate/swaggerversion branch from 90e2118 to c744114 Compare January 22, 2025 02:06
@amitgalitz amitgalitz merged commit 1b9e365 into main Jan 22, 2025
20 checks passed
@amitgalitz amitgalitz deleted the whitesource-remediate/swaggerversion branch January 22, 2025 20:38
@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/flow-framework/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/flow-framework/backport-2.x
# Create a new branch
git switch --create backport/backport-1010-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 1b9e365c44031c859f876ce0e6a0ef9872e710ee
# Push it to GitHub
git push --set-upstream origin backport/backport-1010-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/flow-framework/backport-2.x

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

@opensearch-trigger-bot opensearch-trigger-bot bot added the backport-failed Applied to PRs when the automatic backport fails label Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport 2.x backport PRs to 2.x branch backport-failed Applied to PRs when the automatic backport fails skip-changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants