Skip to content

[release-4.18] OCPEDGE-1117: Update dependencies#806

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.18from
suleymanakbas91:upd-dep-4.18
Dec 10, 2024
Merged

[release-4.18] OCPEDGE-1117: Update dependencies#806
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.18from
suleymanakbas91:upd-dep-4.18

Conversation

@suleymanakbas91
Copy link
Copy Markdown
Contributor

No description provided.

Signed-off-by: Suleyman Akbas <sakbas@redhat.com>
@suleymanakbas91 suleymanakbas91 changed the title chore: update dependencies [release-4.18] OCPEDGE-1117: Update dependencies Dec 10, 2024
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Dec 10, 2024

@suleymanakbas91: This pull request references OCPEDGE-1117 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 10, 2024
@openshift-ci openshift-ci bot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Dec 10, 2024
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Dec 10, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: suleymanakbas91

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 10, 2024
@codecov-commenter
Copy link
Copy Markdown

codecov-commenter commented Dec 10, 2024

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.53%. Comparing base (4bf6c07) to head (99b86c5).
⚠️ Report is 139 commits behind head on release-4.18.

Additional details and impacted files

Impacted file tree graph

@@              Coverage Diff              @@
##           release-4.18     #806   +/-   ##
=============================================
  Coverage         69.53%   69.53%           
=============================================
  Files                50       50           
  Lines              3453     3453           
=============================================
  Hits               2401     2401           
  Misses              866      866           
  Partials            186      186           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@qJkee
Copy link
Copy Markdown
Contributor

qJkee commented Dec 10, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 10, 2024
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Dec 10, 2024

@suleymanakbas91: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit 165ed25 into openshift:release-4.18 Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants