Repository navigation
Bump sidecar deps and release new sidecars - #183
ElijahQuinones wants to merge 1 commit into
Conversation
|
PR Looks good to me, waiting on CVE report to approve |
SummaryHello and thank you for your contribution to the CSI Components repository! This PR was created from a fork of the upstream Instructions for Third Party ContributorsMaintainers will review your PR as per normal GitHub procedure, and approve and/or suggest changes as necessary. After the changes are ready to merge, a maintainer will transfer the changes to a branch on the upstream repository and open a new PR using the new branch. This will allow the changes to run against the E2E changes before being merged. You may find it useful to pre-emptively run the E2E tests yourself to avoid any issues in the merging process. Currently, the CI runs the following E2E tests:
Note: These tests require access to an AWS account, and will temporarily create testing resources in the account that cost money. If the tests crash or otherwise exit early, they may leave resources behind that require manual cleanup. Instructions for MaintainersIf you are a maintainer and submitted this PR, close it and open the PR using a branch pushed to the upstream If this is a third party contributor's PR, follow this procedure:
gh pr checkout 183
git switch -c pr-183
git push
|
SummaryHello and thank you for your contribution to the CSI Components repository! This PR was created from a fork of the upstream Instructions for Third Party ContributorsMaintainers will review your PR as per normal GitHub procedure, and approve and/or suggest changes as necessary. After the changes are ready to merge, a maintainer will transfer the changes to a branch on the upstream repository and open a new PR using the new branch. This will allow the changes to run against the E2E changes before being merged. You may find it useful to pre-emptively run the E2E tests yourself to avoid any issues in the merging process. Currently, the CI runs the following E2E tests:
Note: These tests require access to an AWS account, and will temporarily create testing resources in the account that cost money. If the tests crash or otherwise exit early, they may leave resources behind that require manual cleanup. Instructions for MaintainersIf you are a maintainer and submitted this PR, close it and open the PR using a branch pushed to the upstream If this is a third party contributor's PR, follow this procedure:
gh pr checkout 183
git switch -c pr-183
git push
|
1 similar comment
SummaryHello and thank you for your contribution to the CSI Components repository! This PR was created from a fork of the upstream Instructions for Third Party ContributorsMaintainers will review your PR as per normal GitHub procedure, and approve and/or suggest changes as necessary. After the changes are ready to merge, a maintainer will transfer the changes to a branch on the upstream repository and open a new PR using the new branch. This will allow the changes to run against the E2E changes before being merged. You may find it useful to pre-emptively run the E2E tests yourself to avoid any issues in the merging process. Currently, the CI runs the following E2E tests:
Note: These tests require access to an AWS account, and will temporarily create testing resources in the account that cost money. If the tests crash or otherwise exit early, they may leave resources behind that require manual cleanup. Instructions for MaintainersIf you are a maintainer and submitted this PR, close it and open the PR using a branch pushed to the upstream If this is a third party contributor's PR, follow this procedure:
gh pr checkout 183
git switch -c pr-183
git push
|
Issue #, if available:
Description of changes:
Bump sidecars and remove patches dependencies that have been updated upstream
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.