dsh-tg-bridge 1.4.0 → 1.4.1

package/README.md

@@ -27,9 +27,10 @@ blocks.
 - DeepSeek Harness installed (`~/.dsh/profiles/headless`)
 - A Telegram bot token from [@BotFather](https://t.me/BotFather)
 
-The supported harness range is declared twice: `engines.dsh` in `package.json`
-(what npm and the market read) and `dsh.compatibility.dsh` (what DSH itself
-reads before mounting the bundle). A future `0.3.0` needs an explicit bump:
+The supported harness range is declared in `engines.dsh`; that field decides
+compatibility on its own (DSH ignores `peerDependencies` when it is present).
+The range includes an explicit prerelease branch, because a plain `<0.3.0`
+silently excludes `0.2.2-*` builds. A future `0.3.0` needs an explicit bump:
 the bridge relies on the `0.2.x` CLI flags and profile layout.
 
 ## Ecosystem

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-tg-bridge",
-  "version": "1.4.0",
+  "version": "1.4.1",
   "description": "Telegram bridge for DeepSeek Harness: text, voice, photos and project-per-topic sessions without opening the desktop app",
   "type": "module",
   "main": "plugin-bridge.mjs",
@@ -17,19 +17,11 @@
   },
   "engines": {
     "node": ">=20",
-    "dsh": ">=0.2.1-rc.2 <0.3.0"
+    "dsh": ">=0.2.1-rc.2 <0.3.0-0 || >=0.2.2-rc.1 <0.3.0-0"
   },
   "dsh": {
-    "manifestVersion": 1,
     "bundle": {
       "patch": "./cordis.patch.yml"
-    },
-    "compatibility": {
-      "dsh": ">=0.2.1-rc.2 <0.3.0",
-      "profiles": [
-        "desktop",
-        "web"
-      ]
     }
   },
   "repository": {