-
Notifications
You must be signed in to change notification settings - Fork 828
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
1.10.1 backports #3682
1.10.1 backports #3682
Conversation
…open-telemetry#3677) * fix(resource): make properties for async resolution optional * fix(changelog): add changelog * fix(resources): add regression test * fix(resources): remove ts-ignore in tests --------- Co-authored-by: Daniel Dyla <[email protected]>
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## v1.10 #3682 +/- ##
=======================================
Coverage 93.56% 93.56%
=======================================
Files 275 275
Lines 8126 8129 +3
Branches 1691 1697 +6
=======================================
+ Hits 7603 7606 +3
Misses 523 523
|
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.
Looks good, thank you for the backporting this! 🙂
…pen-telemetry#3681) * fix(resources): change fs/promises import to be node 12 compatible * fix(changelog): add changelog entry.
Why backport instead of just release main? |
There was a |
To be clear before I merge this, are you asking purely out of curiosity or because you believe we're making a mistake here? |
Just out of curiosity. Personally I see no benefit of backporting as the changes on main should not harm. |
"@opentelemetry/sdk-trace-base": "1.10.0", | ||
"@opentelemetry/sdk-trace-node": "1.10.0", | ||
"@opentelemetry/semantic-conventions": "1.10.0" | ||
"@opentelemetry/exporter-jaeger": "1.10.1", |
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.
Manually changing the versions indicate that there is no release automation on backport releases.
So it seems we have to take some extra care during the next main release to avoid that it selects the same versions for GA and/or experimental packages.
Bumps the patch version for SDK packages.
Backported PRs:
Note: this PR goes into a branch specifically for the v1.10 release line since there was already a
feat
committed to main