chore: bump component versions - #4075
Closed
tekton-robot wants to merge 185 commits into
Closed
Conversation
- dashboard: v0.68.0 → v0.69.0 - pipeline: v1.12.0 → v1.13.0 Signed-off-by: tekton-bot <tekton-bot@users.noreply.github.com>
.tekton/release.yaml and .tekton/release-patch.yaml explicitly set koExtraArgs="--preserve-import-paths", which overrides the pipeline default that was corrected in #3400. The flag makes ko push images to non-canonical long paths (ghcr.io/tektoncd/operator/github.com/tektoncd/ operator/cmd/...) which are created private by default, breaking the published release manifests (seen in v0.79.1 and again in v0.80.0). Setting koExtraArgs="" restores ko's default --base-import-paths hash-based names (operator-<md5>, webhook-<md5>, ...), matching the canonical, public image paths referenced by historical releases. Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
Set appVersion in the Helm release workflow to use the full tag (e.g. v0.80.0) instead of the stripped version (0.80.0), so image tags resolved from .Chart.AppVersion match the published images. Expose KUBERNETES_MIN_VERSION as kubernetesMinVersion in values.yaml defaulting to v1.34.0 (aligned with vendored knative/pkg). Inject it into all three containers (lifecycle, cluster-operations, webhook) via a shared helper. Also support additionalEnvs on the cluster-operations and webhook containers. Strip format: int32/int64 from Helm CRD templates in sync-helm-crds.sh to eliminate Kubernetes API server warnings on apply. Fixes #3482 #3483 Signed-off-by: Jawed khelil <jkhelil@redhat.com> Assisted-by: Claude Sonnet 4.6 (via Cursor) Co-authored-by: Cursor <cursoragent@cursor.com>
Replace cgr.dev/chainguard/static with the Tekton-maintained static base image built in tektoncd/plumbing. Supports all four target architectures (amd64, arm64, s390x, ppc64le) and is rebuilt daily. Related: tektoncd/pipeline#9557, tektoncd/plumbing#3434
Bumps [chainguard-dev/actions](https://github.com/chainguard-dev/actions) from 1.6.19 to 1.6.22. - [Release notes](https://github.com/chainguard-dev/actions/releases) - [Commits](chainguard-dev/actions@c69a264...3b7bbee) --- updated-dependencies: - dependency-name: chainguard-dev/actions dependency-version: 1.6.22 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [golang.org/x/sync](https://github.com/golang/sync) from 0.20.0 to 0.21.0. - [Commits](golang/sync@v0.20.0...v0.21.0) --- updated-dependencies: - dependency-name: golang.org/x/sync dependency-version: 0.21.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [k8s.io/apimachinery](https://github.com/kubernetes/apimachinery) from 0.35.5 to 0.35.6. - [Commits](kubernetes/apimachinery@v0.35.5...v0.35.6) --- updated-dependencies: - dependency-name: k8s.io/apimachinery dependency-version: 0.35.6 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [github.com/openshift-pipelines/pipelines-as-code](https://github.com/openshift-pipelines/pipelines-as-code) from 0.47.0 to 0.48.0. - [Release notes](https://github.com/openshift-pipelines/pipelines-as-code/releases) - [Commits](tektoncd/pipelines-as-code@v0.47.0...v0.48.0) --- updated-dependencies: - dependency-name: github.com/openshift-pipelines/pipelines-as-code dependency-version: 0.48.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
- pipeline: v1.13.0 → v1.13.1 Signed-off-by: tekton-bot <tekton-bot@users.noreply.github.com>
Bumps [github/codeql-action](https://github.com/github/codeql-action) from 4.36.0 to 4.36.2. - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](github/codeql-action@7211b7c...8aad20d) --- updated-dependencies: - dependency-name: github/codeql-action dependency-version: 4.36.2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [actions/checkout](https://github.com/actions/checkout) from 6.0.2 to 6.0.3. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@de0fac2...df4cb1c) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: 6.0.3 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [golang.org/x/mod](https://github.com/golang/mod) from 0.36.0 to 0.37.0. - [Commits](golang/mod@v0.36.0...v0.37.0) --- updated-dependencies: - dependency-name: golang.org/x/mod dependency-version: 0.37.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Add a generator script and config file following the same pattern as tektoncd/pipeline. The dependabot.yml is now generated from .github/dependabot.config.yml, keeping it easy to add/remove release branches without editing the verbose output file directly. A weekly workflow (dependabot-regen.yml) re-runs the generator and opens a PR automatically if changes are detected. Signed-off-by: Jawed khelil <jkhelil@redhat.com> Assisted-by: Claude Sonnet 4.6 (via Cursor) Co-authored-by: Cursor <cursoragent@cursor.com>
Add v0.80 (LTS) to releases.md so the dependabot generator can auto-discover release-v0.80.x when the workflow runs. Signed-off-by: Jawed khelil <jkhelil@redhat.com> Assisted-by: Claude Sonnet 4.6 (via Cursor) Co-authored-by: Cursor <cursoragent@cursor.com>
Add OCI publishing step to the helm-release workflow so the chart is available at oci://ghcr.io/tektoncd/operator/charts/tekton-operator in addition to the existing GitHub Pages Helm repository. This enables Flux CD users to consume the chart via a HelmRepository with type: oci, avoiding the GitRepository workaround that exposes version: "devel" from the raw git source. Uses docker/login-action (SHA-pinned) for ghcr.io authentication and helm push for the OCI publish step. Adds packages: write permission to the job. Signed-off-by: Jawed khelil <jkhelil@redhat.com> Assisted-by: Claude Sonnet 4.6 (via Cursor) Co-authored-by: Cursor <cursoragent@cursor.com>
Use a real contributor identity in the git commit config so the Signed-off-by trailer satisfies EasyCLA. Using tekton-robot@users.noreply.github.com caused the bot account to be flagged as an unsigned CLA signer. Signed-off-by: Jawed khelil <jkhelil@redhat.com> Assisted-by: Claude Sonnet 4.6 (via Cursor) Co-authored-by: Cursor <cursoragent@cursor.com>
This automated PR regenerates .github/dependabot.yml from .github/dependabot.config.yml to ensure the configuration is up-to-date with the latest release branches. Generated by: Regenerate Dependabot Configuration Triggered by: workflow_dispatch Signed-off-by: Jawed khelil <jkhelil@redhat.com>
tekton-multicluster-proxy-aae-role becomes redundent after this change
A recent change where we replaced the manual CRDs with OpenAPI generated CRDs made options field mandatory for components. Historically this field is optional and was never enforced in CRD but openAPI generated CRDs made this field mandatory as there no '+optional' Directive on this field. This PR adds the '+optional directive on this field so generated CRDs keep this field optional.
Bumps [k8s.io/code-generator](https://github.com/kubernetes/code-generator) from 0.35.5 to 0.35.6. - [Commits](kubernetes/code-generator@v0.35.5...v0.35.6) --- updated-dependencies: - dependency-name: k8s.io/code-generator dependency-version: 0.35.6 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [chainguard-dev/actions](https://github.com/chainguard-dev/actions) from 1.6.22 to 1.6.23. - [Release notes](https://github.com/chainguard-dev/actions/releases) - [Commits](chainguard-dev/actions@3b7bbee...5f02082) --- updated-dependencies: - dependency-name: chainguard-dev/actions dependency-version: 1.6.23 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Simplify the OpenShift image SHA update script by removing authentication requirements and consolidating the implementation to use only skopeo. Changes: - Remove REGISTRY_USER and REGISTRY_PASSWORD parameters - script now uses existing registry credentials from local skopeo/podman/docker login - Replace podman commands with skopeo for better compatibility and consistency (skopeo inspect, skopeo list-tags) - Remove manifest-tool container dependency - use skopeo inspect --raw to get image SHA digests directly - Remove unused helper functions (log, err, info, die, usage) - Remove registry_login() function - no longer needed - Improve output formatting with clearer status messages - Reduce script from 103 lines to 68 lines while maintaining functionality The script still updates the same 7 Red Hat images (buildah, kn-client, postgresql-15, skopeo, s2i, ubi-minimal, openjdk-17) across all OpenShift YAML files in: - config/openshift/base/operator.yaml - operatorhub/openshift/config.yaml - operatorhub/openshift/release-artifacts/bundle/manifests/*.yaml - cmd/openshift/operator/kodata/tekton-addon/addons/**/*.yaml Usage is now simpler: bash hack/openshift/update-image-sha.sh (No environment variables required) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Bumps [k8s.io/api](https://github.com/kubernetes/api) from 0.35.5 to 0.35.6. - [Commits](kubernetes/api@v0.35.5...v0.35.6) --- updated-dependencies: - dependency-name: k8s.io/api dependency-version: 0.35.6 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
The semver-major-days, semver-minor-days and semver-patch-days cooldown fields are not supported for the github-actions ecosystem and caused Dependabot validation errors. Only default-days is valid for github-actions; semver cooldown fields are gomod-only. Signed-off-by: Jawed khelil <jkhelil@redhat.com> Assisted-by: Claude Sonnet 4.6 (via Cursor) Co-authored-by: Cursor <cursoragent@cursor.com>
# Conflicts: # config/base/kustomization.yaml
Bumps [k8s.io/apiextensions-apiserver](https://github.com/kubernetes/apiextensions-apiserver) from 0.35.5 to 0.35.6. - [Release notes](https://github.com/kubernetes/apiextensions-apiserver/releases) - [Commits](kubernetes/apiextensions-apiserver@v0.35.5...v0.35.6) --- updated-dependencies: - dependency-name: k8s.io/apiextensions-apiserver dependency-version: 0.35.6 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
The operator service account was missing permissions for the openshift-pipelines.org API group (approvaltasks resources) in the Helm chart ClusterRole. This caused RBAC escalation errors when reconciling ManualApprovalGate on Kubernetes, because the operator cannot grant permissions it does not already hold. The kustomize base (config/base/role.yaml) and OperatorHub CSV already had these permissions; only the Helm chart was missing them. Fixes #3519 Signed-off-by: Jawed khelil <jkhelil@redhat.com> Assisted-by: Claude Sonnet 4.6 (via Cursor) Co-authored-by: Cursor <cursoragent@cursor.com>
TektonAddon is OpenShift-only. Commit e4f5c9d moved the tektonaddons CRD into the shared config/base to satisfy kustomize path restrictions, which caused the Kubernetes bundle to start shipping it. OLM would then advertise it as a Provided API in the Kubernetes OperatorHub console. Add a kustomize patch in config/kubernetes/base that marks tektonaddons CRD with config.kubernetes.io/local-config, causing kustomize to drop it from the Kubernetes build output entirely. Verified: kustomize build config/kubernetes/overlays/operatorhub produces no CRD object for tektonaddons (RBAC rules only), while tektonaddons CRD remains present in the OpenShift build. This is the symmetric counterpart to the OpenShift fix in #3978, which excluded tektondashboards (Kubernetes-only) from the OpenShift bundle. Signed-off-by: Jawed khelil <jkhelil@redhat.com> Assisted-by: Claude Sonnet 4.6 (via Cursor) Co-authored-by: Cursor <cursoragent@cursor.com>
- pipeline: v1.15.0 → v1.15.1 Signed-off-by: tekton-bot <tekton-bot@users.noreply.github.com>
Bumps the all group in /tekton with 3 updates: [chainguard/crane](https://github.com/chainguard-images/images), [tektoncd/plumbing/ko](https://github.com/tektoncd/plumbing) and [tektoncd/plumbing/koparse](https://github.com/tektoncd/plumbing). Updates `chainguard/crane` from `6fc6fcd` to `993b6cd` - [Commits](https://github.com/chainguard-images/images/commits) Updates `tektoncd/plumbing/ko` from `976eb63` to `c84f47a` - [Commits](https://github.com/tektoncd/plumbing/commits) Updates `tektoncd/plumbing/koparse` from `e060328` to `dc3e092` - [Commits](https://github.com/tektoncd/plumbing/commits) --- updated-dependencies: - dependency-name: chainguard/crane dependency-version: latest-dev dependency-type: direct:production dependency-group: all - dependency-name: tektoncd/plumbing/ko dependency-version: c84f47ab24ce22042b06134e8d3e4f4a16943f7b9d63286663691610431051c5 dependency-type: direct:production dependency-group: all - dependency-name: tektoncd/plumbing/koparse dependency-version: dc3e092bd165a1f72e8b1fe0e2a5c5dfcea419adbb7b90fa047967da49fd9a1d dependency-type: direct:production dependency-group: all ... Signed-off-by: dependabot[bot] <support@github.com>
- pruner: v0.4.1 → v0.4.3 Signed-off-by: tekton-bot <tekton-bot@users.noreply.github.com>
Bumps the github-actions group with 3 updates: [github/codeql-action/init](https://github.com/github/codeql-action), [github/codeql-action/analyze](https://github.com/github/codeql-action) and [chainguard-dev/actions/kind-diag](https://github.com/chainguard-dev/actions). Updates `github/codeql-action/init` from 4.37.7 to 4.37.8 - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](github/codeql-action@ff2f1c6...db488dd) Updates `github/codeql-action/analyze` from 4.37.7 to 4.37.8 - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](github/codeql-action@ff2f1c6...db488dd) Updates `chainguard-dev/actions/kind-diag` from 1.6.32 to 1.6.33 - [Release notes](https://github.com/chainguard-dev/actions/releases) - [Commits](chainguard-dev/actions@7bd1e94...0ffab11) --- updated-dependencies: - dependency-name: github/codeql-action/init dependency-version: 4.37.8 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: github-actions - dependency-name: github/codeql-action/analyze dependency-version: 4.37.8 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: github-actions - dependency-name: chainguard-dev/actions/kind-diag dependency-version: 1.6.33 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: github-actions ... Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: tekton-bot <tekton-bot@users.noreply.github.com>
- chains: v0.29.2 → v0.29.3 Signed-off-by: tekton-bot <tekton-bot@users.noreply.github.com>
Secure component metrics endpoints with mutual TLS on OpenShift. Each reconciler syncs the Prometheus client CA bundle from kube-system/extension-apiserver-authentication into the component namespace as a metrics-client-ca ConfigMap. OpenShift's serving-cert controller is triggered via annotation on each metrics Service to provision a per-component TLS Secret. Two new manifest transformers (InjectMetricsServingCert, ApplyMetricsTLS) wire the Secret and ConfigMap as volumes and inject METRICS_PROMETHEUS_TLS_* env vars so that the knative/pkg prometheus.Server enables mTLS with require client auth. ServiceMonitor resources are updated with scheme: https, scrapeClass tls-client-certificate-auth, and tlsConfig.serverName. The existing UpdateServiceMonitorTargetNamespace transformer is extended to also patch the namespace segment inside serverName at runtime. Relates-To: SRVKP-8172 Signed-off-by: Jawed khelil <jkhelil@redhat.com> Assisted-by: Claude Sonnet 4.6 (via Cursor) Co-authored-by: Cursor <cursoragent@cursor.com>
Add opt-in feature flag spec.platforms.openshift.enableMetricsMTLS to TektonConfig. When false (default) all mTLS transformers are skipped so existing clusters are unaffected. Key changes: - Add EnableMetricsMTLS *bool to OpenShift API struct + CRD schema - EnsureMetricsClientCA (TektonConfig-only) returns a clear error when kube-system/extension-apiserver-authentication is absent, asking the user to disable mTLS or install CMO - Add ResolveMetricsMTLS helper (flag check + CM existence in one call) used by all 6 component PreReconcile methods - Gate all mTLS transformers behind metricsMTLSReady on each component extension struct - Include MetricsCABundle content in GetPlatformData() hash so component CRs are automatically re-annotated when TektonConfig creates the CM, triggering immediate component re-reconciles - Add unit tests for IsMetricsMTLSEnabled, AnnotateMetricsServingCert, RenameServicePort, UpdateServiceMonitorForMetricsMTLS Fix tekton-results ServiceMonitor/Service port mismatch: 05-results-monitoring.yaml unconditionally hardcoded scheme: https and https-* port names for both results ServiceMonitors, while the underlying Services keep plain port names unless the flag is on. This broke Prometheus scraping for tekton-results-api and tekton-results-watcher by default, regardless of the flag. The static manifest now stays plain HTTP, and tektonpipeline's filterAndTransformMonitoring conditionally upgrades the results-watcher ServiceMonitor to mTLS in lockstep with the Service port rename, matching every other component. tekton-results-api is excluded from the mTLS upgrade entirely: its Prometheus metrics endpoint (cmd/api/main.go in tektoncd/results) is a bare net/http server that never reads METRICS_PROMETHEUS_TLS_* env vars, so it cannot serve mTLS. Its Service/ServiceMonitor stay on plain HTTP regardless of this flag; this is a known upstream limitation, not something this operator can fix. Signed-off-by: Jawed khelil <jkhelil@redhat.com> Assisted-by: Claude Sonnet 4.6 (via Cursor) Co-authored-by: Cursor <cursoragent@cursor.com>
Expose Prometheus metrics for tekton-pipelines-remote-resolvers by adding a ServiceMonitor, matching the existing monitors for the pipeline controller, webhook, triggers, and chains. Signed-off-by: Deekshith Kumar Netha Bamandla N <dbamandl@redhat.com> Assisted-by: Claude Sonnet 5 (via Cursor) Co-authored-by: Cursor <cursoragent@cursor.com>
Add the missing UpdateServiceMonitorForMetricsMTLS entry for openshift-pipelines-resolvers-monitor so it upgrades to https-metrics in lockstep with the other five monitors when metrics mTLS is enabled. Without this, the resolvers ServiceMonitor would keep requesting the now-renamed http-metrics port, breaking Prometheus scraping on mTLS-enabled clusters. Signed-off-by: Deekshith Kumar Netha Bamandla N <dbamandl@redhat.com> Assisted-by: Claude Sonnet 5 (via Cursor)
The results-retention-policy-agent NetworkPolicy allowed egress to DNS and the database, but not to the Kubernetes API server. The agent uses a ConfigMap watcher (informer) to load its schedule and retention settings from tekton-results-config-results-retention-policy, which requires talking to the API server, not just Postgres/DNS. Signed-off-by: Emil Natan <ena@redhat.com> Assisted-by: Claude <noreply@anthropic.com>
Regenerate Kubernetes and OpenShift operator bundles using operator-sdk v1.37.0 (previously v1.21.0) on release-v0.81.x branch. Changes: - Kubernetes and Openshift bundle updated to v0.81.1 - CRD schemas updated with controller-gen v0.18.0 annotations - Removed deprecated version labels from CRD metadata - Added new CRDs: ManualApprovalGate, OpenShiftPipelinesAsCode, SyncerService, TektonPruner, TektonScheduler, and others. Signed-off-by: pratap0007 <shverma@redhat.com>
Bumps the github-actions group with 4 updates: [github/codeql-action/init](https://github.com/github/codeql-action), [github/codeql-action/analyze](https://github.com/github/codeql-action), [chainguard-dev/actions/kind-diag](https://github.com/chainguard-dev/actions) and [zizmorcore/zizmor-action](https://github.com/zizmorcore/zizmor-action). Updates `github/codeql-action/init` from 4.37.8 to 4.37.9 - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](github/codeql-action@db488dd...cdf488f) Updates `github/codeql-action/analyze` from 4.37.8 to 4.37.9 - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](github/codeql-action@db488dd...cdf488f) Updates `chainguard-dev/actions/kind-diag` from 1.6.33 to 1.6.34 - [Release notes](https://github.com/chainguard-dev/actions/releases) - [Commits](chainguard-dev/actions@0ffab11...a9d4aa7) Updates `zizmorcore/zizmor-action` from 0.6.2 to 0.6.3 - [Release notes](https://github.com/zizmorcore/zizmor-action/releases) - [Commits](zizmorcore/zizmor-action@3dc1ecc...70fb788) --- updated-dependencies: - dependency-name: github/codeql-action/init dependency-version: 4.37.9 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: github-actions - dependency-name: github/codeql-action/analyze dependency-version: 4.37.9 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: github-actions - dependency-name: chainguard-dev/actions/kind-diag dependency-version: 1.6.34 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: github-actions - dependency-name: zizmorcore/zizmor-action dependency-version: 0.6.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: github-actions ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [github.com/tektoncd/pruner](https://github.com/tektoncd/pruner) from 0.4.1 to 0.4.3. - [Release notes](https://github.com/tektoncd/pruner/releases) - [Changelog](https://github.com/tektoncd/pruner/blob/main/releases.md) - [Commits](tektoncd/pruner@v0.4.1...v0.4.3) --- updated-dependencies: - dependency-name: github.com/tektoncd/pruner dependency-version: 0.4.3 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps the all group in /tekton with 3 updates: [chainguard/crane](https://github.com/chainguard-images/images), [tektoncd/plumbing/ko](https://github.com/tektoncd/plumbing) and [tektoncd/plumbing/koparse](https://github.com/tektoncd/plumbing). Updates `chainguard/crane` from `993b6cd` to `8f40a0a` - [Commits](https://github.com/chainguard-images/images/commits) Updates `tektoncd/plumbing/ko` from `c84f47a` to `d5b1f55` - [Commits](https://github.com/tektoncd/plumbing/commits) Updates `tektoncd/plumbing/koparse` from `dc3e092` to `dc202b2` - [Commits](https://github.com/tektoncd/plumbing/commits) --- updated-dependencies: - dependency-name: chainguard/crane dependency-version: latest-dev dependency-type: direct:production dependency-group: all - dependency-name: tektoncd/plumbing/ko dependency-version: d5b1f55955363c20e01c27f940692df77bf5520103012446af9900ac681fbc8c dependency-type: direct:production dependency-group: all - dependency-name: tektoncd/plumbing/koparse dependency-version: dc202b2d066bb4453bf36a0d7b8e6242d52e9516313bb0026d5633b1efe44d29 dependency-type: direct:production dependency-group: all ... Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: tekton-bot <tekton-bot@users.noreply.github.com>
Signed-off-by: tekton-bot <tekton-bot@users.noreply.github.com>
Contributor
Author
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
- manual-approval-gate: v0.9.0 → v0.9.1 - pipeline: v1.15.1 → v1.16.0 - pipelines-as-code: v0.50.0 → v0.51.0 - chains: v0.29.3 → v0.29.4 - dashboard: v0.71.0 → v0.72.0 Signed-off-by: tekton-bot <tekton-bot@users.noreply.github.com>
tekton-robot
force-pushed
the
bot-bump-payload
branch
from
September 11, 2026 05:27
a424fa9 to
73978c7
Compare
Contributor
Author
|
@tekton-robot: PR needs rebase. DetailsInstructions 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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Component Version Updates
This PR updates the following component versions:
chains
v0.27.6v0.29.4dashboard
v0.68.0v0.72.0pipeline
v1.12.2v1.16.0results
v0.19.0v0.20.0scheduler
v0.3.1v0.4.0triggers
v0.36.0v0.37.0manual-approval-gate
v0.9.0v0.9.1pipelines-as-code
v0.48.1v0.51.0This PR was automatically created by the bump-payload workflow.