Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 27, 2026

This PR contains the following updates:

Package Change Age Confidence
io.opentelemetry.semconv:opentelemetry-semconv-incubating 1.37.0-alpha β†’ 1.39.0-alpha age confidence

Configuration

πŸ“… Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

β™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

πŸ”• Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner January 27, 2026 23:33
@codecov
Copy link

codecov bot commented Jan 27, 2026

Codecov Report

βœ… All modified and coverable lines are covered by tests.
βœ… Project coverage is 90.17%. Comparing base (87b0d9a) to head (fc5070b).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##               main    #8022   +/-   ##
=========================================
  Coverage     90.16%   90.17%           
+ Complexity     7484     7483    -1     
=========================================
  Files           836      836           
  Lines         22562    22562           
  Branches       2237     2237           
=========================================
+ Hits          20344    20345    +1     
+ Misses         1515     1513    -2     
- Partials        703      704    +1     

β˜” View full report in Codecov by Sentry.
πŸ“’ Have feedback on the report? Share it here.

πŸš€ New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@renovate renovate bot force-pushed the renovate/io.opentelemetry.semconv-opentelemetry-semconv-incubating-1.x branch from ca9e0e9 to 6b0604a Compare January 28, 2026 18:47
@renovate renovate bot changed the title fix(deps): update dependency io.opentelemetry.semconv:opentelemetry-semconv-incubating to v1.38.0-alpha fix(deps): update dependency io.opentelemetry.semconv:opentelemetry-semconv-incubating to v1.39.0-alpha Jan 28, 2026
@renovate
Copy link
Contributor Author

renovate bot commented Jan 29, 2026

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@jkwatson jkwatson merged commit fd7d014 into main Jan 29, 2026
45 of 47 checks passed
@jkwatson jkwatson deleted the renovate/io.opentelemetry.semconv-opentelemetry-semconv-incubating-1.x branch January 29, 2026 03:08
}
if (grpcStatusCode != null) {
return Attributes.of(SemConvAttributes.RPC_GRPC_STATUS_CODE, grpcStatusCode);
return Attributes.of(SemConvAttributes.RPC_RESPONSE_STATUS_CODE, grpcStatusCode.name());
Copy link
Member

@jack-berg jack-berg Jan 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jkwatson did you clock this change? Its essentially a breaking change to our internal telemetry, but its understood if you choose InternalTelemetryVersion.LATEST, that the instrumentation will change as we keep up with changes from the still-evolving semantic-conventions.

cc @open-telemetry/java-approvers for visibility.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

whoops. No, I hadn't noticed you had made some adjustments to the PR. If you're fine with this, I'm also fine with it.

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 this pull request may close these issues.

2 participants