Update github.com/go-git/go-git/v5 from v5.12.0 to v5.13.1

[SaschaSchwarze0]

Changes

Not sure why dependabot has not opened a pull request. govulncheck clearly reports this repository being affected by the vulnerability.

Fixes CVE-2025-21613
Fixes CVE-2025-21614

/kind security

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
• Has Tests included if any functionality added or changed
• pre-commit Passed
• Follows the commit message standard
• Meets the Tekton contributor standards (including functionality, content, code)
• Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
• Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
• Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

[tekton-robot]

Hi @SaschaSchwarze0. Thanks for your PR.

I'm waiting for a tektoncd 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.

[SaschaSchwarze0]

/retest
/kind security

[tekton-robot]

@SaschaSchwarze0: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest
/kind security

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.

[vdemeester]

/ok-to-test

[SaschaSchwarze0]

@vdemeester thanks for ok-to-test. Can you help me with two things:

1. I initially marked it with kind/cleanup until I noticed there is a kind/security. Now the PR has two labels and the kind check fails complaining on this. But I do not know how to remove kind/cleanup. Can you let me know the command or simply remove the label? Ty.
2. The e2e failure. Failing is "TestExamples/v1/taskruns/entrypoint-resolution" and I see failed to create task run pod "entrypoint-resolution": translating TaskSpec to Pod: GET https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/b1/b1d9df8ab81559494794e522b380878cf9ba82d4c1fb67293bcf931c3aa69ae4/data?verify=REDACTED: unexpected status code 403 Forbidden: {"status":403,"message":"Error: invalid URL signature"}. Maybe invalid TaskSpec which is maybe related. I'll try a /retest, but if you have other insights, let me know.

[SaschaSchwarze0]

/retest

[vdemeester]

@SaschaSchwarze0 arf, it needs a rebase now.

[SaschaSchwarze0]

@vdemeester done

[vdemeester]

ah go-billy got released 👼🏼
cc @afrittoli @waveywaves

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

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:

• OWNERS [vdemeester]

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

[afrittoli]

/lgtm