Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Jan 16, 2026

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

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).

  • Updated dependencies [7e925ea, 118e7a4, d7e75d6]:

    • effect@3.19.15
    • @effect/platform@0.94.2

@effect/cli@0.73.1

Patch Changes

  • #5983 0d1a44f Thanks @cevr! - Allow options to appear after positional arguments

    Previously, @effect/cli required all options to appear before positional arguments. For example, cmd --force staging worked but cmd staging --force failed with "Received unknown argument".

    This change updates the option parsing logic to scan through all arguments to find options, regardless of their position relative to positional arguments. This aligns with the behavior of most CLI tools (git, npm, docker, etc.) which allow options anywhere in the command.

    Before:

    myapp deploy --force staging  # worked
    myapp deploy staging --force  # failed: "Received unknown argument: '--force'"

    After:

    myapp deploy --force staging  # works
    myapp deploy staging --force  # works
  • Updated dependencies [7e925ea, 118e7a4, d7e75d6]:

    • effect@3.19.15
    • @effect/platform@0.94.2

effect@3.19.15

Patch Changes

  • #5981 7e925ea Thanks @bxff! - Fix type inference loss in Array.flatten for complex nested structures like unions of Effects with contravariant requirements. Uses distributive indexed access (T[number][number]) in the Flatten type utility and adds const to the flatten generic parameter.

  • #5970 d7e75d6 Thanks @KhraksMamtsov! - fix Config.orElseIf signature

@effect/platform@0.94.2

Patch Changes

@effect/platform-bun@0.87.1

Patch Changes

@effect/platform-node@0.104.1

Patch Changes

@effect/platform-node-shared@0.57.1

Patch Changes

@github-actions github-actions bot requested a review from IMax153 as a code owner January 16, 2026 02:53
@github-project-automation github-project-automation bot moved this to Discussion Ongoing in PR Backlog Jan 16, 2026
@github-actions github-actions bot force-pushed the changeset-release/main branch from 4870945 to abb87ed Compare January 18, 2026 20:11
@github-actions github-actions bot requested a review from mikearnaldi as a code owner January 18, 2026 20:11
@github-actions github-actions bot force-pushed the changeset-release/main branch from abb87ed to 152a0fd Compare January 19, 2026 22:04
@github-actions github-actions bot requested a review from tim-smart as a code owner January 19, 2026 22:04
@github-actions github-actions bot force-pushed the changeset-release/main branch 3 times, most recently from 0eb7deb to 6651952 Compare January 21, 2026 20:45
@github-actions github-actions bot force-pushed the changeset-release/main branch from 6651952 to b187f44 Compare January 22, 2026 15:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Discussion Ongoing

Development

Successfully merging this pull request may close these issues.

1 participant