chore(deps): upgrade to version 1.23.6

[jenkins-x-bot]

from: https://github.com/jenkins-x/lighthouse.git

---

Upgrade of API version for Tekton Pipelines to v1

With this upgrade the API version of Tekton Pipeline resources (like pipeline runs) are updated from tekton.dev/v1beta1
to tekton.dev/v1.

If the Kubernetes cluster you now upgrade does not have Tekton Pipelines installed this will naturally not have any
effect. A typical case if this is a remote cluster.

Potential problems with conversion

In the Jenkins X cluster upgrade process any changes to custom resource definitions are applied first. In this case
this will trigger the Kubernetes cluster to ask tekton-pipelines-webhook to convert existing tekton pipeline
resources in the cluster. At this time the tekton-pipelines-webhook deployment is an old version which include bugs
that can cause old pipeline runs to start executing again. This can cause confusion, especially if a release pipeline
for an old version of an application is run again.

The simplest way to avoid this is to manually delete existing pipeline runs before doing this upgrade. This can be
done by running

kubectl delete piplinerun --all -namespace jx

Existing pipelines in application repositories

So far the supported API version of the pipelines in the .ligthouse directory of your application respositories have
been tekton.dev/v1beta1. From now on tekton.dev/v1 is also supported. Any pipelines with version tekton.dev/v1beta1
will be automatically converted to tekton.dev/v1 when read by lighthouse. After the Tekton Pipelines project remove
support for this conversion it will be removed from lighthouse as well. But before that tools to convert the
pipelines in .lighthouse will be made available.

---

jenkins-x/lighthouse

Changes in version 1.23.5

Tests

• make tests pass about activityRecord (JordanGoasdoue)

Chores

• upgrade tektoncd to latest 0.69.1 (JordanGoasdoue)
• tests: fix remaining tests (JordanGoasdoue)
• periodic: make test pass with new taskruntemplate (JordanGoasdoue)
• breakpoint: make test pass with updated struct (JordanGoasdoue)
• normalize actual and expected data to avoid diff when indent (JordanGoasdoue)
• convert from v1beta1 to v1 pipeline/task loaded from ref (JordanGoasdoue)
• support v1 and v1beta1 (JordanGoasdoue)
• use lighthousev1alpha1 (JordanGoasdoue)
• pass tektonClient from param in ConvertPipelineRun (JordanGoasdoue)
• add taskruns get permission (JordanGoasdoue)
• add scheme on Manager config (JordanGoasdoue)
• remove deprecated PipelineResources (JordanGoasdoue)
• get taskruns from clients instead of pr.Status.TaskRuns (JordanGoasdoue)
• replace ArrayOrString with ParamValue (JordanGoasdoue)
• use Timeouts.Pipeline instead of Timeout (JordanGoasdoue)
• manually edit zz_generated because controller-gen fails (JordanGoasdoue)
• regenerate crds with make crd-manifests (JordanGoasdoue)
• use tektoncd/pipeline/pkg/apis/pipeline/v1 (JordanGoasdoue)
• use pipelinev1beta1 everywhere (JordanGoasdoue)
• upgrade tekton pipeline to 0.65.3 with dependencies upgrades (JordanGoasdoue)

Other Changes

These commits did not use Conventional Commits formatted messages:

• chore(load_pipelinerun): convert the expected to v1 (JordanGoasdoue)
• chore(load_pipelinerun): show how to validate one uses test (JordanGoasdoue)

[msvticket]

/hold

[jenkins-x-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JordanGoasdoue

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

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

[jenkins-x-bot]

@jenkins-x-bot: The following test failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
gsm	32b2e8c	link	/test gsm

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 jenkins-x/lighthouse repository. I understand the commands that are listed here.