-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
make update-otel shouldn't update the toolchain #33600
Comments
A workaround is to run the command w/ the same go version as what's in the repo |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
I may have found a way to somewhat fix this issue. You can run |
@codeboten PR is open: #35490 |
**Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> This PR adds a new `remove-toolchain` make command which removes the `toolchain` directive from all go.mod files. The new make command is also added to the `update-otel` make target. **Link to tracking Issue:** <Issue number if applicable> - fixes open-telemetry#33600 - could potentially also work for open-telemetry#35160 **Testing:** <Describe what testing was performed and which tests were added.> - add a `toolchain go1.22.5` directive to any of the go.mod files in this repo - call `make remove-toolchain` - check if the toolchain directive was removed --------- Signed-off-by: Moritz Wiesinger <moritz.wiesinger@dynatrace.com>
Component(s)
No response
Describe the issue you're reporting
This is a problem that blocks releases every time:
https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/33593/files#diff-a130a63473f70bd378b211cd809cb20b6629b62ae603fd1b280445412a2dfa95R7
The text was updated successfully, but these errors were encountered: