build(deps): bump go.opentelemetry.io/contrib/propagators/jaeger from 1.35.0 to 1.36.0

[dependabot]

Bumps go.opentelemetry.io/contrib/propagators/jaeger from 1.35.0 to 1.36.0.

Changelog

Sourced from go.opentelemetry.io/contrib/propagators/jaeger's changelog.

[1.36.0/0.61.0/0.30.0/0.16.0/0.11.0/0.9.0/0.8.0] - 2025-05-21

Added

• http.route attribute to otelhttp server request spans, when net/http.Request.Pattern is set in the modules below. (#6905, #6937)
  • go.opentelemetry.io/contrib/instrumentation/github.com/emicklei/go-restful/otelrestful
  • go.opentelemetry.io/contrib/instrumentation/github.com/gin-gonic/gin/otelgin
  • go.opentelemetry.io/contrib/instrumentation/github.com/gorilla/mux/otelmux
  • go.opentelemetry.io/contrib/instrumentation/github.com/labstack/echo/otelecho
  • go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp
• Add WithAttributes option to set instrumentation scope attributes on the created log.Logger in go.opentelemetry.io/contrib/bridges/otelzap. (#6962)
• Add WithAttributes option to set instrumentation scope attributes on the created log.Logger in go.opentelemetry.io/contrib/bridges/otelslog. (#6965)
• Add WithAttributes option to set instrumentation scope attributes on the created log.Logger in go.opentelemetry.io/contrib/bridges/otellogrus. (#6966)
• Add WithAttributes option to set instrumentation scope attributes on the created log.Logger in go.opentelemetry.io/contrib/bridges/otellogr. (#6967)
• Add the WithGinMetricAttributes option to allow setting dynamic, per-request metric attributes based on *gin.Context in go.opentelemetry.io/contrib/instrumentation/github.com/gin-gonic/gin/otelgin. (#6932)
• Use Gin's own ClientIP method to detect the client's IP, which supports custom proxy headers in go.opentelemetry.io/contrib/instrumentation/github.com/gin-gonic/gin/otelgin. (#6095)
• Added test for Fields in go.opentelemetry.io/contrib/propagators/jaeger. (#7119)
• Allow configuring samplers in go.opentelemetry.io/contrib/otelconf. (#7148)
• Slog log bridge now sets SeverityText attribute using source value in go.opentelemetry.io/contrib/bridges/otelslog. (#7198)
• Add http.route metric attribute in go.opentelemetry.io/contrib/instrumentation/github.com/gin-gonic/gin/otelgin. (#7275)
• Add the WithSpanStartOptions option to add custom options to new spans go.opentelemetry.io/contrib/instrumentation/github.com/gin-gonic/gin/otelgin. (#7261)
• Add instrumentation support for go.mongodb.org/mongo-driver/v2 in go.opentelemetry.io/contrib/instrumentation/go.mongodb.org/mongo-driver/v2/mongo/otelmongo. (#6539)
• Rerun the span name formatter after the request ran if a req.Pattern is set, so the span name can include it in go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp. (#7192)

Changed

• Jaeger remote sampler's probabilistic strategy now uses the same sampling algorithm as trace.TraceIDRatioBased in go.opentelemetry.io/contrib/samplers/jaegerremote. (#6892)

• Switched the default for OTEL_SEMCONV_STABILITY_OPT_IN to emit the v1.26.0 semantic conventions by default in the following modules.

  • go.opentelemetry.io/contrib/instrumentation/github.com/emicklei/go-restful/otelrestful
  • go.opentelemetry.io/contrib/instrumentation/github.com/gin-gonic/gin/otelgin
  • go.opentelemetry.io/contrib/instrumentation/github.com/gorilla/mux/otelmux
  • go.opentelemetry.io/contrib/instrumentation/github.com/labstack/echo/otelecho
  • go.opentelemetry.io/contrib/instrumentation/net/http/httptrace/otelhttptrace
  • go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp The OTEL_SEMCONV_STABILITY_OPT_IN=http/dup environment variable can be still used to emit both the v1.20.0 and v1.26.0 semantic conventions. It is however impossible to emit only the 1.20.0 semantic conventions, as the next release will drop support for that environment variable. (#6899)

• Improve performance by reducing allocations for http request when using OTEL_SEMCONV_STABILITY_OPT_IN=http/dup in the modules below. (#7180)

  • go.opentelemetry.io/contrib/instrumentation/github.com/emicklei/go-restful/otelrestful
  • go.opentelemetry.io/contrib/instrumentation/github.com/gin-gonic/gin/otelgin
  • go.opentelemetry.io/contrib/instrumentation/github.com/gorilla/mux/otelmux
  • go.opentelemetry.io/contrib/instrumentation/github.com/labstack/echo/otelecho
  • go.opentelemetry.io/contrib/instrumentation/net/http/httptrace/otelhttptrace
  • go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp

• Update the Jaeger remote sampler to use "github.com/jaegertracing/jaeger-idl/proto-gen/api_v2" in go.opentelemetry.io/contrib/samplers/jaegerremote. (#7061)

• Improve performance by reducing allocations in the gRPC stats handler in go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc. (#7186)

• Update http.route attribute to support request.Pattern in go.opentelemetry.io/contrib/instrumentation/github.com/gorilla/mux/otelmux. (#7108)

• Change the default span name to be GET /path so it complies with the HTTP semantic conventions in go.opentelemetry.io/contrib/instrumentation/github.com/gin-gonic/gin/otelgin. (#6381)

• Set url.scheme attribute to the request URL.Scheme when possible for HTTP client metrics in go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp. (#6938)

• The semantic conventions have been upgraded from v1.17.0 to v1.30.0 in go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc. (#7270)

... (truncated)

Commits

• 934fb13 Release v1.36.0/v0.61.0/v0.30.0/v0.16.0/v0.11.0/v0.9.0/v0.8.0 (#7350)
• ea9b739 fix(deps): update module github.com/labstack/echo/v4 to v4.13.4 (#7352)
• 461e409 otelhttp: Add client-side test for OTEL_SEMCONV_STABILITY_OPT_IN=http/dup w...
• a91d747 chore(deps): update module github.com/uudashr/iface to v1.4.0 (#7346)
• 394163b fix(deps): update module github.com/gin-gonic/gin to v1.10.1 (#7344)
• d1b0749 fix(deps): update go.opentelemetry.io/otel digest to e578799 (#7342)
• b76d20b chore(deps): update googleapis to 55703ea (#7341)
• 2896fea refactor: move example from otelmux to make it a testable example (#7121)
• 158bafc feat: Support mixed categories for semconv opt-in (#7274)
• a35d2d8 refactor: move example from otelgin to make it a testable example (#7328)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

The reviewers field in the dependabot.yml file will be removed soon. Please use the code owners file to specify reviewers for Dependabot PRs. For more information, see this blog post.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.