[skip-ci] Update actions/upload-artifact action to v4

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/upload-artifact	action	major	v3 -> v4

---

Release Notes

actions/upload-artifact (actions/upload-artifact)

v4

Compare Source

---

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 is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[openshift-ci]

Hi @renovate[bot]. Thanks for your PR.

I'm waiting for a containers 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/test-infra repository.

[cevich]

Closing so the new platform-engineering renovate bot can take over.

[cgwalters]

@cevich Is the platform-engineering bot going to take over or not?

[cevich]

Thanks for asking, that's exactly what I was testing. Having the PR & branch owned by another bot seems to be breaking it's tiny little "brain" 😁 It appears renovate is simply not able to cope. There are no warnings or errors, but the new workflow is actually looking/checking for updates 🤔 I re-ran the workflow multiple times, w/ and w/o the "manage this PR" box checked. I'm at a loss here. But please poke me if you notice an update it should have opened but failed to do so.

/cc @lmilbaum

Ref: Dependency Dashboard

[cevich]

I think maybe what's hanging up the new bot isn't the existence of the old bot's PRs, it's the branches. I'm going to close these 3 old PRs and delete the old bot's branches. I'm betting that will prompt the new bot to open up fresh PRs. If it doesn't, then the bot is truly broken (it's not opening legit update PRs).