Bump github.com/tektoncd/chains from 0.16.1-0.20230519214917-07aacf584d01 to 0.17.0

[dependabot]

Bumps github.com/tektoncd/chains from 0.16.1-0.20230519214917-07aacf584d01 to 0.17.0.

Changelog

Sourced from github.com/tektoncd/chains's changelog.

Tekton Chains Releases

Release Frequency

Tekton Chains follows the Tekton community [release policy][release-policy] as follows:

• Versions are numbered according to semantic versioning: vX.Y.Z
• At a minimum four LTS release are produced. Additional releases are produced based on availability of new features to be released
• Four releases a year are chosen for long term support (LTS). All remaining releases are supported for approximately 1 month.
  • The first Tekton Chains LTS release will be v0.13.0 in October 2022

Tekton Chains produces nightly builds, publicly available on gcr.io/tekton-nightly.

Transition Process

Before release v0.13 Tekton Chains has worked on the basis of an undocumented support period, providing patch releases when needed. While transitioning to the new support model, v0.11 and v0.12 will be supported for four months from the initial publishing date.

Release Process

Tekton Chains releases are made of YAML manifests and container images. Manifests are published to cloud object-storage as well as [GitHub][tekton-chains-releases]. Container images are signed by [Sigstore][sigstore] via [Tekton Chains][tekton-chains]; signatures can be verified through the [public key][chains-public-key] hosted by the Tekton Chains project.

Further documentation available:

• The Tekton Chains [release process][tekton-releases-docs]
• [Installing Tekton][tekton-installation]
• Standard for [release notes][release-notes-standards]

Backwards Incompatible Changes

In general we aim for new features to be added in a backwards compatible way, but sometimes we will need to make breaking changes. This policy outlines how we will make and communicate these.

NOTE: Tekton Chains is working towards a formal beta release. Until then, all features are technically considered alpha (though we continue to do our best to retain backwards compatibility).

... (truncated)

Commits

• See full diff 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 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

[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

[vinamra28]

/lgtm