Bump Tekton Pipeline from v1.12.0 to v1.12.2#2228
Open
shipwright-ci-bot wants to merge 1 commit into
Open
Conversation
shipwright-ci-bot
added
the
kind/dependency-change
openshift-ci
Bot
added
the
release-note
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
pull-request-size
Bot
added
the
size/M
Member
|
/hold Tekton bumped gcr to v0.21.6 which is proven to not be working. |
openshift-ci
Bot
added
the
do-not-merge/hold
shipwright-ci-bot
force-pushed
the
bump-tekton-pipeline
branch
from
c0e9e5f to
fde635c
Compare
shipwright-ci-bot
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
Bumps Tekton Pipeline from v1.12.0 to v1.12.2
You can trigger a rebase manually by commenting
/rebaseand resolve any conflicts with this PR.Submitter Checklist
Release Notes