Open terrytangyuan opened 1 year ago
Do we want to cherry-pick in my UI date filter fixes? i.e. #11742, #11792, #11840
If so, I think I'd want to make another PR to remove the date filter default from the upgrade notes modal (as #11840 removes the default)
Sure I think we'll include all fixes if there's no conflict.
We need to include https://github.com/argoproj/argo-workflows/pull/11971 to unblock the build.
@juliev0 and @sarabala1979 suggests including https://github.com/argoproj/argo-workflows/pull/11774
We are targeting end of next week for this. Please comment if you’d like to prioritize any other fixes.
Sure I think we'll include all fixes if there's no conflict.
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)
@juliev0 and @sarabala1979 suggests including #11774
isn't that a feature though?
From @juliev0:
Without it, users in a cluster with too many sso groups can't log in to Argo Server.
So we could consider that a fix.
Tag created: https://github.com/argoproj/argo-workflows/releases/tag/v3.4.12 Images will be published once CI succeeds: https://github.com/argoproj/argo-workflows/actions/runs/6587281270/job/17897237879
Released
Reusing this issue to track any potential bug fixes for future v3.4 patch releases.
Sorry, I forgot to ask before to merge this one: https://github.com/argoproj/argo-workflows/pull/11470/files (no hurry)
As discussed in today's contributors meeting, for v3.4 patch release, I will only cherry-pick the additional commits mentioned in the comments on this issue.
Commits to include in v3.4.14 release:
requesting this be incorporated as well: https://github.com/argoproj/argo-workflows/pull/12203 (this is based on a Regression issue called out in 3.5.1 but I assume it also applies to 3.4.13, which is where it was noticed by someone at Intuit)
requesting this be incorporated as well: #12203 (this is based on a Regression issue called out in 3.5.1 but I assume it also applies to 3.4.13, which is where it was noticed by someone at Intuit)
It's already patched in https://github.com/argoproj/argo-workflows/pull/12201 to release-3.4.14 branch
v3.4.14 tag created https://github.com/argoproj/argo-workflows/releases/tag/v3.4.14
May I request #12281 be included in the next 3.4 patch? Upgrading to 3.5 caused some issues we don't have cycles to debug at the moment and would prefer to remain on 3.4 if we could. Thanks!
Request to include https://github.com/argoproj/argo-workflows/pull/12353
This needs to be included https://github.com/argoproj/argo-workflows/pull/12470
I am working on releasing v3.4.15 patch that includes https://github.com/argoproj/argo-workflows/pull/12470 https://github.com/argoproj/argo-workflows/pull/12353 https://github.com/argoproj/argo-workflows/pull/12281
@terrytangyuan @agilgur5 @juliev0 Let me know if you need to include any other PRs
@calvinwiebe https://github.com/argoproj/argo-workflows/pull/12281 has depended on another PR which has spec change. I would recommend upgrading v3.5 which is more stable now.
~#12397 would be good to have for any patch~
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 b3aaaa45d chore(build): Replaced master to main in changelogs fbf933563 fix: Resolve vulnerabilities in axios (#12470) feb992505 fix: liveness check (healthz) type asserts to wrong type (#12353) edb0a98c3 fix(docs): release-3.4 readthedocs backport (#12474)
12397 would be good to have for any patch
this commit requires other UI PR need to be cherry-picked which has UI file conflicts. Can you ask user to pick v3.5?
We might need another patch ASAP https://github.com/argoproj/argo-workflows/pull/12515
Another vuln #12556 (which is actually from a new go-git
dep after #12515)
12397 would be good to have for any patch
this commit requires other UI PR need to be cherry-picked which has UI file conflicts. Can you ask user to pick v3.5?
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?
Could you please include #11847 in the next patch release? Our workflow-controller is susceptible to crashing with "was unable to obtain node for ...".
release-3.4
If it applies neatly, #12666 fixes a warning and performance issue
https://github.com/argoproj/argo-workflows/pull/12622 impact is significant, please release as soon as possible
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
This issue tracks commits for v3.4 patch releases.