# Tekton v1.6.7

2026-08-27 · [Original release notes](https://github.com/tektoncd/pipeline/releases/tag/v1.6.7) · [Full summary](https://ratatosk.io/en/releases/tekton/v1.6.7)

Important fixes 2 · Other changes 2

## Important fixes (2)

### One-second requeues during `PipelineRun` and `TaskRun` remote resolution

- Affects: remote resolution of `Pipeline`, `Task`, or `StepAction` resources (Inferred)

If a `ResolutionRequest` completion event was missed or could not be mapped through owner references, a run could remain stuck while resolving. The periodic requeue lets resolution progress in those cases.

> * :bug: [release-v1.6.x] Fix PipelineRun stuck in ResolvingTaskRef when RR enqueue is missed (#10488)
> ix PipelineRun remaining stuck in ResolvingTaskRef when a ResolutionRequest completion event is missed by periodically requeueing while remote resolution is in progress

### Resolver frameworks stop re-resolving populated requests

- Affects: the `pkg/remoteresolution` or `pkg/resolution` resolver frameworks

Under load, when the pipeline controller's queue backed up, requests with `Status.Data` populated but not yet marked Done could be reconciled repeatedly. The frameworks now skip resolving those requests again once `Status.Data` is populated.

> * :bug: [cherry-pick: release-v1.6.x] fix(resolvers): skip re-resolution when ResolutionRequest data is already present (#10478)
> Skip re-resolution of ResolutionRequests when Status.Data is already present, preventing hundreds of redundant reconciliations under load.

## Other changes (2)

- Resolver replicas check bucket ownership before resolving requests
- Development action `ossf/scorecard-action` updated to 2.4.4

---

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.
