-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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] Fix update-otel #38676
[chore] Fix update-otel #38676
Conversation
Signed-off-by: Evan Bradley <[email protected]>
Signed-off-by: Evan Bradley <[email protected]>
Signed-off-by: Evan Bradley <[email protected]>
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.
Approval pending passing tests
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Remove the deprecation notice until the v0.122.0 release is complete. After trying to migrate from `Range` to `All` in open-telemetry/opentelemetry-collector-contrib#38676, I think the changes required for this will be sufficiently large that we should avoid doing them during a release.
I'm going to close this in favor of getting the release out, the diff is growing too large to do during a release. I undid the deprecation notice in open-telemetry/opentelemetry-collector#12648, we can migrate contrib to the new method after the release is complete. |
Fix build errors in #38668.