fix the latest_version function

[dprotaso]

it's aware of the new tag format and the manual jump from
v0.26 => v1.0

note: lates_version returns the tag which may now include prefixes

[knative-prow-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dprotaso

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

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

[dprotaso]

/hold - there's a bug

[dprotaso]

/hold cancel

[dprotaso]

/hold I'll verify in serving

[dprotaso]

/hold cancel

[dprotaso]

verified the behaviour

• serving, main => picked knative-v1.0.0
• serving, release-1.0 => picked v0.26.0
• serving, release-0.26 => picked v0.25.1

[benmoss]

/lgtm

[tzununbekov]

I was wondering if using Github's latest endpoint could help save some lines:

function latest_version() {
  local origin=$(git config --get remote.origin.url | sed 's/.*:\(.*\)\..*$/\1/')
  curl -I -s https://github.com/${origin}/releases/latest | grep "location:" | awk -F/ '{print $NF}' | sed 's/ //g'
}

[dprotaso]

looking https://docs.github.com/en/rest/reference/repos#get-the-latest-release - it's is sorted by created_at time

but we need to sort by our semver versions since we'll produce newer patch releases for older branches

[dprotaso]

/cherry-pick release-1.0

[knative-prow-robot]

@dprotaso: new pull request created: #106

In response to this:

/cherry-pick release-1.0

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-0.26
/cherry-pick release-0.25
/cherry-pick release-0.24

[knative-prow-robot]

@dprotaso: #101 failed to apply on top of branch "release-0.26":

Applying: fix the latest_version function
Using index info to reconstruct a base tree...
M	library.sh
M	release.sh
Falling back to patching base and 3-way merge...
Auto-merging release.sh
CONFLICT (content): Merge conflict in release.sh
Auto-merging library.sh
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 fix the latest_version function
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-0.26
/cherry-pick release-0.25
/cherry-pick release-0.24

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.