-
Notifications
You must be signed in to change notification settings - Fork 450
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] prepare v0.108.0 release #3265
[chore] prepare v0.108.0 release #3265
Conversation
@@ -2,16 +2,16 @@ | |||
# by default with the OpenTelemetry Operator. This would usually be the latest | |||
# stable OpenTelemetry version. When you update this file, make sure to update the | |||
# the docs as well. | |||
opentelemetry-collector=0.107.0 | |||
opentelemetry-collector=0.108.0 |
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.
Collector v0.108.0 has a breaking change to mark a feature gate stable: https://github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.108.0. Do we need an upgrade rule to remove any -confmap.strictlyTypedInput
feature gates? Or is that too magical?
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.
nah let's not mess with those unless we really need to (i.e. it's something we had added automagically previously)
e8a6db9
to
6e53f74
Compare
6e53f74
to
fb64df0
Compare
Co-authored-by: Mikołaj Świątek <[email protected]>
closes #3241