@gjermundgaraba/effect-actions 0.8.0 → 0.9.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/README.md +4 -4
  2. package/docs/README.md +1 -1
  3. package/docs/setup.md +4 -4
  4. package/package.json +4 -4
package/README.md CHANGED
@@ -73,10 +73,10 @@ Code that does not run Effects, such as a browser page, gets the same calls as P
73
73
  ## Install
74
74
 
75
75
  ```sh
76
- pnpm add @gjermundgaraba/effect-actions effect@4.0.0-rc.118
76
+ pnpm add @gjermundgaraba/effect-actions effect@^4.0.0
77
77
  ```
78
78
 
79
- Add `@effect/platform-node@4.0.0-rc.118` to serve from Node. Every module is a subpath import
79
+ Add `@effect/platform-node@^4.0.0` to serve from Node. Every module is a subpath import
80
80
  (`.../Action`, `.../ActionHttp`, ...); there is no package root, so a contracts-only bundle
81
81
  never loads a server.
82
82
 
@@ -101,8 +101,8 @@ in `node_modules/@gjermundgaraba/effect-actions/docs`) gives the same content.
101
101
 
102
102
  ## Status
103
103
 
104
- The `effect` peer accepts any Effect 4.0 release candidate from `4.0.0-rc.118` on; the package
105
- is built and tested against the release candidate in its `devDependencies` (see [docs/setup.md](docs/setup.md)). Actions are unary JSON over HTTP and MCP: no streaming, uploads, prompts, or resources.
104
+ The `effect` peer is `^4.0.0`; the package is built and tested against the Effect release in
105
+ its `devDependencies` (see [docs/setup.md](docs/setup.md)). Actions are unary JSON over HTTP and MCP: no streaming, uploads, prompts, or resources.
106
106
  Authentication and authorization belong to the application. See [docs/setup.md](docs/setup.md).
107
107
 
108
108
  ## Acknowledgements
package/docs/README.md CHANGED
@@ -10,7 +10,7 @@ Read the card for a module before writing code that uses it. Exported TypeScript
10
10
  Package facts that apply everywhere:
11
11
 
12
12
  - Every module is a subpath import: `import * as Action from "@gjermundgaraba/effect-actions/Action"`. There is no package root.
13
- - The `effect` peer accepts any 4.0 release candidate from `4.0.0-rc.118` on (`>=4.0.0-rc.118 <4.0.0`). The package is built and tested against `4.0.0-rc.118`.
13
+ - The `effect` peer is `^4.0.0`. The package is built and tested against `4.0.0`.
14
14
  - Contracts are pure values. Nothing runs, binds, or acquires services until an adapter layer is built.
15
15
 
16
16
  ## Pages
package/docs/setup.md CHANGED
@@ -5,12 +5,12 @@ Install, version pins, entry points, and the boundaries of the package.
5
5
  ## Install
6
6
 
7
7
  ```sh
8
- pnpm add @gjermundgaraba/effect-actions effect@4.0.0-rc.118
8
+ pnpm add @gjermundgaraba/effect-actions effect@^4.0.0
9
9
  ```
10
10
 
11
11
  | Need | Add |
12
12
  | ------------------------------ | ----------------------------------------------------- |
13
- | Node HTTP server or stdio host | `@effect/platform-node@4.0.0-rc.118` |
13
+ | Node HTTP server or stdio host | `@effect/platform-node@^4.0.0` |
14
14
  | `TestingClient.withMcpClient` | `@modelcontextprotocol/client@^2.0.0` (optional peer) |
15
15
 
16
16
  Node `^22.12.0 || ^24.0.0 || >=26.0.0`. ESM only.
@@ -60,6 +60,6 @@ What the package does, and nothing else:
60
60
  ## Failure modes
61
61
 
62
62
  - `Cannot find module '@gjermundgaraba/effect-actions'`: there is no root export. Import a subpath.
63
- - Type errors inside `effect/*` modules after install: `effect` version drift. Install one `effect` release candidate within the peer range for every package.
64
- - `Cannot find module 'effect/http'` (or `effect/http-api`, `effect/cli`, `effect/ai`): `effect` is older than `4.0.0-rc.118`, which moved these modules out of `effect/unstable/*`. Install a release candidate within the peer range, and import from the new paths.
63
+ - Type errors inside `effect/*` modules after install: `effect` version drift. Install one `effect` 4.x release for every package.
64
+ - `Cannot find module 'effect/http'` (or `effect/http-api`, `effect/cli`, `effect/ai`): `effect` is a release candidate older than `4.0.0-rc.118`, which moved these modules out of `effect/unstable/*`. Install `effect` 4.0.0 or later, and import from the new paths.
65
65
  - `@modelcontextprotocol/client` resolution errors in a server build: something imported `TestingClient`. Only tests should.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@gjermundgaraba/effect-actions",
3
- "version": "0.8.0",
3
+ "version": "0.9.0",
4
4
  "description": "Define Effect action contracts once and project them onto HTTP, MCP, native Toolkits, catalogs, and CLIs.",
5
5
  "homepage": "https://github.com/gjermundgaraba/effect-actions#readme",
6
6
  "bugs": {
@@ -35,10 +35,10 @@
35
35
  "access": "public"
36
36
  },
37
37
  "devDependencies": {
38
- "@effect/platform-node": "4.0.0-rc.118",
38
+ "@effect/platform-node": "4.0.0",
39
39
  "@modelcontextprotocol/client": "2.0.0",
40
40
  "@types/node": "26.6.2",
41
- "effect": "4.0.0-rc.118",
41
+ "effect": "4.0.0",
42
42
  "tsx": "4.23.15",
43
43
  "typescript": "7.0.2",
44
44
  "vite": "npm:@voidzero-dev/vite-plus-core@1.0.0",
@@ -46,7 +46,7 @@
46
46
  },
47
47
  "peerDependencies": {
48
48
  "@modelcontextprotocol/client": "^2.0.0",
49
- "effect": ">=4.0.0-rc.118 <4.0.0"
49
+ "effect": "^4.0.0"
50
50
  },
51
51
  "peerDependenciesMeta": {
52
52
  "@modelcontextprotocol/client": {