@gjsify/webview2-native 0.54.0 → 0.56.0

package/README.md

@@ -190,8 +190,10 @@ and a lie:
   per-handler shim would run *after* a bootstrap script that uses it — which is
   the whole `@gjsify/iframe` bridge. The host warns once per unknown channel,
   naming it, rather than discarding the message in silence.
-- **`x64` only.** `gvsbuild` publishes no arm64 GTK, so ADR 0024's `--arch arm64`
-  refusal on Windows already forecloses the question.
+- **`x64` only.** `@gjsify/gtk-runtime-win32-arm64` is not built yet, so ADR 0024's
+  `--arch arm64` refusal on Windows forecloses the question and this package
+  inherits it rather than restating it. (The prefix is not the obstacle: ADR 0089
+  builds it from our `gjsify/gvsbuild` fork in CI.)
 
 ## The runtime closure is bigger than the tarball
 

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@gjsify/webview2-native",
-    "version": "0.54.0",
+    "version": "0.56.0",
     "description": "Microsoft's WebView2 (Chromium) behind a GObject API shaped like WebKitGTK 6.0 — the win32 backend for @gjsify/iframe (ADR 0035). Deliberately claims the WebKit-6.0 namespace; the engine is Chromium. Contains no JavaScript; the prebuilt library and typelib arrive through per-target optionalDependencies.",
     "type": "module",
     "files": [],
@@ -54,6 +54,6 @@
     },
     "homepage": "https://github.com/gjsify/gjsify/tree/main/packages/framework/webview2-native#readme",
     "optionalDependencies": {
-        "@gjsify/webview2-native-win32-x64": "0.54.0"
+        "@gjsify/webview2-native-win32-x64": "0.56.0"
     }
 }