Skip to content
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

Upgrade to v0.13.0 of go.opentelemetry.io/otel #389

Closed
codeboten opened this issue Oct 9, 2020 · 3 comments · Fixed by #391
Closed

Upgrade to v0.13.0 of go.opentelemetry.io/otel #389

codeboten opened this issue Oct 9, 2020 · 3 comments · Fixed by #391
Assignees

Comments

@codeboten
Copy link
Contributor

The new version moved/renamed several packages. Therefore we cannot upgrade to otel v0.13.0 without go-contrib also upgrading

@Aneurysm9 Aneurysm9 self-assigned this Oct 9, 2020
@Aneurysm9
Copy link
Member

Upgrading contrib is a standard part of our release process and typically follows a day behind. I've started on this process, but the propagator changes this time around are less amenable to s///g so it may take slightly longer.

@codeboten
Copy link
Contributor Author

Hey @Aneurysm9, I wasn't sure if it was part of the process or not so thanks for clarifying!

@Aneurysm9
Copy link
Member

No worries! I'd love to have a process whereby we could release the main repo and contrib simultaneously, but I'm not sure I see a great way to it since we need to be able to update the go.mod files in contrib to point to the new release tag. Once we hit 1.0 this will (hopefully) become a non-issue as we'll stop breaking things with every release! :)

@Aneurysm9 Aneurysm9 linked a pull request Oct 9, 2020 that will close this issue
plantfansam referenced this issue in plantfansam/opentelemetry-go-contrib Mar 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants