-
Notifications
You must be signed in to change notification settings - Fork 467
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 the operator v0.87.0 #2207
Comments
@TylerHelmuth you are next on the list :) https://github.com/open-telemetry/opentelemetry-operator/blob/main/RELEASE.md#release-schedule |
@pavolloffay do you want to go right into this one or wait a week since we just released 0.86.0? |
I don't have any preference. It depends if other folks want to get in some functionality cc) @open-telemetry/operator-approvers @open-telemetry/operator-maintainers |
I would like to get this one in #2215 |
It would be great to wait for 0.87.1 collector that fixes CVE-2023-44487 |
We have some guidance here around patch releases: https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/release.md#bugfix-release-criteria
Do we consider this to be a critical vulnerability? The score seems to be 5.3 (moderate) on Github's tracker, but I am not sure if this is what we should be looking at (the CVE talks about Swift specifically). |
Thanks for the info. This is probably a better tracker GHSA-4374-p667-p6c8 |
Some more trackers:
The CVSS v3 Base Score is 7.5 and is classified as 'Important' (in between Moderate and Critical) or of 'Medium' priority. |
I am prepping the release PR, but I believe we need to merge #2239 before the next release. |
No description provided.
The text was updated successfully, but these errors were encountered: