Bump tkn-results to use latest version of results

[avinal]

Changes

• go1.17 support has already ended, bump tkn-results to 1.19
• replace deprecated methods
• bump results version in tkn-results

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you review them:

• Has Docs included if any changes are user facing
• Has Tests included if any functionality added or changed
• Tested your changes locally (if this is a code change)
• Follows the commit message standard
• Meets the Tekton contributor standards (including functionality, content, code)
• Has a kind label. You can add 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)
• Release notes contain the string "action required" if the change requires additional action from users switching to the new release

Release Notes

- tkn-results bumped to use v0.7.0 of results
- tkn-results Go version bumped to go1.19

[tekton-robot]

Hi @avinal. 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.

[avinal]

I have a feeling that it would be better to break it into two commits or even two PRs. Please let me know.

[adambkaplan]

@avinal two commits makes the most sense:

• First commit - update to go 1.19, run go mod tidy && go mod vendor
• Second commit - refactors related to code updates.

[adambkaplan]

/ok-to-test

[avinal]

I did not run go mod vendor for tkn-results. It is currently not in the main tree and many dependencies will be duplicated. Filed #551 for moving in tree.

[khrm]

We need to merge older prs of cli.

[avinal]

/kind misc

[vdemeester]

@avinal needs a small rebase

[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

[avinal]

Hey Vincent, we are holding this PR until other CLI prs are merged. I will rebase as soon they are meregd.

[avinal]

I have tested the bump with the latest changes in tkn-results, everything is working as expected. PTAL

[khrm]

/lgtm