Skip to content

[cherry-pick: release-v0.27.x] fix(release): stop duplicating GitHub release title - #1853

Open
jkhelil wants to merge 1 commit into
tektoncd:release-v0.27.xfrom
jkhelil:cherry-pick-1851-to-release-v0.27.x
Open

[cherry-pick: release-v0.27.x] fix(release): stop duplicating GitHub release title#1853
jkhelil wants to merge 1 commit into
tektoncd:release-v0.27.xfrom
jkhelil:cherry-pick-1851-to-release-v0.27.x

Conversation

@jkhelil

@jkhelil jkhelil commented Aug 4, 2026

Copy link
Copy Markdown
Member

This is an automated cherry-pick of #1851

/kind bug

Changes

The create-draft-release task's github_release_oci.yaml pin was
still on the commit before tektoncd/plumbing#3519, so this pipeline
never picked up the upstream fix for the duplicated, quoted release
title.

This PR:

  • Bumps the pinned plumbing revision to main, which includes that
    fix.

  • Drops this pipeline's own Release ${VERSION} fallback name in
    prepare-draft-release: the plumbing task only avoids the
    duplicated title when release-name is empty, so synthesizing a
    non-empty fallback here defeated the fix, producing titles like:

    Tekton Chains release v0.27.x "Release v0.27.x"
    
  • Wires up the new draft param (default "false") introduced by
    that same plumbing PR, so releases are published directly instead
    of being left as an unpublished draft that a maintainer has to
    manually publish.

Submitter Checklist

  • Has Docs included if any changes are user facing
  • Has Tests included if any functionality added or changed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including
    functionality, content, code)
  • Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
  • Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

Fix duplicated GitHub release titles and publish releases directly instead of leaving them as unpublished drafts.

Made with Cursor

The create-draft-release task's github_release_oci.yaml pin was
still on the commit before tektoncd/plumbing#3519, so this pipeline
never picked up the upstream fix for the duplicated, quoted release
title.

Bump the pinned plumbing revision to main, which includes that fix,
and drop this pipeline's own "Release ${VERSION}" fallback name in
prepare-draft-release: the plumbing task only avoids the duplicated
title when release-name is empty, so synthesizing a non-empty
fallback here defeated the fix, producing titles like:

  Tekton Chains release v0.28.0 "Release v0.28.0"

Also wire up the new "draft" param (default "false") introduced by
that same plumbing PR, so releases are published directly instead of
being left as an unpublished draft that a maintainer has to manually
publish.

Signed-off-by: Jawed khelil <jkhelil@redhat.com>
Assisted-by: Claude Sonnet 5 (via Cursor)
Co-authored-by: Cursor <cursoragent@cursor.com>
(cherry picked from commit 0335906)
@tekton-robot tekton-robot added the kind/bug Categorizes issue or PR as related to a bug. label Aug 4, 2026
@tekton-robot

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please ask for approval from jkhelil after the PR has been reviewed.

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

Details Needs approval from an approver in each of these files:

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 size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Aug 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind/bug Categorizes issue or PR as related to a bug. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants