@ego-z/contracts 0.15.5 → 0.15.6

package/README.md

@@ -58,6 +58,30 @@ import type { AskRequestBody, AskResponseData, AskStreamEvent } from '@ego-z/con
 their generated `.d.ts` automatically — end users see the types as if
 they were declared in the SDK itself.
 
+## ⚠️ Do not pin `0.15.5`
+
+`0.15.5` was published with a `dependencies` entry naming **itself**
+(`"@ego-z/contracts": "^0.15.0"`). It is harmless while 0.15.5 is the newest
+0.15.x — npm resolves that range back to the same copy and dedupes it:
+
+```
+`-- @ego-z/contracts@0.15.5
+  `-- @ego-z/contracts@0.15.5 deduped
+```
+
+**It stops being harmless the moment a newer 0.15.x exists.** That range can
+then resolve a *different* version nested underneath 0.15.5, putting two
+copies of the same types in one tree — the classic "these two identical
+interfaces are not assignable" failure, from a cause nobody would think to
+look for.
+
+So: **when the next patch ships, move off 0.15.5 rather than staying on it.**
+Don't pin it, and don't leave a lockfile resolving to it.
+
+The source is already fixed — the package declares no runtime dependencies at
+all — so the next publish for any reason clears it. It was not worth a
+version bump on its own mid-integration.
+
 ## When to bump
 
 - **Adding** an optional field — non-breaking, no version bump required

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ego-z/contracts",
-  "version": "0.15.5",
+  "version": "0.15.6",
   "description": "Wire-format type contracts shared between EgoZ backend, SDK, MCP and console. Type-only — no runtime artifacts.",
   "types": "./src/index.d.ts",
   "exports": {
@@ -44,8 +44,5 @@
   },
   "devDependencies": {
     "typescript": "^5.0.0"
-  },
-  "dependencies": {
-    "@ego-z/contracts": "^0.15.0"
   }
 }