@farmslot/adapter-web 0.6.3 → 0.6.5
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.
- package/CHANGELOG.md +9 -0
- package/package.json +3 -3
package/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,15 @@ All notable changes to `@farmslot/adapter-web` are tracked here.
|
|
|
6
6
|
|
|
7
7
|
- Active-development baseline; add user-facing changes here before release or package publication.
|
|
8
8
|
|
|
9
|
+
## 0.6.5 - 2026-10-09
|
|
10
|
+
|
|
11
|
+
- A test now pins the web HUD limits that untrusted recipe sources rely on, now that `run` shows the HUD for them: recipe text capped at 180 characters and drawn as text in the closed shadow root, beside the RUN badge and the `step n/m` label. No behavior change.
|
|
12
|
+
- Publish with adapter-sdk 0.8.1 and recipe-runner 0.28.1 so consumers share one adapter-sdk and one recipe-runner copy.
|
|
13
|
+
|
|
14
|
+
## 0.6.4 - 2026-10-09
|
|
15
|
+
|
|
16
|
+
- Publish with adapter-sdk 0.8.0 and recipe-runner 0.28.0 so consumers share one adapter-sdk and one recipe-runner copy. No code change.
|
|
17
|
+
|
|
9
18
|
## 0.6.3 - 2026-10-09
|
|
10
19
|
|
|
11
20
|
- Fix: `launch-browser` stops waiting for its CDP listener once the browser it started has exited (`Chrome launched but did not expose an owned CDP listener on 127.0.0.1:<port>: the browser exited`), or once a process it did not launch holds the port (the same `Refusing to launch on CDP port <port>` refusal the pre-launch check gives, naming that pid). Either must hold for about a second, and a browser started through `open` counts as exited only once it has been seen, or after 5 s. The wait is now 30 s of wall-clock time; before, it was 300 polls: 30 s on an idle host, minutes on a loaded one. After the foreign refusal, once the browser this launch saw start is stopped, the launch markers are cleared, so a rerun on a free port is not refused as quarantined; if that browser was never seen, the markers stay and the refusal names the `rm` that clears them. An exit or a timeout keeps them, as before. A `ps` or `lsof` failure mid-wait now stops the browser before it is reported; if that stop fails too, one error names both failures and the pid to stop, and the markers are kept. Wait progress reports `seconds`, not `attempts`.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@farmslot/adapter-web",
|
|
3
|
-
"version": "0.6.
|
|
3
|
+
"version": "0.6.5",
|
|
4
4
|
"description": "Web platform adapter for Farmslot recipes: resolve and launch an isolated Chromium, own its CDP port, load unpacked extensions, and keep macOS focus.",
|
|
5
5
|
"type": "commonjs",
|
|
6
6
|
"exports": {
|
|
@@ -83,8 +83,8 @@
|
|
|
83
83
|
"prepublishOnly": "node ../../scripts/quality/check-farmslot-package-readiness.mjs --publish --packages @farmslot/adapter-web"
|
|
84
84
|
},
|
|
85
85
|
"dependencies": {
|
|
86
|
-
"@farmslot/adapter-sdk": "0.
|
|
87
|
-
"@farmslot/recipe-runner": "0.
|
|
86
|
+
"@farmslot/adapter-sdk": "0.8.1",
|
|
87
|
+
"@farmslot/recipe-runner": "0.28.1",
|
|
88
88
|
"ws": "^8.18.0"
|
|
89
89
|
},
|
|
90
90
|
"devDependencies": {
|