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

[main] Upgrade to latest dependencies #2810

Merged

Conversation

knative-automation
Copy link
Contributor

Cron -knative-prow-robot

/cc knative/serving-writers knative/eventing-writers
/assign knative/serving-writers knative/eventing-writers

Produced by: knative-extensions/knobots/actions/update-deps

@knative-prow knative-prow bot requested review from a team September 7, 2023 01:30
@knative-prow knative-prow bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Sep 7, 2023
@codecov
Copy link

codecov bot commented Sep 7, 2023

Codecov Report

Patch coverage has no change and project coverage change: -0.06% ⚠️

Comparison is base (9780686) 81.84% compared to head (526dfb4) 81.78%.

❗ Current head 526dfb4 differs from pull request most recent head 5e2a8f1. Consider uploading reports for the commit 5e2a8f1 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2810      +/-   ##
==========================================
- Coverage   81.84%   81.78%   -0.06%     
==========================================
  Files         167      167              
  Lines       10217    10217              
==========================================
- Hits         8362     8356       -6     
- Misses       1610     1614       +4     
- Partials      245      247       +2     

see 2 files with indirect coverage changes

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

eval "$orig_pipefail_opt"

if ! [ -d vendor ]; then
if ! [[ "${FORCE_VENDOR:-false}" == "true" ]] && ! [ -d vendor ]; then
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cardil rather than an env var why don't we just infer repos want to use vendor if they already have a vendor folder?

This would mean things should just work as expected until repos remove vendor themselves?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another question are we skipping update_licenses call if there is no vendor? If so why?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It already works like you're suggesting.

If you don't have a vendor dir, it will not be created for you. If you have one, it will be updated as it was before. You could set this environment flag to force the creation of vendor dir, which I imagine being handy for Knative's vendors.

The license saving is removed here, yes, if there's no vendor dir. But, remember we still do the license scan during the --build-test run. I believe that satisfies the CNCF license guidelines AFAIK.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The license saving is removed here, yes, if there's no vendor dir. But, remember we still do the license scan during the --build-test run. I believe that satisfies the CNCF license guidelines AFAIK.

We ship licenses in our containers - we shouldn't stop doing that unless we get clear guidance from the CNCF that we no longer need to do that

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So I would expect we still run even if we don't have a vendor folder

update_licenses third_party/VENDOR-LICENSE "./..."

@knative-automation knative-automation force-pushed the auto-updates/update-deps-main branch 2 times, most recently from 526dfb4 to 88e6809 Compare September 12, 2023 13:12
bumping knative.dev/hack 9cc05a3...0bb79ff:
  > 0bb79ff Update community files (# 314)
  > 3af329f Update community files (# 313)
  > 760813a Allow to not vendor the dependencies (# 311)
  > f63d16e 🎁 Source embedded hack scripts (# 222)

Signed-off-by: Knative Automation <automation@knative.team>
@dprotaso
Copy link
Member

/hold

/assign @cardil to answer questions

@knative-prow knative-prow bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 14, 2023
@dprotaso
Copy link
Member

Unholding - created a separate issue knative/hack#315
/unhold
/lgtm
/apporve

@knative-prow knative-prow bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 18, 2023
@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Sep 18, 2023
@dprotaso
Copy link
Member

/approve

@knative-prow
Copy link

knative-prow bot commented Sep 18, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dprotaso, knative-automation

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 Sep 18, 2023
@knative-prow knative-prow bot merged commit 5e88665 into knative:main Sep 18, 2023
36 checks passed
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. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants