Updated yq command to get the tag properly on release-v1.9

[Cali0707]

This PR cherry picks a fix to the yq command in the generate-release script onto the release-v1.9 branch

[Cali0707]

/cc @pierDipi @creydr

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Cali0707
Once this PR has been reviewed and has the lgtm label, please assign lberk for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[Cali0707]

/retest-required

[creydr]

@Cali0707 where did you get this error? IIRC we are (/were?!?) using yq 3 in CI (Jenkins).

[Cali0707]

@Cali0707 where did you get this error? IIRC we are (/were?!?) using yq 3 in CI (Jenkins).

I got this error when I was running make generate-release locally to set up the release-v1.10 branch. I didn't know this also runs in CI, but it makes sense that it does.

@creydr if we are using yq 3 in CI, do you think that we should revert this change on the release-v1.10 branch and document somewhere that you need yq 3 locally to run this?

[creydr]

@pierDipi regarding the discussions from e05f546#r120280389: I thought we are on yq 3 in Jenkins 🤔

[pierDipi]

@pierDipi regarding the discussions from e05f546#r120280389: I thought we are on yq 3 in Jenkins thinking

Yes, I thought it was an existing problem and not that Calum is on yq v4

[pierDipi]

Therefore, we need to stick with yq v3, so we need to revert/change accordingly

[pierDipi]

@Cali0707 I guess the only action item left here is to revert e05f546, right?

[pierDipi]

I did it in #760