8000 chore: Update components' versions to latest by github-actions[bot] · Pull Request #2827 · knative/func · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

chore: Update components' versions to latest #2827

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
May 7, 2025
Merged

chore: Update components' versions to latest #2827

merged 1 commit into from
May 7, 2025

Conversation

github-actions[bot]
Copy link
Contributor
@github-actions github-actions bot commented May 6, 2025

chore: Update components' versions to latest
You might need to close & open this PR so all tests can run
/assign @gauron99

8000 @knative-prow knative-prow bot assigned gauron99 May 6, 2025
@knative-prow knative-prow bot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels May 6, 2025
@knative-prow Knative Prow
Copy link
knative-prow bot commented May 6, 2025

Hi @github-actions[bot]. Thanks for your PR.

I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@knative-prow knative-prow bot requested review from dsimansk and jrangelramos May 6, 2025 16:07
@gauron99
Copy link
Contributor
gauron99 commented May 7, 2025

/lgtm

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label May 7, 2025
@gauron99 gauron99 closed this May 7, 2025
@knative-prow Knative Prow
Copy link
knative-prow bot commented May 7, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gauron99, github-actions[bot]

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

The pull request process is described here

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

@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 7, 2025
@gauron99 gauron99 reopened this May 7, 2025
@codecov Codecov
Copy link
codecov bot commented May 7, 2025 •
edited
Loading

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 48.42%. Comparing base (7467ce1) to head (75b6204).
Report is 1 commits behind head on main.

❗ There is a different number of reports uploaded between BASE (7467ce1) and HEAD (75b6204). Click for more details.

HEAD has 6 uploads less than BASE
Flag BASE (7467ce1) HEAD (75b6204)
unit-tests-macos-latest 1 0
unit-tests-ubuntu-latest 1 0
unit-tests-windows-latest 1 0
integration-tests 1 0
e2e-test-oncluster 1 0
e2e-test 1 0
Additional details and impacted files 
@@             Coverage Diff             @@
##             main    #2827       +/-   ##
===========================================
- Coverage   61.60%   48.42%   -13.18%     
===========================================
  Files         131      129        -2     
  Lines       15796    15787        -9     
===========================================
- Hits         9731     7645     -2086     
- Misses       5154     7455     +2301     
+ Partials      911      687      -224
Flag Coverage Δ
e2e-test ?
e2e-test-oncluster ?
integration-tests ?
unit-tests-macos-latest ?
unit-tests-ubuntu-latest ?
unit-tests-windows-latest ?

Flags with carried forward coverage won't be shown. Click here to find out more.

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@gauron99
Copy link
Contributor
gauron99 commented May 7, 2025

/test unit-tests_func_main

@gauron99
Copy link
Contributor
gauron99 commented May 7, 2025

/override codecov/project

@knative-prow Knative Prow
Copy link
knative-prow bot commented May 7, 2025

@gauron99: Overrode contexts on behalf of gauron99: codecov/project

In response to this:

/override codecov/project

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.

@knative-prow knative-prow bot merged commit bcd141d into main May 7, 2025
36 of 37 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@gauron99 gauron99 gauron99 approved these changes

@dsimansk dsimansk Awaiting requested review from dsimansk

@jrangelramos jrangelramos Awaiting requested review from jrangelramos

Assignees

@gauron99 gauron99

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@gauron99 @knative-automation
0