CI(deps): Update actions/checkout digest to b4ffde6

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/checkout	action	digest	8ade135 -> b4ffde6

---

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 becomes conflicted, 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.

[wenzeslaus]

b4ffde6 is actions/checkout latest release v4.1.1.

I wonder how to review these...one hash changing to another.

[echoix]

b4ffde6 is actions/checkout latest release v4.1.1.

I wonder how to review these...one hash changing to another.

@wenzeslaus if we add more granularity to the comment, like # v4.1.1 I think renovate will keep the comment updated. I'm not able to refind the source for that, but renovate tried to keep the same granularity for Docker images, for example.

[neteler]

re backporting: I tried to cherry-pick 7c64bcf but it failed with a lot of merge conflicts.

[landam]

Confirmed, there are plenty of conficts. Let's avoid backporting. @wenzeslaus Do you agree?

[wenzeslaus]

I guess you would have to use Meld or similar procedure to get the changes there unless you follow (backport) every preceding change from main. I don't know why I added the backport label in November. Generally, I don't see how the automatic "renovations" would work for release branches unless 1) they are automated and 2) we are ready to make changes to the other source code if the need arises. Neither is fulfilled at this point. Maybe we were backporting these changes in the past...I do remember we had to backport things in CI when CI was broken, but that does not seem to be the case here. We also just deleted the problematic workflows on release branches in the past. Perhaps, it is on case-by-case basis.