Promote StepAction API to v1 (tekton.dev/v1)

[vdemeester]

StepActions are documented as a stable/GA feature (docs/stepactions.md), and #8485 tracked promoting the feature to GA. However, the StepAction API type still only exists in v1alpha1 and v1beta1 — there is no tekton.dev/v1 StepAction.

Unlike Task/Pipeline/TaskRun/PipelineRun, StepAction is absent from pkg/apis/pipeline/v1/register.go, the CRD (config/300-crds/300-stepaction.yaml) only serves v1alpha1/v1beta1 with v1beta1 as storage, and the webhook (cmd/webhook/main.go) only registers v1alpha1 <-> v1beta1 conversion.

This issue tracks graduating the StepAction API version to v1.

Tasks

• Add pkg/apis/pipeline/v1/stepaction_{types,defaults,validation}.go
• Add conversion v1beta1 <-> v1 + register in cmd/webhook/main.go
• Add StepAction/StepActionList to pkg/apis/pipeline/v1/register.go
• CRD: serve v1, set storage version, configure conversion
• Regenerate clients/informers/listers (./hack/update-codegen.sh)
• Migrate reconciler/resolvers from v1beta1.StepAction to v1
• Update docs + regenerate docs/pipeline-api.md

Related

• TEP-0142 Promote StepActions to GA #8485 (feature GA)
• TEP-0142 Promote StepActions to Beta #7805 (beta promotion)

[beanscg]

Bean Labs took a public-source pass on this issue.

The narrowest useful next step looks like: Offer a concise wording/example clarification for docs/stepactions.md after verifying the current page.

Public evidence checked:

• Open public issue in tektoncd/pipeline; repo license Apache-2.0; no assignee; 0 comments.
• Labels: kind/feature, area/api, area/roadmap.
• Referenced files/paths: docs/stepactions.md, pkg/apis/pipeline/v1/register.go, config/300-crds/300-stepaction.yaml, cmd/webhook/main.go.

A good acceptance check would be a narrow public change that directly exercises the issue's reported boundary.

No PR opened from this pass.