-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release-v0.14.x] cherry-picks for 0.14.1 release #2921
[release-v0.14.x] cherry-picks for 0.14.1 release #2921
Conversation
When validating declared input and output resources for Tasks within a Pipeline, and an invalid Task declaration is detected, it is not included *what* Task declaration is invalid. (cherry picked from commit e9ebbe3)
variables under params section were not substituted with the values for tasks in finally section. Fixing the parameter interpolation for final tasks. (cherry picked from commit e41a897)
Fix the link to the config options. Remove pipeline run events for now. (cherry picked from commit 6c1f2d6)
(cherry picked from commit c32ce97)
(cherry picked from commit cc86204)
This PR cannot be merged: expecting exactly one kind/ label Available
|
1 similar comment
This PR cannot be merged: expecting exactly one kind/ label Available
|
/kind misc |
This PR cannot be merged: expecting exactly one kind/ label Available
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, this looks good!
Note that cherry-picking all commits in one PR means that release notes automation won't really show the content of the release notes, as it's PR based. The actual list of commits included can be added manually to the release notes.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbwsg The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Changes
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Double check this list of stuff that's easy to miss:
cmd
dir, please updatethe release Task to build and release this image.
Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes