-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Cherry-pick 3.3.9 #9262
Comments
I propose to cherry pick the following commits related to security:
|
This fix contains other feature changes. We could cherry pick |
I am busy with priority work. I will try to release before the end of this week. |
@terrytangyuan Do you have bandwidth do cherry-pick? |
Hi @terrytangyuan @sarabala1979, is this something I could help out with? If one of you can provide a quick write up of what needs to be done, happy to take a stab at it. |
Yes, I can try cherry-picking to release-3.3 branch. Update: it's cherry-picked but CI is failing. Investigating https://github.com/argoproj/argo-workflows/runs/7634723040?check_suite_focus=true |
@mcgrawia @sarabala1979 #9235 has been cherry-picked and CI is passing in the release branch. |
I cherry-picked this one as well. |
Hi @terrytangyuan, it looks like the changes are ready to go on the release branch. Is there anything else that needs to be done before the patch can be released? |
@terrytangyuan Sorry I forgot to mention. Cherry-pick process is to cherry-pick all fixes (exclude new feature fixes or fixes in new code). |
Okay I thought you only needed help with the mentioned fixes. Unfortunately I am on vacation starting today. Would you be able to take it from here? |
Hi @sarabala1979, I see some progress was made on cherry picking the commits to the release branch. Just offering again to see if there's anything I can do to get this over the finish line. The Critical level CVE was identified 26 days ago and we are about to break our 30 day patch SLAs with our customers if we cannot get this released asap. Please let me know, thanks |
Release 3.3.9 |
Thank you so much @sarabala1979!! |
{{ workflow.failures }}
doesn't get a value in lifecycle hook #8882 (fix: Add workflow failures before hooks run. Fixes #8882 #9009){{workflow.status}}
is not working in metrics #8895 (fix: workflow.status is now set properly in metrics. Fixes #8895 #8939)swagger.json
when opening with https://editor.swagger.io #8830 (fix: Fixed Swagger error. Fixes #8830 #8886)List
on all Secrets #8534 (fix!: remove list and watch on secrets. Fixes #8534 #8555)ARGO_REMOVE_PVC_PROTECTION_FINALIZER
by default. Fixes Enable ARGO_REMOVE_PVC_PROTECTION_FINALIZER by default. #8592 (fix: enableARGO_REMOVE_PVC_PROTECTION_FINALIZER
by default. Fixes #8592 #8661)ArtifactGC
should be onArtifact
notTemplate
#8556. (fix: ArtifactGC moved from Template to Artifact. Fixes #8556. #8581)SearchArtifact
to returnArtifactSearchResults
. Fixes Artifact GC:SearchArtifact
to returnArtifactSearchResults
#8543 (fix(Artifact GC): modifiedSearchArtifact
to returnArtifactSearchResults
. Fixes #8543 #8557)k8sapi
executor #7802 (fix: removed deprecated k8sapi executor. Fixes #7802 #8205)The text was updated successfully, but these errors were encountered: