Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Nov 4, 2025

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/[email protected]

Minor Changes

  • #5606 24a1685 Thanks @tim-smart! - backport @effect/cluster from effect v4

    @effect/cluster no longer requires a Shard Manager, and instead relies on the
    RunnerStorage service to track runner state.

    To migrate, remove any Shard Manager deployments and use the updated layers in
    @effect/platform-node or @effect/platform-bun.

    Breaking Changes

    • ShardManager module has been removed
    • EntityNotManagedByRunner error has been removed
    • Shard locks now use database advisory locks, which requires stable sessions
      for database connections. This means load balancers or proxies that rotate
      connections may cause issues.
    • @effect/platform-node/NodeClusterSocketRunner is now
      @effect/cluster/NodeClusterSocket
    • @effect/platform-node/NodeClusterHttpRunner is now
      @effect/cluster/NodeClusterHttp
    • @effect/platform-bun/BunClusterSocketRunner is now
      @effect/cluster/BunClusterSocket
    • @effect/platform-bun/BunClusterHttpRunner is now
      @effect/cluster/BunClusterHttp

    New Features

    • RunnerHealth.layerK8s has been added, which uses the Kubernetes API to track
      runner health and liveness. To use it, you will need a service account with
      permissions to read pod information.

Patch Changes

[email protected]

Minor Changes

Patch Changes

@effect/[email protected]

Minor Changes

  • #5606 24a1685 Thanks @tim-smart! - backport @effect/cluster from effect v4

    @effect/cluster no longer requires a Shard Manager, and instead relies on the
    RunnerStorage service to track runner state.

    To migrate, remove any Shard Manager deployments and use the updated layers in
    @effect/platform-node or @effect/platform-bun.

    Breaking Changes

    • ShardManager module has been removed
    • EntityNotManagedByRunner error has been removed
    • Shard locks now use database advisory locks, which requires stable sessions
      for database connections. This means load balancers or proxies that rotate
      connections may cause issues.
    • @effect/platform-node/NodeClusterSocketRunner is now
      @effect/cluster/NodeClusterSocket
    • @effect/platform-node/NodeClusterHttpRunner is now
      @effect/cluster/NodeClusterHttp
    • @effect/platform-bun/BunClusterSocketRunner is now
      @effect/cluster/BunClusterSocket
    • @effect/platform-bun/BunClusterHttpRunner is now
      @effect/cluster/BunClusterHttp

    New Features

    • RunnerHealth.layerK8s has been added, which uses the Kubernetes API to track
      runner health and liveness. To use it, you will need a service account with
      permissions to read pod information.

Patch Changes

@effect/[email protected]

Minor Changes

  • #5606 24a1685 Thanks @tim-smart! - backport @effect/cluster from effect v4

    @effect/cluster no longer requires a Shard Manager, and instead relies on the
    RunnerStorage service to track runner state.

    To migrate, remove any Shard Manager deployments and use the updated layers in
    @effect/platform-node or @effect/platform-bun.

    Breaking Changes

    • ShardManager module has been removed
    • EntityNotManagedByRunner error has been removed
    • Shard locks now use database advisory locks, which requires stable sessions
      for database connections. This means load balancers or proxies that rotate
      connections may cause issues.
    • @effect/platform-node/NodeClusterSocketRunner is now
      @effect/cluster/NodeClusterSocket
    • @effect/platform-node/NodeClusterHttpRunner is now
      @effect/cluster/NodeClusterHttp
    • @effect/platform-bun/BunClusterSocketRunner is now
      @effect/cluster/BunClusterSocket
    • @effect/platform-bun/BunClusterHttpRunner is now
      @effect/cluster/BunClusterHttp

    New Features

    • RunnerHealth.layerK8s has been added, which uses the Kubernetes API to track
      runner health and liveness. To use it, you will need a service account with
      permissions to read pod information.

Patch Changes

@effect/[email protected]

