Skip to content

Bump tektoncd/pipeline to 1.3.4 to fix CVE-2026-33211#2835

Open
divyansh42 wants to merge 1 commit intotektoncd:release-v0.42.1from
divyansh42:fix-cve-pipelines-42.1
Open

Bump tektoncd/pipeline to 1.3.4 to fix CVE-2026-33211#2835
divyansh42 wants to merge 1 commit intotektoncd:release-v0.42.1from
divyansh42:fix-cve-pipelines-42.1

Conversation

@divyansh42
Copy link
Copy Markdown
Member

@divyansh42 divyansh42 commented May 3, 2026

Changes

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

  • Includes tests (if functionality changed/added)
  • Run the code checkers with make check
  • Regenerate the manpages, docs and go formatting with make generated
  • Commit messages follow commit message best practices

See the contribution guide
for more details.

Release Notes

NONE

@tekton-robot tekton-robot added the release-note Denotes a PR that will be considered when it comes time to generate release notes. label May 3, 2026
@tekton-robot tekton-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. release-note-none Denotes a PR that doesnt merit a release note. and removed release-note Denotes a PR that will be considered when it comes time to generate release notes. labels May 3, 2026
Signed-off-by: divyansh42 <diagrawa@redhat.com>
@divyansh42 divyansh42 force-pushed the fix-cve-pipelines-42.1 branch from 719ec6c to 57686e1 Compare May 3, 2026 09:41
@divyansh42 divyansh42 changed the title Bump tektoncd/pipeline to 1.3.3 to fix CVE-2026-33211 Bump tektoncd/pipeline to 1.3.4 to fix CVE-2026-33211 May 3, 2026
@pratap0007
Copy link
Copy Markdown
Contributor

/lgtm
/approve

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label May 4, 2026
@pratap0007
Copy link
Copy Markdown
Contributor

/approve

@tekton-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: pratap0007
To complete the pull request process, please assign vinamra28 after the PR has been reviewed.
You can assign the PR to them by writing /assign @vinamra28 in a comment when ready.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants