Bump github.com/openshift-pipelines/pipelines-as-code from 0.20.0 to 0.21.0

[dependabot]

Bumps github.com/openshift-pipelines/pipelines-as-code from 0.20.0 to 0.21.0.

Release notes

Sourced from github.com/openshift-pipelines/pipelines-as-code's releases.

v0.21.0

Pipelines as Code version v0.21.0

OpenShift Pipelines as Code v0.21.0 has been released 🥳

Changes

• Support for dynamic value to incoming webhook

  • Now params can be passed as json in incoming webhook and can be used in repo CR to be passed to pipelineruns
  • Doc: https://main.pipelines-as-code.pages.dev/docs/guide/incoming_webhook/#passing-dynamic-parameter-value-to-incoming-webhook
  • PR #1404

• Refactor /ok-to-test behaviour on pushing commits to PR

  • Now jobs will be triggered if /ok-to-test has given on PR on new push events
  • If you want to disable retriggering jobs, you set remember-ok-to-test flag to false
  • Doc: https://main.pipelines-as-code.pages.dev/docs/install/settings/
  • PR #1364

• Add source_url information to standard parameters

  • It has the url of the source from where the event is coming
  • PR #1385

• Add support for tag push event on gitlab

  • PR #1403

• Now display name of task will be used to show status on checks page

  • PR #1413

• tkn bootstrap command now supports --github-hostname flag and --github-api-url flag has been deprecated

  • PR #1420

Fixes

• PAC now supports paginated api calls to GitHub

  • PR #1379

• Fix branch name with slash should be parsed while fetching remote resources

  • PR #1396

• Fix gitea tag push broken

  • PR #1401

• Optimize fetching remote tasks for pipelines, now remote task are fetched only for matched pipelineruns

  • PR #1371

• Fix verification of multiple PRs with generateName or duplicate generateName in .tekton directory

  • PR #1415

• Now on webhook event, only pipelinerun with webhookevent will be triggered in place of all

... (truncated)

Commits

• 0506de5 Fix flaky unit tests
• b63b9be Fix syntax error in release pipeline
• 8f990bf Fix logs spamming regarding catalogs
• c6ceb71 Fix status issue for GitLab Merge Requests
• 7fb5e22 Fix multiple creation of Pipelinerun for incoming event
• e2fd1b9 Add GitHub hostname flag
• 8048063 Fix verification of duplicate name and generateName in .tekton directory
• 86b8697 GH App, make sure token generated works for itself
• 6dda846 Let incoming webhook define or redefine parameters
• 100c616 Bump docker/build-push-action from 4.1.1 to 4.2.1
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[tekton-robot]

Hi @dependabot[bot]. 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.

[piyush-garg]

/approve
/lgtm

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: piyush-garg

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 [piyush-garg]

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