fix dependabot config

[dprotaso]

Fixing the config after merging - #15475

[dprotaso]

/assign @skonto

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.55%. Comparing base (df03027) to head (aab9fd1).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #15668      +/-   ##
==========================================
+ Coverage   83.51%   83.55%   +0.04%     
==========================================
  Files         219      219              
  Lines       17427    17427              
==========================================
+ Hits        14554    14562       +8     
+ Misses       2502     2494       -8     
  Partials      371      371              

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

[dprotaso]

/retest

[skonto]

nit: Although both are accepted by yaml, probably adding space for array items is mor ereadable, also as in the example here.

[skonto]

/lgtm
/approve

[knative-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dprotaso, skonto

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:

• OWNERS [dprotaso,skonto]

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

[skonto]

/override ?

[knative-prow]

@skonto: skonto unauthorized: /override is restricted to Repo administrators.

Details

In response to this:

/override ?

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.

[skonto]

Error: Unable to download artifact(s): Artifact not found for name: artifacts
        Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact.
        For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md

@dprotaso could you override the failing test (I have no rights) or do you know why it didnt keep the artifact around?

[dprotaso]

@dprotaso could you override the failing test (I have no rights) or do you know why it didnt keep the artifact around?

It's a 'best' effort cache. We need to re-kick off the build step first

[dprotaso]

lol we hit a weird prow bug