Skip to content

chore: upgrade effect to stable v4.0.0 release - #25

Merged
dinwwwh merged 1 commit into
mainfrom
claude/sleepy-noether-fxswtg
Oct 3, 2026
Merged

dinwwwh merged 1 commit into
mainfrom
claude/sleepy-noether-fxswtg

Conversation

@dinwwwh

@dinwwwh dinwwwh commented Oct 3, 2026

Copy link
Copy Markdown
Member

Summary

Updates the Effect library imports from unstable RC versions to the stable v4.0.0 release. This involves updating both the dependency versions in package.json and migrating all import paths from the unstable API namespaces to their stable counterparts.

Key Changes

  • Updated effect and @effect/platform-node dependencies from ^4.0.0-rc.116 to ^4.0.0
  • Migrated all imports from effect/unstable/cli to effect/cli
  • Migrated all imports from effect/unstable/process to effect/process
  • Updated imports across 11 source files to use the stable API paths

Files Modified

  • package.json: Dependency version updates
  • src/commands/uncheck.ts: CLI and process imports
  • src/commands/init.ts: CLI and process imports
  • src/commands/prepare.ts: CLI imports
  • src/commands/staged.ts: CLI imports
  • src/commands/hooks/index.ts: CLI imports
  • src/commands/hooks/install.ts: CLI imports
  • src/commands/hooks/run.ts: CLI imports
  • src/cli.ts: CLI imports
  • src/errors.ts: CLI error imports
  • src/files.ts: Process imports
  • src/git.ts: Process imports
  • src/tool.ts: Process imports
  • src/types.ts: Process type imports

This change stabilizes the Effect library usage and removes dependency on unstable APIs.

https://claude.ai/code/session_012GFt9xsBVmPzK9bhuT69kA

Bump effect and @effect/platform-node from ^4.0.0-rc.116 to ^4.0.0.
The stable release promotes the former `effect/unstable/*` modules to
top-level subpaths, so imports move from `effect/unstable/cli` and
`effect/unstable/process` to `effect/cli` and `effect/process`.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012GFt9xsBVmPzK9bhuT69kA
@pkg-pr-new

pkg-pr-new Bot commented Oct 3, 2026

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/uncheck@25

commit: d7c8b28

@dinwwwh dinwwwh changed the title Upgrade Effect to stable v4.0.0 release chore: upgrade effect to stable v4.0.0 release Oct 3, 2026

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No new issues found.

Reviewed changes

  • Dependency bump — effect and @effect/platform-node moved from ^4.0.0-rc.116 to ^4.0.0; pnpm-lock.yaml regenerated (effect@4.0.0, @effect/platform-node@4.0.0, @effect/platform-node-shared@4.0.0, transitive undici@8.11.2, ws@8.22.0).
  • Import path migration — 13 source files switch effect/unstable/cli → effect/cli and effect/unstable/process → effect/process. No effect/unstable/* imports remain anywhere in the repo.

Verified against the published artifacts: effect@4.0.0 exports ./cli and ./process (and no ./unstable/*), every imported namespace is present (Argument, CliConfig, CliError, CliOutput, Command, Flag, GlobalFlag, Prompt, ChildProcess, ChildProcessSpawner), @effect/platform-node@4.0.0 keeps its ./* wildcard so NodeRuntime/NodeServices still resolve, tsc --noEmit passes against 4.0.0, and the CLI runs cleanly (--version, --help). The lockfile integrity hash for effect@4.0.0 matches the npm registry.

Pullfrog  | View workflow run | Using deepseek-v4.1-flash (free via Pullfrog for OSS) | 𝕏

@codecov

codecov Bot commented Oct 3, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@dinwwwh
dinwwwh merged commit fa8f177 into main Oct 3, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants