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.5 patch releases discussion #11997
Comments
#12025 needs to be fixed for this |
I am thinking about releasing v3.5.1 next week. The most important fix would be #12068 since it blocks people from upgrading to v3.5. |
Security fix: #12111 |
Would be good to get my UI code-splitting / bundle reductions changes into the next patch release once they're all merged in (#12061, #12097, #12150). They are primarily refactors in content, but their overall intent is to fix long wait times for the UI on slow networks or slow devices as described in #11970 |
TODO: @terrytangyuan to post a list of commits to cherry-pick here |
Could you add #12215 and #12214 to 3.5.2 please @terrytangyuan, just to ensure those tests are happening. |
Could we add the UI code-splitting PRs as I mentioned above? I don't think they have a big impact to that many users, so I'm fine with it going in 3.5.3 instead if you'd prefer to keep 3.5.2 smaller/more stable. Otherwise commit list LGTM ✅ |
Sounds good. In the future, let's make sure the PR titles can tell us that. |
Yea each PR individually is more of a refactor, but as a whole they are a fix -- in other words, a bunch of refactors that enable a fix. |
Working on branch https://github.com/argoproj/argo-workflows/tree/release-3.5.2 Note that I also included some merged dependabot PRs from master branch and some of the dependabot PRs cannot be cherry-picked. |
v3.5.2 tag created https://github.com/argoproj/argo-workflows/releases/tag/v3.5.2 |
Request to include #12353 |
This needs to be included #12470 |
#12421 is also a fix for a 3.5.0 feature |
Updating here that 3.5.3 was released |
#12397 for the next release |
Good news, it is done now, I want to go over the changes carefully again though. Should be finished tomorrow evening or by Tuesday evening. |
Do you want to post a branch or something for others to review? |
Please help me check the correctness here: https://github.com/isubasinghe/argo-workflows/tree/release-3.5.5 |
Would it be a good idea to make a PR to v3.5.4 and trigger git actions to make sure all tests pass? |
I've doubled checked it's fine and CI passes. I don't have the permissions to create a tag however. @terrytangyuan |
Can you update the release branch? Once updated, I can also help create a tag: https://github.com/argoproj/argo-workflows/tree/release-3.5 |
I did notice that two missing from this list were mentioned above in this issue: #12556 and #12581
I checked a few of the individual commits that LGTM / match their counterparts. The notable difference is the reversed order of the commits (that you had mentioned offline due to the Also ran a |
I added these two:
and another patch that was recently added:
|
Thanks @agilgur5, I suppose let's ship it |
You should be able to create a tag now. |
Completed in #12312 (comment) |
could we make a patch release for recent CVE fixes? |
Yes, we should release a patch for security fixes. |
@isubasinghe, I see that #12413 was originally included as a feature addition for v3.5.5, but the was removed from your final comment. Is this feature being bumped to v3.5.6 or to a v3.6.x release? I see a few followup PRs ( #12596, #12632, #12862) as well, so maybe there was a stability concern? Looking forward to getting this feature released. Thanks! |
Backported both to |
Released v3.5.6 |
Any objections to cherry-pick #12736 to the next 3.5 patch release? |
Nope, had been planning to do so since it's a feature that fixes substantial 3.5 regressions (so long as it didn't break anything). Had also added the 3.5.x milestone to the respective issues |
This issue tracks commits for 3.5 patch releases.
The text was updated successfully, but these errors were encountered: