build(deps-dev): bump @effect/opentelemetry from 0.60.0 to 0.61.0

[dependabot]

Bumps @effect/opentelemetry from 0.60.0 to 0.61.0.

Release notes

Sourced from @​effect/opentelemetry's releases.

@​effect/opentelemetry@​0.61.0

Minor Changes

• #5927 f4972ed Thanks @​davidgoli! - Add protobuf protocol support for OTLP exporters

  This introduces an OtlpSerialization service for choosing between JSON and Protobuf encoding.

  Breaking changes:

  • Otlp.layer now requires an OtlpSerialization layer to be provided for the desired encoding format.

  JSON encoding:

  import { Layer } from "effect"
  import { Otlp, OtlpSerialization } from "@effect/opentelemetry"
  // Option 1: Explicit JSON layer
  const layer = Otlp.layerJson({
  baseUrl: "http://localhost:4318",
  resource: { serviceName: "my-service" }
  })
  // Option 2: Use layer and provide OtlpSerialization JSON layer
  const layer = Otlp.layer({
  baseUrl: "http://localhost:4318",
  resource: { serviceName: "my-service" }
  }).pipe(Layer.provide(OtlpSerialization.layerJson))

  Protobuf encoding:

  import { Otlp } from "@effect/opentelemetry"
  // Simply use layerProtobuf for protobuf encoding
  const layer = Otlp.layerProtobuf({
  baseUrl: "http://localhost:4318",
  resource: { serviceName: "my-service" }
  })

• #5952 4725a7e Thanks @​clayroach! - Make @​opentelemetry/sdk-trace-node and @​opentelemetry/sdk-trace-web required peer dependencies instead of optional. This fixes module resolution errors when importing from the main entry point.

Patch Changes

• #5929 abdab5c Thanks @​schickling! - Fix Span.addEvent to correctly handle the 2-argument overload with attributes.

  Previously, calling span.addEvent("name", { foo: "bar" }) would throw TypeError: {} is not iterable because the implementation incorrectly treated the attributes object as a TimeInput. The fix adds proper runtime type discrimination to distinguish between TimeInput (number, Date, or HrTime tuple) and Attributes (plain object).

... (truncated)

Changelog

Sourced from @​effect/opentelemetry's changelog.

0.61.0

Minor Changes

• #5927 f4972ed Thanks @​davidgoli! - Add protobuf protocol support for OTLP exporters

  This introduces an OtlpSerialization service for choosing between JSON and Protobuf encoding.

  Breaking changes:

  • Otlp.layer now requires an OtlpSerialization layer to be provided for the desired encoding format.

  JSON encoding:

  import { Layer } from "effect"
  import { Otlp, OtlpSerialization } from "@effect/opentelemetry"
  // Option 1: Explicit JSON layer
  const layer = Otlp.layerJson({
  baseUrl: "http://localhost:4318",
  resource: { serviceName: "my-service" }
  })
  // Option 2: Use layer and provide OtlpSerialization JSON layer
  const layer = Otlp.layer({
  baseUrl: "http://localhost:4318",
  resource: { serviceName: "my-service" }
  }).pipe(Layer.provide(OtlpSerialization.layerJson))

  Protobuf encoding:

  import { Otlp } from "@effect/opentelemetry"
  // Simply use layerProtobuf for protobuf encoding
  const layer = Otlp.layerProtobuf({
  baseUrl: "http://localhost:4318",
  resource: { serviceName: "my-service" }
  })

• #5952 4725a7e Thanks @​clayroach! - Make @​opentelemetry/sdk-trace-node and @​opentelemetry/sdk-trace-web required peer dependencies instead of optional. This fixes module resolution errors when importing from the main entry point.

Patch Changes

• #5929 abdab5c Thanks @​schickling! - Fix Span.addEvent to correctly handle the 2-argument overload with attributes.

  Previously, calling span.addEvent("name", { foo: "bar" }) would throw TypeError: {} is not iterable because the implementation incorrectly treated the attributes object as a TimeInput. The fix adds proper runtime type discrimination to distinguish between TimeInput (number, Date, or HrTime tuple) and Attributes (plain object).

... (truncated)

Commits

• 3134f12 Version Packages (#5985)
• 4725a7e fix(opentelemetry): make sdk-trace-node and sdk-trace-web required peer deps ...
• f4972ed feat(opentelemetry): add protobuf protocol support for OTLP exporters (#5927)
• abdab5c fix(opentelemetry): correct Span.addEvent 2-arg overload (#5929)
• See full diff 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)