tim-smart / tim-smart/effect-atom
Release new version for latest Effect (3.21+)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 792
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the package metadata for @effect-atom/atom and @effect-atom/atom-react, then inspect the repository's release configuration. Update the peer dependency ranges to cover the listed Effect versions, verify the package metadata, and cut the requested releases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100