For each image in the attestation, match it to the release file
for image in $REKOR_ATTESTATION_IMAGES; do
printf $image; grep -q $image release.yaml && echo " ===> ok" || echo " ===> no match";
done
Upgrade Notices
Tekton Pipeline v0.41.0 requires Kubernetes version 1.23 or greater.
Release EOL: Oct 30th, 2023.
Actions Required
To allow PodSecurityAdmission to take effect, please set PodSecurity flag as Beta in kubernetes 1.23-1.24. See kubernetes feature gates for more information. (#5652)
Tekton Pipelines follows the Tekton community [release policy][release-policy]
as follows:
Versions are numbered according to semantic versioning: vX.Y.Z
A new release is produced on a monthly basis
Four releases a year are chosen for long term support (LTS).
All remaining releases are supported for approximately 1 month (until the next
release is produced)
LTS releases take place in January, April, July and October every year
The first Tekton Pipelines LTS release will be v0.41.0 in October 2022
Releases happen towards the middle of the month, between the 13th and the
20th, depending on week-ends and readiness
Tekton Pipelines produces nightly builds, publicly available on
gcr.io/tekton-nightly.
Transition Process
Before release v0.41 Tekton Pipelines has worked on the basis of an undocumented
support period of four months, which will be maintained for the releases between
v0.37 and v0.40.
Release Process
Tekton Pipeline releases are made of YAML manifests and container images.
Manifests are published to cloud object-storage as well as
[GitHub][tekton-pipeline-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 Pipeline [release process][tekton-releases-docs]
[Installing Tekton][tekton-installation]
Standard for [release notes][release-notes-standards]
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)
Bumps github.com/tektoncd/pipeline from 0.40.2 to 0.41.0.
Release notes
Sourced from github.com/tektoncd/pipeline's releases.
... (truncated)
Changelog
Sourced from github.com/tektoncd/pipeline's changelog.
... (truncated)
Commits
e38d112
Bump HorizontalPodAutoscaler apiVersion to v2b7d8693
[TEP-0089] Modify entrypoint to sign the results.1b941d3
[TEP-0115] Support Artifact Hub in Hub Resolverc172f5c
Add Beta feature gate for projected workspacedb4c05c
fix tekton documentation contributor`s guide linkd4c2f75
Bump github.com/sigstore/sigstore from 1.4.4 to 1.4.5eaca696
Bump github.com/stretchr/testify from 1.8.0 to 1.8.1817d043
Bump github.com/google/go-containerregistry from 0.11.0 to 0.12.06bc53ca
Bump github.com/containerd/containerd from 1.6.8 to 1.6.9867fe2d
Remove PipelineRun cancelation of Runs when Pipeline Task timeout is reachedDependabot 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)