Minor Changes

  • #5606 24a1685 Thanks @tim-smart! - backport @effect/cluster from effect v4

    @effect/cluster no longer requires a Shard Manager, and instead relies on the
    RunnerStorage service to track runner state.

    To migrate, remove any Shard Manager deployments and use the updated layers in
    @effect/platform-node or @effect/platform-bun.

    Breaking Changes

    • ShardManager module has been removed
    • EntityNotManagedByRunner error has been removed
    • Shard locks now use database advisory locks, which requires stable sessions
      for database connections. This means load balancers or proxies that rotate
      connections may cause issues.
    • @effect/platform-node/NodeClusterSocketRunner is now
      @effect/cluster/NodeClusterSocket
    • @effect/platform-node/NodeClusterHttpRunner is now
      @effect/cluster/NodeClusterHttp
    • @effect/platform-bun/BunClusterSocketRunner is now
      @effect/cluster/BunClusterSocket
    • @effect/platform-bun/BunClusterHttpRunner is now
      @effect/cluster/BunClusterHttp

    New Features

    • RunnerHealth.layerK8s has been added, which uses the Kubernetes API to track
      runner health and liveness. To use it, you will need a service account with
      permissions to read pod information.

Patch Changes

@effect/[email protected]

Minor Changes

Patch Changes

@effect/[email protected]

Minor Changes

  • #5606 24a1685 Thanks @tim-smart! - backport @effect/cluster from effect v4

    @effect/cluster no longer requires a Shard Manager, and instead relies on the
    RunnerStorage service to track runner state.

    To migrate, remove any Shard Manager deployments and use the updated layers in
    @effect/platform-node or @effect/platform-bun.

    Breaking Changes

    • ShardManager module has been removed
    • EntityNotManagedByRunner error has been removed
    • Shard locks now use database advisory locks, which requires stable sessions
      for database connections. This means load balancers or proxies that rotate
      connections may cause issues.
    • @effect/platform-node/NodeClusterSocketRunner is now
      @effect/cluster/NodeClusterSocket
    • @effect/platform-node/NodeClusterHttpRunner is now
      @effect/cluster/NodeClusterHttp
    • @effect/platform-bun/BunClusterSocketRunner is now
      @effect/cluster/BunClusterSocket
    • @effect/platform-bun/BunClusterHttpRunner is now
      @effect/cluster/BunClusterHttp

    New Features

    • RunnerHealth.layerK8s has been added, which uses the Kubernetes API to track
      runner health and liveness. To use it, you will need a service account with
      permissions to read pod information.

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

  • #5606 24a1685 Thanks @tim-smart! - backport @effect/cluster from effect v4

    @effect/cluster no longer requires a Shard Manager, and instead relies on the
    RunnerStorage service to track runner state.

    To migrate, remove any Shard Manager deployments and use the updated layers in
    @effect/platform-node or @effect/platform-bun.

    Breaking Changes

    • ShardManager module has been removed
    • EntityNotManagedByRunner error has been removed
    • Shard locks now use database advisory locks, which requires stable sessions
      for database connections. This means load balancers or proxies that rotate
      connections may cause issues.
    • @effect/platform-node/NodeClusterSocketRunner is now
      @effect/cluster/NodeClusterSocket
    • @effect/platform-node/NodeClusterHttpRunner is now
      @effect/cluster/NodeClusterHttp
    • @effect/platform-bun/BunClusterSocketRunner is now
      @effect/cluster/BunClusterSocket
    • @effect/platform-bun/BunClusterHttpRunner is now
      @effect/cluster/BunClusterHttp

    New Features

    • RunnerHealth.layerK8s has been added, which uses the Kubernetes API to track
      runner health and liveness. To use it, you will need a service account with
      permissions to read pod information.
  • Updated dependencies [3c15d5f, 3863fa8, 2a03c76, 24a1685]:

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@effect/[email protected]

Patch Changes

@github-actions github-actions bot force-pushed the changeset-release/main branch from 1cc09a0 to d2c68a0 Compare November 4, 2025 06:44
@tim-smart tim-smart merged commit 7c6dac4 into main Nov 4, 2025
@tim-smart tim-smart deleted the changeset-release/main branch November 4, 2025 06:50
@github-project-automation github-project-automation bot moved this from Discussion Ongoing to Done in PR Backlog Nov 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants