-
Notifications
You must be signed in to change notification settings - Fork 40
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
chore(master): merge maint-0.9 #478
Conversation
tiborsimko
commented
Dec 4, 2024
- chore(maint-0.9): release 0.9.4 (chore(maint-0.9): release 0.9.4 #418)
- build(python): bump shared REANA packages as of 2024-11-28 (build(python): bump shared REANA packages as of 2024-11-28 (#477) #477)
- fix(kubernetes): avoid privilege escalation in Kubernetes jobs (feat: multiple improvements for REANA 0.9.4 #476)
- fix(config): read secret key from env (feat: multiple improvements for REANA 0.9.4 #476)
- fix(htcondorcern): support multiline commands (fix(htcondorcern): unpacked images and multiline commands #474)
- fix(htcondorcern): run provided command in unpacked image (fix(htcondorcern): unpacked images and multiline commands #474)
- build(deps): update reana-auth-vomsproxy to 1.3.0 (build(deps): update reana-auth-vomsproxy to 1.3.0 #466)
- build(docker): pin setuptools 70 (build(docker): pin setuptools 70 #465)
- fix(config): update reana-auth-vomsproxy to 1.2.1 to fix WLCG IAM (fix(config): update reana-auth-vomsproxy to 1.2.1 to fix WLCG IAM #457)
- feat(backends): add new Compute4PUNCH backend (Add job controller, job monitor and tools to support compute4punch backend #430)
…anahub#457) Update reana-auth-vomsproxy to the latest version in order to fix VOMS proxy initialisation troubles now that WLCG IAM is in production.
Pin `setuptools` to the maximum version of 70 to allow working on Ubuntu 20.04 LTS based environments. (New versions of `setuptools` are not compatible.) Note that this fix is necessary only for the `maint-0.9` branches and the REANA 0.9 release series. In `master` we have switched to Ubuntu 24.04 LTS based environments and Python 3.12 and no pinning is necessary there.
Make sure the secret key is propagated to the Flask app, instead of incorrectly using the default one.
…hub#476) Configure the security context of Kubernetes jobs to disallow privilege escalation.
chore(maint-0.9): release 0.9.4 (reanahub#418) build(python): bump shared REANA packages as of 2024-11-28 (reanahub#477) fix(kubernetes): avoid privilege escalation in Kubernetes jobs (reanahub#476) fix(config): read secret key from env (reanahub#476) fix(htcondorcern): support multiline commands (reanahub#474) fix(htcondorcern): run provided command in unpacked image (reanahub#474) build(deps): update reana-auth-vomsproxy to 1.3.0 (reanahub#466) build(docker): pin setuptools 70 (reanahub#465) fix(config): update reana-auth-vomsproxy to 1.2.1 to fix WLCG IAM (reanahub#457) feat(backends): add new Compute4PUNCH backend (reanahub#430) Note: The merge commit removes the changes related to pinning `setuptools` to version 70, because this was only necessary for the `maint-0.9` branches, as well as other 0.9.4 release-related changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #478 +/- ##
==========================================
- Coverage 48.07% 41.87% -6.21%
==========================================
Files 17 18 +1
Lines 1302 1576 +274
==========================================
+ Hits 626 660 +34
- Misses 676 916 +240
|