-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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.6 cherry-pick candidates #10747
Comments
@terrytangyuan #9058 is also important |
Thanks, @terrytangyuan for creating this release issue. We will schedule 3.4.6 on Friday. |
Sounds good. I can follow the release instructions and start cherry-picking the commits to release-3.4 branch. Is that okay? Is there anything else I should pay attention to during the process? @sarabala1979 @alexec |
Looks like it's still in draft cc @rohankmr414 @caelan-io @JPZ13 |
yeah, #9058 isn't quite ready. 1-2 hairy problems to resolve there. @rohankmr414 will post once it's ready to merge. |
we can take entire master(all fixes) to current v3.4.6. I think there won't be any breaking changes |
Yes, all fixes are listed in the issue description. I'll tag a release on Friday. Please feel free to comment if there are any additional fixes that you'd like to bring into this release. |
This needs to be included since we copy ssh_known_hosts in our Dockerfiles: |
We'd like to get #10745 in please @terrytangyuan. |
We only cherry-pick fixes, not features, into patch releases. |
The release branch is ready (note that certain commits are not cherry-picked, either unnecessary or due to too many conflicts to resolve). It passed CI checks as well as a dry-run for release. https://github.com/argoproj/argo-workflows/tree/release-3.4 I'll create a tag tomorrow to kick off the release. |
@caelan-io any update on this? |
Hi community, here's the a list of commits that can potentially go to the v3.4.6 Argo Workflows release that we are preparing. If you have additional commits/issues/PRs that you want to bring attention to the maintainers, please comment on this issue!
Bug fixes
level=info msg="stopping progress monitor (context done)" error="context canceled"
#10490 (fix: Correct SIGTERM handling. Fixes #10518 #10337 #10033 #10490 #10523)workflow.status
doesn't work with ternary operator in arguments #10393 (fix: exit handler variables don't get resolved correctly. Fixes #10393 #10449)CI and build fixes that might fix/improve the CI during release:
The text was updated successfully, but these errors were encountered: