chrome-relay 0.5.4 → 0.5.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/dist/cli.js +8 -1
- package/dist/index.js +1 -1
- package/dist/native-host.js +1 -1
- package/package.json +1 -1
package/dist/cli.js
CHANGED
|
@@ -43,7 +43,7 @@ var RelayError = class extends Error {
|
|
|
43
43
|
};
|
|
44
44
|
|
|
45
45
|
// src/index.ts
|
|
46
|
-
var CHROME_RELAY_VERSION = true ? "0.5.
|
|
46
|
+
var CHROME_RELAY_VERSION = true ? "0.5.5" : "0.0.0-dev";
|
|
47
47
|
|
|
48
48
|
// src/install/install.ts
|
|
49
49
|
import os from "os";
|
|
@@ -196,6 +196,13 @@ async function callTool(name, args) {
|
|
|
196
196
|
|
|
197
197
|
// src/release-notes.ts
|
|
198
198
|
var RELEASE_NOTES = {
|
|
199
|
+
"0.5.5": [
|
|
200
|
+
"BEHAVIOR CHANGE \u2014 `chrome_navigate --new` no longer silently falls back to 'wherever Chrome picks' when an explicit routing intent fails (code-quality-hardening PR 3).",
|
|
201
|
+
"`navigate --new --tab <id>` where <id> doesn't exist now throws `target_not_found` instead of silently letting Chrome drop the tab in the focused (often the user's) window.",
|
|
202
|
+
"`navigate --new --group <name>` where the group-join fails now throws `partial_success_disallowed`. The new tab IS created (we don't roll back) so the agent can clean it up; the error details include `createdTabId` and `groupName`.",
|
|
203
|
+
"Both new strict paths accept `allowPartial: true` as an arg to opt back into the legacy best-effort behavior. With allowPartial, the success result carries `partial: true` and a `warnings[]` array naming what didn't happen.",
|
|
204
|
+
"Tightened `chrome_navigate` argument errors to RelayError(invalid_arguments) \u2014 missing url, non-numeric tabId."
|
|
205
|
+
],
|
|
199
206
|
"0.5.4": [
|
|
200
207
|
"Strict target routing (code-quality-hardening PR 2). Within a single scope, --tab / --workspace / --group are mutually exclusive \u2014 passing more than one on the same subcommand (or both at the program level) now fails with `target_conflict` and exit code 2.",
|
|
201
208
|
"Cross-scope override is still allowed but visible: `chrome-relay --workspace W <cmd> --workspace W2` works, but stderr prints a `target_overridden: workspace W \u2192 W2` notice so the agent (or user) knows what happened.",
|
package/dist/index.js
CHANGED
package/dist/native-host.js
CHANGED
|
@@ -48,7 +48,7 @@ function toBridgeError(unknownErr, fallbackTool) {
|
|
|
48
48
|
}
|
|
49
49
|
|
|
50
50
|
// src/index.ts
|
|
51
|
-
var CHROME_RELAY_VERSION = true ? "0.5.
|
|
51
|
+
var CHROME_RELAY_VERSION = true ? "0.5.5" : "0.0.0-dev";
|
|
52
52
|
|
|
53
53
|
// src/release-notes.ts
|
|
54
54
|
function compareSemver(a, b) {
|