Description of problem:

After upgrading from 1.10 to 1.11, PipelineRuns with a specification like using the old form of bundle resolver started getting their PipelineRuns converted to an incorrect kind.  For example:

apiVersion: tekton.dev/v1beta1
kind: PipelineRun
metadata:
  name: release-service-pull-request
  annotations:
    pipelinesascode.tekton.dev/on-event: "[pull_request]"
    pipelinesascode.tekton.dev/on-target-branch: "[main]"
    pipelinesascode.tekton.dev/max-keep-runs: "5"
spec:
  params: 
    - name: git-url
      value: "{{ repo_url }}"
    - name: revision
      value: "{{ revision }}"
    - name: output-image
      value: 'quay.io/redhat-appstudio/pull-request-builds:release-service-{{ revision }}'
  pipelineRef:
    name: docker-build
    bundle: quay.io/redhat-appstudio-tekton-catalog/pipeline-core-services-docker-build:latest
  workspaces:
    - name: workspace
      volumeClaimTemplate:

After bundle resolution though the PipelineRun incorrectly was converted to

 
pipelineRef:
params:

• name: bundle
  value: >-
  quay.io/redhat-appstudio-tekton-catalog/pipeline-core-services-docker-build:latest
• name: name
  value: docker-build
• name: kind
  value: Task
  resolver: bundles
   

where as when we were on 1.1 it got converted to

 
pipelineRef:
params:

• name: bundle
  value: >-
  quay.io/redhat-appstudio-tekton-catalog/pipeline-core-services-docker-build:latest
• name: name
  value: docker-build
• name: kind
  value: Pipeline
  resolver: bundles
   

Workaround

We have had to switch PipelineRuns of this sort to use the new bundle resolution directly, where we can force the kind to be correct. 

See https://github.com/redhat-appstudio/release-service/pull/231/files for an example of such a conversion

Prerequisites (if any, like setup, operators/versions):

Steps to Reproduce

 # <steps>

Actual results:

Expected results:

Reproducibility (Always/Intermittent/Only Once):

Acceptance criteria: 

Definition of Done:

Build Details:

Additional info (Such as Logs, Screenshots, etc):

 *