Problem
@effect-atom/atom@0.5.3 declares peer dependency ranges that use pre-1.0 caret semantics:
@effect/experimental: ^0.58.0 → >=0.58.0 <0.59.0@effect/platform: ^0.94.2 → >=0.94.2 <0.95.0@effect/rpc: ^0.73.0 → >=0.73.0 <0.74.0
The latest Effect releases are:
@effect/experimental: 0.60.0@effect/platform: 0.96.0@effect/rpc: 0.75.0
These don't fall within the declared peer ranges, so consumers using the latest Effect versions need peerDependencyRules.allowedVersions workarounds in their pnpm workspace config.
Request
Could you cut a new release of @effect-atom/atom (and @effect-atom/atom-react) that updates the peer dependency ranges to cover the latest Effect packages?
Filed on behalf of @schickling by an AI assistant
Problem
@effect-atom/atom@0.5.3declares peer dependency ranges that use pre-1.0 caret semantics:@effect/experimental: ^0.58.0→>=0.58.0 <0.59.0@effect/platform: ^0.94.2→>=0.94.2 <0.95.0@effect/rpc: ^0.73.0→>=0.73.0 <0.74.0The latest Effect releases are:
@effect/experimental: 0.60.0@effect/platform: 0.96.0@effect/rpc: 0.75.0These don't fall within the declared peer ranges, so consumers using the latest Effect versions need
peerDependencyRules.allowedVersionsworkarounds in their pnpm workspace config.Request
Could you cut a new release of
@effect-atom/atom(and@effect-atom/atom-react) that updates the peer dependency ranges to cover the latest Effect packages?Filed on behalf of @schickling by an AI assistant