You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our tool versions are pinned in the Makefile, and we don't have any process for updating them. Ideally this should happen the same way as all other dependencies. Same thing goes for the Golang version we use to build our binaries - it's currently pinned to an arbitrary version in the GHA workflow.
My proposal would be to use renovate for this. It's already used elsewhere in otel - notably the collector contrib repo uses it for dependency management, and it is capable of updating versions embedded in arbitrary files.
Describe the issue you're reporting
Our tool versions are pinned in the Makefile, and we don't have any process for updating them. Ideally this should happen the same way as all other dependencies. Same thing goes for the Golang version we use to build our binaries - it's currently pinned to an arbitrary version in the GHA workflow.
My proposal would be to use renovate for this. It's already used elsewhere in otel - notably the collector contrib repo uses it for dependency management, and it is capable of updating versions embedded in arbitrary files.
I successfully achieved this in my fork. With the following configuration:
The text was updated successfully, but these errors were encountered: