Bump go-billy to latest main to fix a git resolver issue

[vdemeester]

Changes

Before the update of that dependency, a git repository that contains a
symlink, that points outside of the repository, will fail. This means
even though the definition (pipeline, task, …) that we are trying to
fetch exists, the resolution will fail.

With this bump, this is now fixed.

Signed-off-by: Vincent Demeester [email protected]

/kind bug

Closes #7561

It probably needs a non-regression test, but I am a bit unsure what
repository to use for this. @afrittoli what do you think ? We could
create our own, or create one dynamically during the tests, …

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

The git resolver will be able to resolve a resource even if there is an invalid symlink is present in the repository fetched (for anonymous fetching).

[vdemeester]

/hold

Waiting to see if we can get a go-billy release out before merging this 👼🏼 @pjbgf

[pjbgf]

@vdemeester as per thread on the issue:

unfortunately I don't have permission to cut releases within go-git. I am hoping we will cut new releases for both go-billy and go-git before the end of the year but that will depend on other maintainer's availability.

Based on the above, my current advice is to use the pseudo versions from master, which at present are more reliable and stable than the last cut releases.

[vdemeester]

/hold cancel

[afrittoli]

/approve

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: afrittoli

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 [afrittoli]

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

[vdemeester]

cc @chitrangpatel

[tekton-robot]

@vdemeester: PR needs rebase.

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.