Skip to content

tekton: update plumbing ref to include full image references fix#9399

Merged
tekton-robot merged 1 commit intotektoncd:mainfrom
vdemeester:fix/full-image-references
Feb 18, 2026
Merged

tekton: update plumbing ref to include full image references fix#9399
tekton-robot merged 1 commit intotektoncd:mainfrom
vdemeester:fix/full-image-references

Conversation

@vdemeester
Copy link
Member

Changes

Update the plumbing revision used by the precheck task in the release pipeline to include the fix from tektoncd/plumbing#3110 which replaces short image URLs with full image references (e.g. alpinedocker.io/library/alpine).

Newer k8s versions no longer allow short image URLs, which would break our releases.

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
  • Has Tests included if any functionality added or changed
  • pre-commit Passed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including functionality, content, code)
  • Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
  • Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
  • Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

Update the plumbing revision used by the precheck task to include
the fix from tektoncd/plumbing#3110 which replaces short image URLs
with full image references (e.g. alpine -> docker.io/library/alpine).

Newer k8s versions no longer allow short image URLs.

Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
@vdemeester vdemeester added the kind/bug Categorizes issue or PR as related to a bug. label Feb 18, 2026
@tekton-robot tekton-robot added the release-note-none Denotes a PR that doesnt merit a release note. label Feb 18, 2026
@tekton-robot tekton-robot requested review from dibyom and khrm February 18, 2026 12:01
@tekton-robot tekton-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Feb 18, 2026
Copy link
Member

@waveywaves waveywaves left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@tekton-robot tekton-robot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Feb 18, 2026
Copy link
Member

@afrittoli afrittoli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@vdemeester
Copy link
Member Author

/retest

@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: afrittoli, twoGiants, waveywaves

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 [afrittoli,twoGiants,waveywaves]

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 merged commit 31a2e31 into tektoncd:main Feb 18, 2026
39 of 41 checks passed
@vdemeester vdemeester deleted the fix/full-image-references branch February 18, 2026 13:57
@vdemeester
Copy link
Member Author

/cherry-pick release-v1.9.x release-v1.6.x release-v1.3.x release-v1.0.x

@tekton-robot
Copy link
Collaborator

Cherry-pick to release-v1.6.x failed!

The automatic cherry-pick to release-v1.6.x failed.

Output:

🤖 Starting cherry-pick process...
Fetching PR #9399 information...
Found merge commit: 31a2e31ae8523f847b2d107a06ee4fd7339afcf1
PR title: tekton: update plumbing ref to include full image references fix
Fetching target branch: release-v1.6.x...
From https://github.com/tektoncd/pipeline
 * branch                release-v1.6.x -> FETCH_HEAD
Checking for existing cherry-pick PR...
Creating cherry-pick branch: cherry-pick-9399-to-release-v1.6.x...
Switched to a new branch 'cherry-pick-9399-to-release-v1.6.x'
branch 'cherry-pick-9399-to-release-v1.6.x' set up to track 'origin/release-v1.6.x'.
Fetching commits from PR #9399...
Found 1 commit(s) to cherry-pick
Fetching PR ref to make fork commits available locally...
From https://github.com/tektoncd/pipeline
 * branch                refs/pull/9399/head -> FETCH_HEAD
Cherry-picking commit 1/1: 4efb3d7a9af551bb4aebf89da46c861620b5d728...
Auto-merging tekton/release-pipeline.yaml
CONFLICT (content): Merge conflict in tekton/release-pipeline.yaml
error: could not apply 4efb3d7a9... tekton: update plumbing ref to include full image references fix
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
❌ ERROR: Cherry-pick failed for commit 4efb3d7a9af551bb4aebf89da46c861620b5d728 due to conflicts or other errors

Next steps:

  • Check the action logs for complete details
  • If the PR is not merged, merge it first and try again
  • If there are conflicts, you'll need to manually cherry-pick this PR

@tekton-robot
Copy link
Collaborator

Cherry-pick to release-v1.3.x failed!

The automatic cherry-pick to release-v1.3.x failed.

Output:

🤖 Starting cherry-pick process...
Fetching PR #9399 information...
Found merge commit: 31a2e31ae8523f847b2d107a06ee4fd7339afcf1
PR title: tekton: update plumbing ref to include full image references fix
Fetching target branch: release-v1.3.x...
From https://github.com/tektoncd/pipeline
 * branch                release-v1.3.x -> FETCH_HEAD
Checking for existing cherry-pick PR...
Creating cherry-pick branch: cherry-pick-9399-to-release-v1.3.x...
Switched to a new branch 'cherry-pick-9399-to-release-v1.3.x'
branch 'cherry-pick-9399-to-release-v1.3.x' set up to track 'origin/release-v1.3.x'.
Fetching commits from PR #9399...
Found 1 commit(s) to cherry-pick
Fetching PR ref to make fork commits available locally...
From https://github.com/tektoncd/pipeline
 * branch                refs/pull/9399/head -> FETCH_HEAD
Cherry-picking commit 1/1: 4efb3d7a9af551bb4aebf89da46c861620b5d728...
Auto-merging tekton/release-pipeline.yaml
CONFLICT (content): Merge conflict in tekton/release-pipeline.yaml
error: could not apply 4efb3d7a9... tekton: update plumbing ref to include full image references fix
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
❌ ERROR: Cherry-pick failed for commit 4efb3d7a9af551bb4aebf89da46c861620b5d728 due to conflicts or other errors

Next steps:

  • Check the action logs for complete details
  • If the PR is not merged, merge it first and try again
  • If there are conflicts, you'll need to manually cherry-pick this PR

@tekton-robot
Copy link
Collaborator

Cherry-pick to release-v1.0.x failed!

The automatic cherry-pick to release-v1.0.x failed.

Output:

🤖 Starting cherry-pick process...
Fetching PR #9399 information...
Found merge commit: 31a2e31ae8523f847b2d107a06ee4fd7339afcf1
PR title: tekton: update plumbing ref to include full image references fix
Fetching target branch: release-v1.0.x...
From https://github.com/tektoncd/pipeline
 * branch                release-v1.0.x -> FETCH_HEAD
Checking for existing cherry-pick PR...
Creating cherry-pick branch: cherry-pick-9399-to-release-v1.0.x...
Switched to a new branch 'cherry-pick-9399-to-release-v1.0.x'
branch 'cherry-pick-9399-to-release-v1.0.x' set up to track 'origin/release-v1.0.x'.
Fetching commits from PR #9399...
Found 1 commit(s) to cherry-pick
Fetching PR ref to make fork commits available locally...
From https://github.com/tektoncd/pipeline
 * branch                refs/pull/9399/head -> FETCH_HEAD
Cherry-picking commit 1/1: 4efb3d7a9af551bb4aebf89da46c861620b5d728...
Auto-merging tekton/release-pipeline.yaml
CONFLICT (content): Merge conflict in tekton/release-pipeline.yaml
error: could not apply 4efb3d7a9... tekton: update plumbing ref to include full image references fix
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
❌ ERROR: Cherry-pick failed for commit 4efb3d7a9af551bb4aebf89da46c861620b5d728 due to conflicts or other errors

Next steps:

  • Check the action logs for complete details
  • If the PR is not merged, merge it first and try again
  • If there are conflicts, you'll need to manually cherry-pick this PR

@tekton-robot
Copy link
Collaborator

Cherry-pick to release-v1.9.x successful!

A new pull request has been created to cherry-pick this change to release-v1.9.x.

PR: #9401

Please review and merge the cherry-pick PR.

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

Status: Done

Development

Successfully merging this pull request may close these issues.

5 participants