-
Notifications
You must be signed in to change notification settings - Fork 438
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
[DOC] Upgrade for each dependency is hard to maintain #2678
Comments
This issue was marked as stale due to lack of activity. |
Hi, @marcalff I would like to work on this issue as a beginner? Is it still open for changes? |
Sorry I missed this message. Yes, any contributions are welcome. The goal is up expand the docs/maintaining-dependencies.md file. |
This issue is available for anyone to work on. Make sure to reference this issue in your pull request. |
There is already a maintain document, and the missing content will be added based on this document. |
Currently, the steps to update a dependency in maintaining-dependencies.md have a lot of similar and repeated parts. It would be better to separate them into a common section to follow. |
Check in new dependencies:
|
In light of #2676 and #2677, it turns out upgrading each dependency is not trivial, because versions numbers for each dependencies are spread in multiple files in the source code, some of them long forgotten and easy to overlook.
In this case, opentelemetry-proto was updated to 1.3.1 in a few places, but left as 1.1.0 in others.
Provide maintainers documentation that lists exhaustively, for each dependency:
The text was updated successfully, but these errors were encountered: