add function to set latest semver to latest

[krsna-m]

Changes

• 🎁 Add function to release.sh to set highest semver as latest in github

Fixes knative/infra#201

[krsna-m]

This assumes that jq is available.

[dprotaso]

/assign @cardil @upodroid

[dprotaso]

/approve

will let others add lgtm

[dprotaso]

/cherry-pick release-1.12

[knative-prow-robot]

@dprotaso: once the present PR merges, I will cherry-pick it on top of release-1.12 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.12

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.

[dprotaso]

/cherry-pick release-1.11

[knative-prow-robot]

@dprotaso: once the present PR merges, I will cherry-pick it on top of release-1.11 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.11

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.

[krsna-m]

https://github.com/knative/infra/blob/main/images/prow-tests/Dockerfile#L65

[cardil]

/lgtm

Those conditional failures could be dropped, as the set -e should enforce the script will fail at first error, but I can accept this as a defensive touch. They will ensure this works as intended even if this is executed with set +e (unfortunately it might be)

Thanks @kvmware for fixing this!

[knative-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cardil, dprotaso, kvmware

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 [cardil,dprotaso,kvmware]

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

[knative-prow-robot]

@dprotaso: new pull request created: #340

In response to this:

/cherry-pick release-1.11

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.

[knative-prow-robot]

@dprotaso: new pull request created: #341

In response to this:

/cherry-pick release-1.12

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.