chore(deps): bump github.com/tektoncd/pipeline from 0.53.1 to 0.59.0 in /test/custom-task-ctrls/wait-task-beta
Bumps github.com/tektoncd/pipeline from 0.53.1 to 0.59.0.
Release notes
Sourced from github.com/tektoncd/pipeline's releases.
Tekton Pipeline release v0.59.0 "Scottish Fold Sox" LTS
🎉 Artifact Metadata, Improved StepActions and Improved Stability 🎉
-Docs @ v0.59.0 -Examples @ v0.59.0
Installation one-liner
kubectl apply -f https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.59.0/release.yamlAttestation
The Rekor UUID for this release is
24296fb24b8ad77afedce0421f9d0b300ed47db5907cad59970fed93f978290fd32680173c43e675Obtain the attestation:
REKOR_UUID=24296fb24b8ad77afedce0421f9d0b300ed47db5907cad59970fed93f978290fd32680173c43e675 rekor-cli get --uuid $REKOR_UUID --format json | jq -r .Attestation | jq .Verify that all container images in the attestation are in the release file:
RELEASE_FILE=https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.59.0/release.yaml REKOR_UUID=24296fb24b8ad77afedce0421f9d0b300ed47db5907cad59970fed93f978290fd32680173c43e675Obtains the list of images with sha from the attestation
REKOR_ATTESTATION_IMAGES=$(rekor-cli get --uuid "$REKOR_UUID" --format json | jq -r .Attestation | jq -r '.subject[]|.name + ":v0.59.0@sha256:" + .digest.sha256')
Download the release file
curl "$RELEASE_FILE" > release.yaml
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 v0.59 minimum Kubernetes version is 1.27.
Changes
Features
- :sparkles: Add a feature flag to disable inline spec (#7844)
Add a feature flag
disable-inline-specto disable embedded spec in Pipeline(PipelineSpec/TaskSpec), Taskrun(TaskSpec), and Pipelinerun. (PipelineSpec) By default, the inline specs will be enabled. Only if the flag is set to "pipeline", "pipelinerun" and "taskrun" or a combination like "pipeline,pipelinerun" would the inline spec be disabled for Pipeline, PipelineRun, or TaskRun.
... (truncated)
Changelog
Sourced from github.com/tektoncd/pipeline's changelog.
Tekton Pipeline Releases
Release Frequency
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]
Release
v0.58
- Latest Release: [v0.58.0][v0.58-0] (2024-03-20) ([docs][v0.58-0-docs], [examples][v0.58-0-examples])
- Initial Release: [v0.58.0][v0.58-0] (2024-03-20)
- End of Life: 2024-04-20
- Patch Releases: [v0.58.0][v0.58-0]
... (truncated)
Commits
34d8c0fchore(deps): bump go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptrace...e556bc7fix: resolve pod creation failure on retry when usingworkspace.\<name>.volumea494d6afix(taskrun): emit warning for missing secret in ServiceAccount instead of fa...fba68b7Fix shell for tag-images stepb712fc5chore(deps): bump go.opentelemetry.io/otel/sdk from 1.25.0 to 1.26.091bbee5fix: do not set default kind when taskRef resolver is present30e389bfix: ensure default type for params in remote tasks to prevent pipeline failuresfaccef8Fix the shell in crane imageb419b2cAdd a feature flag to disable inline spec356b30dchore(deps): bump actions/checkout from 4.1.2 to 4.1.3- 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
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.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign vdemeester after the PR has been reviewed.
You can assign the PR to them by writing /assign @vdemeester in a comment when ready.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/retest
@dependabot[bot]: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| pull-tekton-pipeline-integration-tests | 67c6385c631ff1776fcd1c4f007268c22bc59305 | link | true | /test pull-tekton-pipeline-integration-tests |
| pull-tekton-pipeline-beta-integration-tests | 67c6385c631ff1776fcd1c4f007268c22bc59305 | link | true | /test pull-tekton-pipeline-beta-integration-tests |
| pull-tekton-pipeline-alpha-integration-tests | 67c6385c631ff1776fcd1c4f007268c22bc59305 | link | true | /test pull-tekton-pipeline-alpha-integration-tests |
Full PR test history. Your PR dashboard.
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. I understand the commands that are listed here.
Superseded by #7979.