ci: only run catlin validate on the resource version directory

[vdemeester]

Changes

The catlin validate gate (introduced in #the Prow→GHA migration, commit 51a8540f) reduces every changed file to its containing directory with dirname and passes the result to catlin validate. For a new task version the changed set includes the tests/ and tests/fixtures/ subdirectories, so catlin validates the test manifests (a TaskRun or Pipeline) as if they were catalog resources:

FILE: task/<name>/<version>/tests/run.yaml
ERROR: Resource path is invalid; expected path: pipeline/<name>/<name>.yaml
ERROR: Pipeline "<name>" must have a label "app.kubernetes.io/version" ...

catlin also errors with unknown kind TaskRun for TaskRun-based tests, so any new task version that ships a tests/run.yaml fails the gate. Because no new task version has been added since the gate landed, this went unnoticed until now (surfaced by #1386).

Fix

Reduce each changed path to its task/<name>/<version> version directory (grep -oE '^task/[^/]+/[^/]+' | sort -u) instead of dirname on every file. catlin then validates only the catalog resource in that directory and does not descend into tests/ or samples/, which are not catalog resources. The existing [[ -d ]] filter still drops removed directories and non-directory matches such as task/<name>/OWNERS. The same detection is applied to the informational "catlin lint scripts" step.

Verified locally with the pinned catlin version CI installs: validating task/<name>/<version> only checks the resource .yaml and ignores tests/.

Submitter Checklist

• Follows the authoring recommendations
• Includes docs (if user facing) — N/A, CI-only change
• Includes tests (for new tasks or changed functionality) — N/A, CI-only change
• Meets the Tekton contributor standards
• Commit messages follow commit message best practices
• Has a kind label — /kind bug
• Complies with Catalog Organization TEP — no catalog resources changed

/kind bug

See the contribution guide for more details.

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment