Skip to content

fix: remove YAML document separator from .tekton files#3342

Merged
tekton-robot merged 1 commit into
tektoncd:mainfrom
vdemeester:fix-tekton-yaml-separator
Apr 16, 2026
Merged

fix: remove YAML document separator from .tekton files#3342
tekton-robot merged 1 commit into
tektoncd:mainfrom
vdemeester:fix-tekton-yaml-separator

Conversation

@vdemeester

@vdemeester vdemeester commented Apr 13, 2026

Copy link
Copy Markdown
Member

Changes

Remove the --- YAML document separator between the license/description comments and the PipelineRun manifest in .tekton/release.yaml and .tekton/release-patch.yaml.

The --- creates a multi-document YAML file where the first document contains only comments (no Kubernetes object). PAC tries to parse each YAML document and logs an error for the empty one:

cannot read the PipelineRun: unknown, error: error decoding yaml document: Object 'Kind' is missing

This does not block incoming webhooks or release automation (PAC matches by PipelineRun name for those), but it generates noisy error logs on every GitHub event (PRs, pushes, comments, label changes) hitting the operator Repository CR.

Removing the --- makes the comments part of the same YAML document as the PipelineRun, eliminating the spurious parse errors.

Submitter Checklist

See the contribution guide for more details.

Release Notes

NONE

/kind bug

The '---' separator before the PipelineRun creates a multi-document
YAML where the first document is comments-only. PAC tries to parse
each document and fails with 'Object Kind is missing' on the empty
first document.

Removing the separator makes the comments part of the same YAML
document as the PipelineRun, which PAC can parse correctly.
@tekton-robot tekton-robot added the kind/bug Categorizes issue or PR as related to a bug. label Apr 13, 2026
@tekton-robot tekton-robot added do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Apr 13, 2026
@vdemeester vdemeester closed this Apr 13, 2026
@vdemeester vdemeester reopened this Apr 13, 2026
@tekton-robot tekton-robot added release-note-none Denotes a PR that doesnt merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Apr 13, 2026
@anithapriyanatarajan

Copy link
Copy Markdown
Contributor

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 16, 2026
@anithapriyanatarajan

Copy link
Copy Markdown
Contributor

/approve

@tekton-robot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anithapriyanatarajan

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 [anithapriyanatarajan]

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

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 16, 2026
@tekton-robot tekton-robot merged commit d8985d0 into tektoncd:main Apr 16, 2026
20 of 27 checks passed
@vdemeester vdemeester deleted the fix-tekton-yaml-separator branch April 21, 2026 20:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants