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 v3.4 patch releases discussion #11851
Comments
Sure I think we'll include all fixes if there's no conflict. |
We need to include #11971 to unblock the build. |
@juliev0 and @sarabala1979 suggests including #11774 |
We are targeting end of next week for this. Please comment if you’d like to prioritize any other fixes. |
Ok, I added #11982 on top of those since they'll be included in a 3.4.x release then (the upgrade note in the modal is only for 3.4)
isn't that a feature though? |
From @juliev0:
So we could consider that a fix. |
Security fix #11986 |
Tag created: https://github.com/argoproj/argo-workflows/releases/tag/v3.4.12 |
Released |
Reusing this issue to track any potential bug fixes for future v3.4 patch releases. |
Security fix #12111 |
TODOs:
|
#12172 specifically for the 3.4.x patch series |
@calvinwiebe #12281 has depended on another PR which has spec change. I would recommend upgrading v3.5 which is more stable now. |
EDIT: that appears specific to the merging of archived + live workflows in 3.5, so nvm |
Released https://github.com/argoproj/argo-workflows/releases/tag/v3.4.15 contains below commits |
this commit requires other UI PR need to be cherry-picked which has UI file conflicts. |
We might need another patch ASAP #12515 |
Yea this was my bad, it appears to only apply to 3.5 actually (I didn't realize that as it wasn't the Workflow List but the Workflow Details page, apparently that too was merged in 3.5). I edited my comment. Sorry about that! |
Could #12233 be included the next v3.4 patch release? |
#12492 would be good for any patch release |
Could you please include #11847 in the next patch release? |
#12652 adds some missing docs that are still relevant to |
If it applies neatly, #12666 fixes a warning and performance issue |
#12622 impact is significant, please release as soon as possible |
#12683 fixes a regression from 3.4.7+ |
Sorry for the delay, this took a bit more time than I thought, I was a bit sick last week so couldn't finish it. I've only just finished merging everything in. Please help me check for correctness: https://github.com/isubasinghe/argo-workflows/tree/release-3.4.17 I will go through the commits again and confirm conflicts have been resolved correctly, will release tomorrow night AEDT if everything is okay. |
Why not using release-3.4 branch? See the first paragraph in https://github.com/argoproj/argo-workflows/blob/main/docs/releasing.md |
I didn't want any of these changes to be considered official until correctness had been verified. |
@isubasinghe could you kindly confirm if version 3.4.17 has been released? |
@ishivanshgoel You can find all the releases here: https://github.com/argoproj/argo-workflows/tags |
@tachylatus sure, thanks for the reply. But I couldn't find any recent 3.4 updates after 3.4.16 in January. |
Can we get #11585 in to this as well? Would you like me to make a PR for a fixed up version of it? |
Yes please. |
Yes, we are planning to release one soon. |
can #12233 be included? |
This issue tracks commits for v3.4 patch releases.
The text was updated successfully, but these errors were encountered: